Re: readFile close behaviour
Simon Marlow [EMAIL PROTECTED] writes: The upshot is that while GHC might notice that you have dropped a Handle, another implementation which doesn't do black holing, stack stubbing, strictness analysis, GC evaluation of selector thunks or any of the other tricks we do to avoid space leaks might not notice. Maybe I'm confused but I thought the original complaint was that GHC (which plays all these tricks) was leaking objects (file descriptors) worse than Hugs (which plays very few of these tricks). -- Alastair Reid[EMAIL PROTECTED]http://www.cs.utah.edu/~reid/ ___ Glasgow-haskell-bugs mailing list [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
HDirect - Make install on Win32
Hi there. Trivial comments about things that can make builds smoother: Make install in CVS HDirect doesn't copy WideString.hs and WideString.hi to the target directory. It copies the *.hi files to share rather than imports/com. It copies lib*.a to lib rather than ghc/ghc-5.02. Cheers Mike Thomas. ___ Glasgow-haskell-bugs mailing list [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
Re: hGetContents bug?
I'll get a strange result if the file contains the character 1A-hexadecimal (or 26-decimal): all characters beyond this point won't be printed on the screen. I think this is correct behaviour for a text file under Windows/DOS... you should open the file as binary instead. --KW 8-) ___ Glasgow-haskell-bugs mailing list [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
