[Oberon] Completeness; Ceres.
joerg.straube at iaeth.ch
Thu May 3 22:37:32 CEST 2018
Contexts are meant to separate modules with a name in one Oberon OS from the module with same name in another Oberon OS.
The legacy Oberon OS gets the context „Oberon“ and the new Bluebottle/A2 OS (coded in the programming language Active Oberon, a dialect of Oberon) gets the context „A2“
Here a little bit of background of the introduction of contexts in the language Active Oberon. Contexts do not exist in the legacy programming language Oberon.
Basically it’s a SW thing.
Now, Ceres is a HW build at ETH where an Obern OS is running on. As contexts have someting to do with SW, but Ceres is a HW, I don’t see a reason to defne a new context for the Ceres HW.
> Am 03.05.2018 um 17:07 schrieb <peter at easthope.ca> <peter at easthope.ca>:
> Appears that Ceres was important enough and different
> enough from later systems to have a context identifier.
> It would give the system the distinction it deserves
> and allow unambiguous reference on the same basis as
> later variants.
> Comments? Suggestions?
> Something else?
> Thanks, Lyall E.
> This message was composed and transmitted by software designed to
> avoid the need, overhead and vulnerability of antivirus software.
> 123456789 123456789 123456789 123456789 123456789 123456789 123456789
> Tel: +1 360 639 0202 Pender Is.: +1 250 629 3757
> http://easthope.ca/Peter.html Bcc: peter at easthope. ca
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Oberon