10 Nov
2011
10 Nov
'11
7:56 a.m.
Hi, Am Donnerstag, den 10.11.2011, 12:36 +0000 schrieb Simon Marlow:
It's not what we traditionally refer to as "lazy IO". It is lazy, but it is not injecting side-effects into pure compuations. You can tell that it isn't problematic by the fact that you can implement hPutStrLn yourself in terms of hPutChar, there's no ned for unsafeInterleaveIO.
The problematic lazy I/O is really just hGetContents and getContents. So it's really just lazy I, not lazy I/O.
ah, got it. Thanks for the clarification! Greetings, Joachim -- Joachim "nomeata" Breitner mail@joachim-breitner.de | nomeata@debian.org | GPG: 0x4743206C xmpp: nomeata@joachim-breitner.de | http://www.joachim-breitner.de/