Re: NSFileHandle notifications
Re: NSFileHandle notifications
- Subject: Re: NSFileHandle notifications
- From: Charles Bennett <email@hidden>
- Date: Tue, 31 Jul 2001 14:45:55 -0400
[munched]
Very old bug alert..(perhaps) This is a true reach into almost forgotton memory,
and we all know that the mind is the SECOND thing to go, but..
In a former life I reported an apparent bug in select() all the way back to NeXTSTEP 2.0
At the time it seemed that select always returned "ready" but had zero bytes
to be read. I seem to remember thinking that it was triggered by select calls against tty/pty file handles.
There was some back and forth with the NeXTSTEP tech folks, but I don't think it was ever fixed..
Makes me wonder if some form of this bug has lurked all the way to OS X..
>
The no-data could be because there is an error occurring (say, in the
>
background wait) or because no data has been added to the file (your fd
>
is still "at EOF") but select() is returning the file descriptor as
>
readable anyway.
>
>
In any case, I'd try converting to -readInBackgroundAndNotify.
>
>
Chris Kane
>
Cocoa Frameworks, Apple
>
_______________________________________________
>
cocoa-dev mailing list
>
email@hidden
>
http://www.lists.apple.com/mailman/listinfo/cocoa-dev