[Oberon] Module contexts in Original Oberon 2013

Andreas Pirklbauer andreas_pirklbauer at yahoo.com
Mon May 7 22:37:32 CEST 2018

  > 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.

Hi Jörg,

I agree. Which is why I hesitated to actually implement module contexts
in the first place - until I realized that its implementation is absolutely trivial
(only a few lines of code, <30min of work) if only one accepts the restriction
that a module belonging to a context C can only import modules belonging
to the same context (and vice versa). This restriction appears acceptable
because - as you stated - running Oberon OS on Bluebottle OS is rare…

But in the case, module context is just a file selection mechanism..


More information about the Oberon mailing list