| I didn't try it, because I didn't know about that flag. I'll
| experiment with it at some point. But from your other comments, it
| sounds like you're confirming my suspicion that making GHC generate
| External Core files that it can read back in again entails either
| paying an optimization cost in terms of the generated Core files, or
| cross-cutting changes to GHC?

I think that's a separate question.

I'm saying that if you want to read in a ExtCore file, you'd better not have 
recompiled any of the modules it depends on.  But that's true for linking too!  
If A imports B, and you recompile B you may well get link errors if you link 
the old A.o with the new B.o.  It's not specific to ExtCore at all.

Maybe I'm missing your point?

S

_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc

Reply via email to