Wed Jul 9 04:08:30 PDT 2008 Simon Marlow <[EMAIL PROTECTED]>
* #1205: ':load foo.hs' in GHCi always compiles to bytecode
So now
:load foo.hs loads bytecode for foo.hs, even if foo.o exists
:load foo is just shorthand for :load foo.hs
:load M loads a module M, as object code if possible
(no change here)
If the first two are the same, what is the distinction between the last
two? In other words, what happens if module M is in file M.hs?
This turned out to be very straightforward: when building the
ModSummary for a file (summariseFile) we just ignore the object file
unless -fobject-code is on.
This would seem a simpler specification, but it would rule out
case 3 above.
In the use case of one module interpreted for debugging/inspection,
everything else compiled, one often has to do a make to generate
all object code in a consistent fashion, but one still wants to load a
few modules at a time interpreted in GHCi, with their imports
loading compiled. Does that still work?
Claus
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
