[Oberon] OP2 Vs Wirth's compiler.

Josef Templ josef.templ at gmail.com
Mon Jul 31 15:52:13 CEST 2017

Besides the abstract syntax tree construction, one difference between OP2
and the original NW Oberon
compiler is the compatibility checking across module boundaries.
In OP2 there is a separate key (fingerprint) per exported object while in
the original compiler there is a single key
per module. Thus, whenever anything in a module is changed all clients are
invalidated. In OP2 only clients that
are using the changed object are invalidated. I don't know how this is
handled in the latest RISC5 compiler.

- JT
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.inf.ethz.ch/pipermail/oberon/attachments/20170731/7d401a79/attachment.html>

More information about the Oberon mailing list