[Oberon] Module contexts in Original Oberon 2013

[Andreas Pirklbauer]

   > Additional remark: If you want to test different versions
   > of your modules another common method is to use the
   > existing alias method e.g., IMPORT Display := S3Display;
   > [...]
   > My personal view: without contexts you still have the
   > possibility to group your files by prefixing them (just
   > without dot), e.g., Win32Display.Mod
   > [...]
   > Running different modules with the same name
   > next to each other is a very rare case.


Jörg,

You have convinced me. There are other mechanisms to
group modules that don’t require a language change.

OTOH, I may not be familiar with some other use
cases that might exist on other systems currently
being used. Any input from A2 users?

-ap