Hi
On 21 Mar 2002, Jens Petersen wrote:
> Volker Wysk <[EMAIL PROTECTED]> writes:
> > POpen-1.0.0 contains the same bug which I made. It doesn't ensure that
> > the values which are needed after the call of forkProcess, before that
> > of executeFile, are fully evaluated. So, if they are read laz
Hi Volker,
Volker Wysk <[EMAIL PROTECTED]> writes:
> On Mit, 2002-03-20 at 07:00, Jens Petersen wrote:
> > Jens Petersen <[EMAIL PROTECTED]> writes:
> >
> > > > The problem is that the child process doesn't
> > > > receive all the data which the parent sends. It's as
> > > > if "hPutStr vonh tx
On Mit, 2002-03-20 at 07:00, Jens Petersen wrote:
> Jens Petersen <[EMAIL PROTECTED]> writes:
>
> > > The problem is that the child process doesn't receive all the data which
> > > the parent sends. It's as if "hPutStr vonh txt" sends the data lazily
> > > somehow, and "hClose vonh" closes the pi
Jens Petersen <[EMAIL PROTECTED]> writes:
> > The problem is that the child process doesn't receive all the data which
> > the parent sends. It's as if "hPutStr vonh txt" sends the data lazily
> > somehow, and "hClose vonh" closes the pipe prematurely.
> >
> > It varies from run to run exactly w
Volker Wysk <[EMAIL PROTECTED]> writes:
> (zu, von) <- createPipe
> vonh <- fdToHandle von
> hSetBuffering vonh NoBuffering
> mpid <- forkProcess
> case mpid of
>Nothing -> do -- child
> -- connect pipe's read end to stdin
>
Hello
There seems to be a bug in the IO libraries. I'm using the following
procedure to call an external program and send it data through a pipe.
pipeto :: String -> String -> [String] -> IO ()
pipeto txt prog par = do
catch (do
-- create pipe
(zu, von) <- createPipe
