[Oberon] [EXT] Portability of Project Oberon

Skulski, Wojciech skulski at pas.rochester.edu
Tue Dec 8 22:31:14 CET 2020


  I will do it then. I will still use BlackBox for creating master files with color. I would prefer using V4 Text, bu BlackBox cannot write V4 Text. It can only read.  Maybe someone knows how to write V4 Text format from under BlackBox?

From: Oberon [oberon-bounces at lists.inf.ethz.ch] on behalf of Andreas Pirklbauer [andreas_pirklbauer at yahoo.com]
Sent: Tuesday, December 8, 2020 3:04 PM
To: Oberon List
Subject: [EXT] [Oberon]  Portability of Project Oberon

    > >Your effort of collecting all low level values and document them in one file is appreciated.
    > [...] Who is going to use what I have done? The collection was released 10 months ago.
    > > But ONE big SysDef.Mod is NOT a good idea.
    > I agree. Remembering your advice I wrote "file or files". My proposition is that cleanup is much needed.
    > The details are less important. I am not standing behind a single file, or a name SysDef.

I’d probably consider using those Def files in Extended Oberon, if only the one large SysDef.Mod file
were split into several smaller ones, as Jörg had suggested, e.g. DevDef, RegDef, MemDef, etc. It
would have to be a sensible choice though, which minimizes recompilations of one of them changes.

But one big SysDef file is a no-go. An import (which has a key) is NOT an include file used in C.


Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems

More information about the Oberon mailing list