🚀 go-pugleaf

In Oberon-2, variables can be exported as 'read-only' (by adding "-" instead of
"*" in its declaration).  What constraints are imposed on the usage of this
kind of variables while being imported?  Surely it cannot appear on the left
side of an assignment statement.  But can it be passed as a VAR parameter to a
procedure?

Why is the garbage collector a hindrance to the real time applications?  In the
implementation to the run time environment, we can make the garbage collector
as a concurrent process to the 'garbage producer', and find some way to ensure
that the garbage producer does not produce garbage faster than the garbage
collector can consume.  Are there any real language implementations using this
kind of approach?  (Maybe some Ada implementations?)

Hao-yang Wang