[Oberon] Module contexts in Original Oberon 2013

[Jörg]

Additional remark:
If you want to test different versions of your modules another common method
is to use the existing alias method for IMPORT.

IMPORT Display := S3Display;
or
IMPORT Display := Win32Display;

In your module, you then use "Display.Dot". To toggle implementations, you
only need to change the IMPORT and the rest of your code is untouched.
I used this method when I implemented colors for ProjectOberon: I had an
intermediate Display.Mod to test my color procedures but VID.v still
rendering B/W.

br
Jörg

-----Original Message-----
From: Oberon [mailto:oberon-bounces at lists.inf.ethz.ch] On Behalf Of Jörg
Sent: Monday, May 07, 2018 9:31 PM
To: 'ETH Oberon and related systems' <oberon at lists.inf.ethz.ch>
Subject: Re: [Oberon] Module contexts in Original Oberon 2013

Hi

Ideas and concepts missing or discussed in ProjectOberon and Andreas is
ready to spend some time on, are implemented in his "Experimental Oberon".
Some of the modifications are implementation optimizations or get rid of
compiler restrictions without influence on the language itself. And some of
the modification (like contexts) enhance / modify the Oberon-07 language.

My personal view: without contexts you still have the possibility to group
your files by prefixing them (just without dot). Win32Display.Mod,
S3Display.Mod etc. Running different modules with the same name next to each
other is a very rare case; I mean: running the Oberon OS in the Bluebottle
OS is not a very common use case.


But your question: What repository to take is indeed a good one?

Unfortunately, the existing ProjectOberon page is good for distribution (get
the latest files NW wrote) but not for contribution (get improvements others
wrote).

br
Jörg

-----Original Message-----
From: Oberon [mailto:oberon-bounces at lists.inf.ethz.ch] On Behalf Of Skulski,
Wojciech
Sent: Monday, May 07, 2018 7:27 PM
To: ETH Oberon and related systems <oberon at lists.inf.ethz.ch>
Subject: Re: [Oberon] Module contexts in Original Oberon 2013

Andreas wrote:

> For those who want to play around with "module contexts", 
> they are now also available in Original Oberon 2013:

How can I understand "Original Oberon 2013" and "now"? Now it is 2018. Your
message is suggesting that you just implemented this feature, which is
great. But this makes "Original Oberon 2013" neither original nor 2013. 

I am afraid that from now on we will have "original Original" and "modified
Original", as well "original 2013" as well as "2018 version of 2013". It
will be confusing. 

Also, how about the repositories? Which repository should become "the"
repository to copy the files from?

How does this development relate to Experimental Oberon? 

Since we are planning the next step of the RiskFive (real soon now ;-)
starting from the "latest greatest" Oberon sources, we will want to start
from the "true latest greatest". Which are they? Original Original 2013,
2018 version of Original 2013, or Experimental Oberon?

You can imagine how we will hurt our project if start from the wrong "latest
greatest". It is a very practical concern for us.

Thank you,
Wojtek
--
Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
https://lists.inf.ethz.ch/mailman/listinfo/oberon

--
Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
https://lists.inf.ethz.ch/mailman/listinfo/oberon