Hm, what about if the harddrive is busy with higher-prioritized IO operations. In this case I suppose the a nonblocking file read is supposed to return with 0 bytes immediately - what do you say?

Though, I suppose there's no way to know from the OS when the drive will be ready for making access again since there's no async-ness in the standard file read procedure, I wonder how Gambit works in relation with that currently (though it's really a kind of exotic situation).

Mikael

2011/6/15 Alan Post <alanpost@sunflowerriver.org>
On Wed, Jun 15, 2011 at 07:44:15AM -0400, Marc Feeley wrote:
> and see if that eliminates the problem.  Of course this makes I/O to files blocking, so the thread multiplexing will not work when doing I/O to files.
>

My understanding is that for regular files, nonblocking mode is
essentially a no-op, as regular files don't block in the way, say,
an interactive prompt or a network socket would.

Can someone confirm or disprove this?

-Alan
--
.i ma'a lo bradi ku penmi gi'e du
_______________________________________________
Gambit-list mailing list
Gambit-list@iro.umontreal.ca
https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list