We don't support Posix for Win32. It's probably not impossible to
implement it, but we have not devoted the time to do so. Maybe you can?
Simon
| -Original Message-
| From: Ahn Ki-yung [mailto:[EMAIL PROTECTED]]
| Sent: 25 November 2002 06:37
| To: [EMAIL PROTECTED]
| Subject: how can
Simon Marlow [EMAIL PROTECTED] writes:
One reason, I think, is lazy I/O(*). It's to stop you accidentally
[...]
(*) kill it! die! die!
So you want
main = readFile /dev/zero return ()
to terminate violantly rather than terminate peacefully? :)
Seriously, I understand that
Simon Marlow:
[Lazy I/O] is nice, but it introduces too many problems. What
happens to any I/O errors encountered by the lazy I/O? They have to
be discarded, which means you can't effectively use lazy I/O for
robust applications anyway.
Surely they are thrown as exceptions which can then
On Mon, Nov 25, 2002 at 10:09:01AM -, Simon Marlow wrote:
It is nice, but it introduces too many problems. What happens to any
I/O errors encountered by the lazy I/O? They have to be discarded,
which means you can't effectively use lazy I/O for robust applications
anyway.
Simon Marlow:
[Lazy I/O] is nice, but it introduces too many problems. What
happens to any I/O errors encountered by the lazy I/O? They have to
be discarded, which means you can't effectively use lazy I/O for
robust applications anyway.
Surely they are thrown as exceptions which can
I am reading the article template meta-programming for haskell and am
wondering if
1) this is already implemented in ghc.
2) if not when this will be released
Thanks in advance
Immanuel
***
His endeavours to improve these
Simon Marlow wrote:
Simon Marlow:
[Lazy I/O] is nice, but it introduces too many problems. What
happens to any I/O errors encountered by the lazy I/O? They have to
be discarded, which means you can't effectively use lazy I/O for
robust applications anyway.
Surely they are
On Mon, Nov 25, 2002 at 11:22:56AM -0500, Dean Herington wrote:
Is even the following example from the library report (section 11.8.2)
problematic?
import System
import Char( toUpper )
main = do
[f1,f2] - getArgs
s - readFile f1
writeFile f2 (map toUpper s)
Simon Marlow wrote:
Simon Marlow:
[Lazy I/O] is nice, but it introduces too many problems. What
happens to any I/O errors encountered by the lazy I/O?
They have to
be discarded, which means you can't effectively use lazy I/O for
robust applications anyway.
Surely
I am reading the article template meta-programming for haskell and am
wondering if
1) this is already implemented in ghc.
2) if not when this will be released
answered in section 2.1 (GHC) and 3.6.1 (Template Haskell) of the
Haskell Communities Activities Report (November 2002 edition):
10 matches
Mail list logo
