[GHC] #1439: ghci silently changes for the worse when already-compiled object code is found

[GHC]

#1439: ghci silently changes for the worse when already-compiled object code is
found
---------------------------+------------------------------------------------
  Reporter:  Isaac Dupree  |          Owner:         
      Type:  bug           |         Status:  new    
  Priority:  normal        |      Milestone:         
 Component:  GHCi          |        Version:  6.6.1  
  Severity:  normal        |       Keywords:         
Difficulty:  Unknown       |             Os:  Unknown
  Testcase:                |   Architecture:  Unknown
---------------------------+------------------------------------------------
{{{ghci MyModule}}}

 If it's been compiled (i.e., up-to-date MyModule.{hi,o} files exist), then
 I can't get to the non-exported symbols in MyModule, in ghci.  Removing
 the .{hi,o} works around it.  (I haven't tried it in any 6.7, sorry, I
 have the feeling it might be different there, but I don't have a 6.7
 stage2)

 If it's not easy/desirable to change the behavior, at least say something
 like "Warning: loading object code, you won't be able to see non-exported
 symbols in this module.  To avoid this, (do x)"

 `-fforce-recomp` recompiles imported modules for ghci too (an inefficient
 workaround). Not sure about the new `-fbyte-code`, maybe it could be
 relevant here?

-- 
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/1439>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
-------------- next part --------------
_______________________________________________
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs at haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs