On: Project Oberon Emulator in JavaScript and Java

[Rochus]

Thanks, interesting; I have looked through the PhD report, but think that Active Oberon only addresses a fraction of the issues; e.g. the "loopholes" described in section 4.4.3 are still present even in more recent Oberon versions; and issues like low level bit manipulation were apparently not the topic of the PhD, but only addressed recently (in http://cas.inf.ethz.ch/projects/a2/repository/raw/trunk/Lang... or my version of the language).

[pjmlp → Rochus]

Active Oberon also addresses having better mechanisms for finalization and untraced references, which allows for more fine grained memory management.