> This is a bug which has been in GHCi from the beginning.
This is actually the defined behaviour (see Section 3.3 of the User's
Guide: a newly compiled object will only be noticed on a :load, not
:reload). But your message made us wonder whether the restriction can
be relaxed slightly, and in the situation you illustrated I think it
can.
There are some technical subtleties to do with the way GHC computes
version numbers for exported entities so it can decide whether a module
needs to be recompiled or not; the upshot is that within a GHCi
"session" (i.e. between one :load and the next) a given module cannot go
from being interpreted to compiled, although it can make the opposite
transition. This restriction will still apply, but I'll remove the
restriction that you can't load a new version of an object file with
:reload.
Cheers,
Simon
_______________________________________________
Glasgow-haskell-bugs mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
