[Oberon] Safe module unloading (was: Re: Oberon for a C++ user.)
chris
chris at gcjd.org
Sat Oct 8 18:08:30 CEST 2016
On Fri, 7 Oct 2016 00:30:08 +0200, Andreas Pirklbauer wrote:
> Solution #2 ('check for references and don't unload if there are
> any') is implemented in Experimental Oberon, eliminating inadvertent
> references to unloaded modules via installed procedures.
Looks very good and not too difficult. Do you have some experience how
it works in practice? Does the problem occur, that you cannot unload
and cannot fix it?
My suspicion was, that if you want to unload a set of related modules
they would block each other. That's why I suggested (yesterday I think)
to postpone the refusal until reload time, so that you could unload a
bunch of modules.
Greetings, chris
More information about the Oberon
mailing list