[Oberon] NAstrobe for RISC5 on Pepino

Andreas Pirklbauer andreas_pirklbauer at yahoo.com
Sat Aug 4 02:11:57 CEST 2018

     > > Except that FPGA Oberon does NOT actually check whether such 
     > > references exist - i.e. it *always* unloads the specified modules, no 
     > > matter whether other modules reference them or not. 
     > 'always’ ?

Yes, always .. except if client modules exist of course :)

Perhaps I should have specified the terminology (mea
culpa…) one can also (and perhaps should?) define the
term “reference to a module M” more broadly, namely:

Apart from client references (where another module
imports M), references to a module can also be in the
form of type tags (addresses of type descriptors) in
dynamic objects of other modules (allocated via the
predefined procedure NEW) pointing to descriptors
of types declared in the module, or in the form of
procedure variables installed in static or dynamic
objects of other modules referring to procedures
declared in the module.

So one has the following types of “references”:

1. Client reference
2. Type (tag) references
3. Procedure (variable) references

FPGA Oberon checks only 1., but not 2. or 3.


More information about the Oberon mailing list