RE: Bug with readFile and named pipes

2001-08-24 Thread Simon Marlow
Simon Marlow wrote: There was a long thread about this a while back (subject Blocking I/O and FIFOs). I didn't find it in the archives... Try here: http://www.mail-archive.com/glasgow-haskell-bugs@haskell.org/msg03235.ht ml unfortunately the archives at haskell.org aren't

RE: Bug with readFile and named pipes

2001-08-23 Thread Simon Marlow
In local.glasgow-haskell-bugs, you wrote: Programs that read from a named pipe usually block until a writer opens the pipe and writes something to it. The following program, main = putStr = readFile /tmp/p (where /tmp/p refers to a named pipe) exhibits this behavour when

Re: Bug with readFile and named pipes

2001-08-23 Thread Thomas Hallgren
Simon Marlow wrote: There was a long thread about this a while back (subject Blocking I/O and FIFOs). I didn't find it in the archives... The conclusion was that the behaviour varies between OSs: the behaviour Thomas described occurs on FreeBSD, but not Linux or Solaris. POSIX appears to

Re: Bug with readFile and named pipes

2001-08-22 Thread Volker Stolz
In local.glasgow-haskell-bugs, you wrote: Programs that read from a named pipe usually block until a writer opens the pipe and writes something to it. The following program, main = putStr = readFile /tmp/p (where /tmp/p refers to a named pipe) exhibits this behavour when compiled

Bug with readFile and named pipes

2001-08-21 Thread Thomas Hallgren
Hi. Programs that read from a named pipe usually block until a writer opens the pipe and writes something to it. The following program, main = putStr = readFile /tmp/p (where /tmp/p refers to a named pipe) exhibits this behavour when compiled with HBC or when run with runhugs, but *not*