🚀 go-pugleaf

> 2. Garbage collection.  This is an issue for me, might not be
>    an issue for others.  I work in real-time applications where
>    it's not all that safe to have garbage collection going on
>    behind the scenes.

Agreed. When working with anything critical, it is usually necessary to 
be able to predict at build time exactly what will be where. Any form of 
dynamic allocation can be a right pain, particularly when it comes to 
debugging (unless your target board has a full symbolic post-mortem 
debugger which is highly unlikely). Same reasons apply to the use of C++ 
(and OO extension to Modula-2) in embedded systems.

> One thing that really bugs me about Oberon is the lack of
> separate definition modules.

Little experience here, but ISWYM. One of my gripes about Modula-2 is 
that it is not possible to have a single definition with multiple 
implementations (e.g. for DLLs), and Oberon here seems to be making 
things worse.

Mark Morgan Lloyd
mark_tbu@cix.compulink.co.uk

[Opinions above are the author's, not those of his employers or 
colleagues]