[Oberon] Oberon for a C++ user.

[chris]

On Wed, 5 Oct 2016 13:23:52 +0000, Skulski, Wojciech wrote:
> I also seem to remember that the procedure code is in the 2nd heap 
> which is typically much smaller than the heap devoted to records. 
> Traversing the procedure heap should be lightning fast even if the 
> machine has a gigabyte on board. You do not need to scan the entire 
> gigabyte, but rather the code hep only. Correct me if I am mistaken.

Yes, but that was not my point. I don't expect any performance 
problems. What I don' like about this is, what I would consider an 
inconsistent state of the system.

There can be different versions of code for the same procedure  around 
at the same time after an unload / reload cycle of a module. 

I am not sure if this situation is a better solution than writing NIL 
to all references to unloaded procedures so that calling an unloaded 
procedure's code would trap instead of running outdated code which does 
not reflect the actal code of the module as loaded.

Greetings, chris