[Oberon] Module aliases - what is the correct way to handle them

Joerg joerg.straube at iaeth.ch
Mon Jul 13 15:27:10 CEST 2020

Hi Peter

Although you didn‘t ask me, here another method to switch output: LinzOberon offers the „version elements“ (http://www.ssw.uni-linz.ac.at/Services/Downloads/#oberon)

Version elements allow managing several versions of your module in the same source.
It can be used to have a Windows and a Unix version of your module in the same source.
And it can be used to have a plain and a debug version of your module.

It‘s like conditional compiling in C.

The elems extension to Texts.Mod (needed by version elems) is not ported to ProjectOberon (yet?)


> Am 13.07.2020 um 14:38 schrieb peter at easthope.ca:
> Andreas,
> From:    Andreas Pirklbauer <andreas_pirklbauer at yahoo.com>
> Date:    Fri, 14 Feb 2020 16:10:20 +0100
>> ... module aliases may be useful in some cases. 
> Pardon my curiosity.  
> Paul Reed mentioned the tidy method of deactivating a module by 
> aliasing to a stub. The immediate objective was to deactivate test 
> output.  An acceptable use for aliasing?
> Without aliasing, a constant can activate or deactivate output.  Paul 
> hinted at risk in that.  
> Have you another way to switch output?  
> Thanks,                                ... P.
> -- 
> https://en.wikibooks.org/wiki/Medical_Machines
> https://en.wikibooks.org/wiki/Oberon
> Tel: +1 604 670 0140            Bcc: peter at easthope. ca
> --
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
> https://lists.inf.ethz.ch/mailman/listinfo/oberon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.inf.ethz.ch/pipermail/oberon/attachments/20200713/48cdf22c/attachment.html>

More information about the Oberon mailing list