I thought about that...it would still be better to add EWOULDBLOCKReadable,
etc, than to pay the .extend toll every time.
On Mar 17, 2012 10:28 AM, "Tanaka Akira" <akr / fsij.org> wrote:

> 2012/3/16 Charles Nutter <headius / headius.com>:
>
> > The nonblocking IO operations started extending WaitReadable or
> WaitWritable into the Errno::EAGAIN instance some time during the 1.9
> series. This has a rather high cost, since a singleton class must be
> created and the global method cache must be flushed.
> >
> > The attached patch instead creates two new classes of the following
> form, and raises them rather than raising a singleton EAGAIN:
>
> EWOULDBLOCK is a different from EAGAIN on some platforms.
> (HP-UX, for example.)
>
> I think your patch breaks applications which rescue only EWOULDBLOCK,
> on such platforms.
> --
> Tanaka Akira
>
>