Dear GHC users If you use GHC 6.0 on Win32, read on. Otherwise, don't bother. Some of you have already discovered that GHC 6.0 has a nasty bug: if you go ghci foo\Baz.hs and there is any error at all in Baz.hs, then GHC deletes the source file! This seems like excessive punishment for a type error. So far as I am aware, this only happens * on windows * with ghci (not ghc) * if you put back-slashes in the path There's no problem if you use forward slashes, or no slashes at all. This will be fixed in 6.0.1, which we'll put out in a couple of weeks, but meanwhile you might want to be aware of it. A bit of an egg-on-face job really. Simon
On Mon, Jul 07, 2003 at 03:49:38PM +0100, Simon Peyton-Jones wrote:
Some of you have already discovered that GHC 6.0 has a nasty bug: if you go ghci foo\Baz.hs and there is any error at all in Baz.hs, then GHC deletes the source file! This seems like excessive punishment for a type error.
And it doesn't even require a type error as an excuse for punishment! .. if the source file is specified as ./file.hs Example: $ echo "module T where" > T.hs && ghc --make ./T.hs -v ... Deleting: ./T.hs This is on linux, don't know about windows.. /Peter
participants (2)
-
Peter Strand -
Simon Peyton-Jones