in reply to Re: Re: Re: porting this 'setnonblocking' subroutine to Windows
in thread porting this 'setnonblocking' subroutine to Windows

You're right, it's a typo, and the code could stand some cleaning up. Regarding the EWOULDBLOCK problem, POSIX::EWOULDBLOCK should probably be set to the same value as EAGAIN. I believe they are synonymous. 
   MeowChow                                   
               s aamecha.s a..a\u$&owag.print
  • Comment on (MeowChow) Re4: porting this 'setnonblocking' subroutine to Windows

Replies are listed 'Best First'.
Re (tilly) 5: porting this 'setnonblocking' subroutine to Windows
by tilly (Archbishop) on Jan 06, 2002 at 00:24 UTC
    EAGAIN and EWOULDBLOCK are actually different errors, though they are similar enough that many vendors alias one to the other.

    Certainly if one is present and the other is not, then I think the missing should be aliased to the present one. But they should not be assumed to be identical because they aren't always.

[reply]

In Section Seekers of Perl Wisdom