|
Re: stdin set to nonblocking mode: msg#00084lang.haskell.glasgow.bugs
On Fri, Aug 12, 2005 at 07:43:56AM -0700, John Meacham wrote: > > Hmm, care to give some details as to why you equate "can" with > > "always will" on all platforms? > > Yes. this is guarenteed behavior on pretty much every system. A whole > lot of things would break if it were otherwise. if select says a file > descriptor can be written to or read from then the next write or read call is > guarenteed to not block, no matter what its size. (you just may get a > short read or write) However, this next read/write doesn't have to be the one you call right after select - it could be called in another process/thread, which shares the open socket or pipe. Best regards Tomasz
|
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: stdin set to nonblocking mode, John Meacham |
|---|---|
| Next by Date: | runghc, .hs suffix, Frederik Eaton |
| Previous by Thread: | Re: stdin set to nonblocking mode, John Meacham |
| Next by Thread: | RE: stdin set to nonblocking mode, Simon Marlow |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |