17 Dec
2007
17 Dec
'07
2:41 p.m.
Luke Palmer wrote:
There was a thread about this recently.
In any case, if you load the code interpreted (which happens if there is no .o or .hi file of the module lying around), then you can look inside all you want. But if it loads compiled, then you only have access to the exported symbols. The reason is because of inlining optimizations; you know about the encapsulation of the module when you compile it, and you can optimize the memory and code usage based on compiling functions that are not exported differently. That's my weak understanding, at least.
Luke
Great. Cleaning before loading into ghci works. Thanks, Peter.