In local.glasgow-haskell-bugs, you wrote:
I've stripped down my program to produce an example. In the process, the
problem disappeard a few times. I hope it shows up on your machine. The
attached files reproduce it on my machine, but the exact results vary
from run to run.
There's no bug in
In local.glasgow-haskell-bugs, you wrote:
I've stripped down my program to produce an example. In the
process, the
problem disappeard a few times. I hope it shows up on your
machine. The
attached files reproduce it on my machine, but the exact
results vary
from run to run.
Just to be sure, I've changed to example program a bit (see attachment).
I think it now demonstrates clearly that there must be a bug in the
libraries.
- If the child closes its child's stdin before calling executeFile, all
data gets through.
- If instead the child's child (echo.c) closes stdin
Am 15. Mar 2002 um 14:39 MET schrieb Volker Wysk:
- If instead the child's child (echo.c) closes stdin immediately after
being executed, some data is lost.
Where's the use in closing stdin when you're passing arguments as
parameters? This is effectively a NOP and shouldn't influence the
On Fre, 2002-03-15 at 15:05, Volker Stolz wrote:
Am 15. Mar 2002 um 14:39 MET schrieb Volker Wysk:
- If instead the child's child (echo.c) closes stdin immediately after
being executed, some data is lost.
Where's the use in closing stdin when you're passing arguments as
parameters? This
