Endangered I/O operations

Sigbjorn Finne sof@galconn.com
Tue, 22 May 2001 09:46:48 -0700

----- Original Message -----
From: "Simon Marlow" <simonmar@microsoft.com>
To: "Sigbjorn Finne" <sof@galconn.com>
Cc: "GHC Users Mailing List (GHC Users Mailing List)"
Sent: Tuesday, May 22, 2001 03:30
Subject: RE: Endangered I/O operations

> > If you handle std{in,out,err} connectedness in other ways,  I
> > think you've
> > covered 99.2% of the uses of hConnectTo. Neat idea borrowed from
> > Korn & Vo's SFIO, but it hasn't proved to be all that useful.
> I wasn't planning to handle connectedness at all.  Is it important, do
> you think?  (I'm not against the feature, just trying to avoid feeping
> creaturism...)

Yes, crucial I think - if stdout and stderr are connected to the same
don't you want their output to be synchronised, e.g.,

main = putStr "foo" >> hPutStr stderr " bar"

should return "foo bar" on your TTY. Ditto for flushing stdout/stderr when
peeking stdin.