process: Confusion about UseHandle handles being closed.
Brandon Allbery
allbery.b at gmail.com
Tue Nov 25 13:20:24 UTC 2014
On Tue, Nov 25, 2014 at 5:27 AM, Michael Snoyman <michael at snoyman.com>
wrote:
> When working on a library, I was surprised to find that the `Handle`s that
> I passed in for `std_in`, `std_out` and `std_err` via `UseHandle` were
> automatically closed. This is not clear from the documentation, and- at
> least for the use case I was interested in- the opposite of what I needed.
Can you explain that use case? It's usually an error to try to use the file
descriptor in the parent as well as the child, because there's no way to
prevent interleaved I/O at the OS level.
--
brandon s allbery kf8nh sine nomine associates
allbery.b at gmail.com ballbery at sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/libraries/attachments/20141125/2d01fd57/attachment.html>
More information about the Libraries
mailing list