From: Bill Kelly <billk@...>
Date: 2006-05-21T10:25:30+09:00
Subject: Re: sysread changes behavior in the presence of threads?

From: "Francis Cianfrocca" <garbagecat10@gmail.com>
> Ahh, thanks for pointing it out, although it ain't the answer I was hoping
> for. Interesting that your concern (not having to think about EAGAIN) is
> opposite from mine- I'm *wanting* to get EAGAIN so I can do something else
> while waiting for the I/O.

Yeah.  I didn't have a specific need to check for EAGAIN at the
time, but my main point was trying to express my confusion that
there would be this one semi-obscure case (single thread only)
that acted differently from the rest.  I say obscure because I
don't think I'd ever write code in ruby to expect that no other
threads were present in the system.  How would I know that
some other library I've required hasn't spawned some worker
thread for its own internal use?  So having ruby act 
inconsistently in the particular case of there being only one
thread alive seems peculiar to me.  So my point was I was 
confused by that behavior since it seems like something I could
never be able to reliably expect to depend on.  :)


Regards,

Bill