On Fri, Dec 19, 2003 at 10:26:02AM -0000, Simon Marlow wrote: > > > On Thu, Dec 18, 2003 at 09:53:50PM +0100, Tomasz Zielonka wrote: > > > On Thu, Dec 18, 2003 at 07:44:58PM +0100, George Russell wrote: > > > > > > It seems to work when I change hGetBuf to > > hGetBufNonBlocking. The name > > > is a bit misleading - the action _does_ wait for some data, > > but it doesn't > > > wait for all requested bytes. > > > > I've made a mistake here. > > > > hGetBuf waits for filling the whole Handle's reading buffer > > (or reaching > > EOF), even if the buffer contains enough data to satisfy the request. > > I'm a bit lost. Do things work as you expect, or not?
Well, I think that it would be better if hGetBuf didn't block if all requested data was already in buffer, but I don't insist on it. However this change of semantics can brake existing programs. In my programs I rather use Data.Array.IO.hGetArray. I was only trying to help George. I am sorry if I only made things more complicated :) > Cheers, > Simon Best regards, Tom -- .signature: Too many levels of symbolic links _______________________________________________ Glasgow-haskell-bugs mailing list [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
