On Sat, 09 Sep 2006 23:34:55 -0300, David Sankel [EMAIL PROTECTED] wrote:
On 9/5/06, Bruno Martínez [EMAIL PROTECTED] wrote:
C++ avoids this problem 'tieing' cin and cout. Why can't haskell do the
same?
I was thinking the same thing. I'm imagining a situation where processes
are
On 9/5/06, Bruno Martínez [EMAIL PROTECTED] wrote:
C++ avoids this problem 'tieing' cin and cout.Why can't haskell do thesame?I was thinking the same thing. I'm imagining a situation where processes are communicating to each other using pipes, but cannot think of a concrete case. Do you know if
Tomasz Zielonka wrote:
On Sat, Sep 02, 2006 at 05:11:33PM -0700, Jeremy Shaw wrote:
GHCi and the compiled program do not buffer the output in quite the
same way.
This comes up so often that perhaps GHCi should advertise those
differences. For example, the starting message could say
Simon Marlow wrote:
We could consider adding a message along the lines you suggest... any
other ideas?
I remember running into this. I wasn't confused by the expected
behavior, it was the fact that ghci had different behavior than compiled
programs and that the settings seem to be
