Re: hGetBuf (or something related) broken for 6.2 with sockets

On Fri, Dec 19, 2003 at 11:39:28AM +0100, Tomasz Zielonka wrote:
> 
> 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.

I am mixing things again:

The change of hGetBuf's semantics happened between GHC 6.0 and 6.2.
I thinks the semantics in 6.0 is more intuitive.

Now we have hGetBufNonBlocking with the old semantics of hGetBuf.
Wouldn't it be better to have hGetBuf with old semantics and
hGetBufBlocking with the new one? This way we wouldn't break existing
programs.

Best regards,
Tom

-- 
.signature: Too many levels of symbolic links