Re: Notes when applying IO channel patch

[Johannes Stezenbach <js convergence de>]

Owen Taylor wrote:
> 
> If we remove ERANGE, EBADMSG as being STREAMS things, say that
> we warn and don't return EBADF and EFAULT, and handle EGAIN
> and EINTR internally, then the set is:

EAGAIN can happen on non-blocking file descriptors only, and
there it makes no sense to handle it internally: The user
asked for it by setting the file descriptor to non-blocking
and needs EAGAIN for status notification.

Besides, how would you handle EAGAIN internally?
Busy waiting until the read/write() call succeeds?


Regards,
Johannes