FROM : I. Savant
DATE : Thu Jan 10 18:33:12 2008
> Yes, that seems reasonable, but the more I think about it, the more I
> think it must be a bug in the library. Based on the stack trace, it
> seems like it's a problem with the NSInputStream object, but I even
> tried doing
That's entirely possible, but not particularly likely as this is a
pretty well-used part of the API. Such a simple use case surely has
been done many times before ... ;-)
At this point, it's probably best to isolate this problem in a test
project (a pain, I know, but a necessary one) and see if you can
reproduce. Post the project on one of the many file sharing sites and
send the link to the list.
--
I.S.
DATE : Thu Jan 10 18:33:12 2008
> Yes, that seems reasonable, but the more I think about it, the more I
> think it must be a bug in the library. Based on the stack trace, it
> seems like it's a problem with the NSInputStream object, but I even
> tried doing
That's entirely possible, but not particularly likely as this is a
pretty well-used part of the API. Such a simple use case surely has
been done many times before ... ;-)
At this point, it's probably best to isolate this problem in a test
project (a pain, I know, but a necessary one) and see if you can
reproduce. Post the project on one of the many file sharing sites and
send the link to the list.
--
I.S.
| Related mails | Author | Date |
|---|---|---|
| Dave Carrigan | Jan 10, 01:03 | |
| Dave Carrigan | Jan 10, 17:40 | |
| I. Savant | Jan 10, 17:52 | |
| Dave Carrigan | Jan 10, 18:29 | |
| I. Savant | Jan 10, 18:33 | |
| j o a r | Jan 10, 19:01 | |
| Dave Carrigan | Jan 10, 19:01 | |
| I. Savant | Jan 10, 19:34 | |
| j o a r | Jan 10, 22:17 |






Cocoa mail archive

