On 18/05/2010 15:44, Thomas Schilling wrote:
If readTextDeviceNonBlocking is not non-blocking, shouldn't its name
be changed to something more accurate? Or at the very least its
documentation?
Something ought to be done, I agree. The problem is that it's not
really readTextDeviceNonBlocking that's the problem, but rather the
Win32 implementation of FD (GHC.IO.Handle.FD), which doesn't support
non-blocking operations. I really hope someone will make a better Win32
backend for the IO library sometime.
I'll add something to the docs for the user-facing API here
(hGetBufNonBlocking).
Cheers,
Simon
On 18 May 2010 08:59, Simon Marlow<[email protected]> wrote:
Mon May 17 06:37:41 PDT 2010 Simon Marlow<[email protected]>
* hWaitForInput: don't try to read from the device (#4078)
readTextDeviceNonBlocking is not non-blocking on Windows
M ./GHC/IO/Handle/Internals.hs -10 +17
M ./GHC/IO/Handle/Text.hs -1 +1
View patch online:
http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=packages/base;a=darcs_commitdiff;h=20100517133741-12142-daba37f0c8cac73c94a5874b2ed3f0f39d7962bd.gz
_______________________________________________
Cvs-libraries mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-libraries
_______________________________________________
Cvs-libraries mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-libraries
