[Oberon] Oberon for a C++ user.

[Douglas G. Danforth]

On 10/6/2016 8:45 AM, chris wrote:
> 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.
The initial state of a procedure variable (I believe) is NIL.  The 
module which exports the procedure variable
should (in my opinion) handle the case of NIL without trapping.  The NIL 
case is exactly the case when no
module uses (assigns) the procedure variable.  Hence any module which 
exports a procedure variable
must handle the NIL case quietly.