[Oberon] Coding practice

Hans Klaver hklaver at dds.nl
Fri Feb 21 22:57:51 CET 2020

As I found this Omi document Programming Conventions very useful and instructive for 
Oberon and Component Pascal programmers, deserving wider circulation, a few 
years ago I made a .pdf document of it (by means of 'printing to PDF'), which can 
be found here: https://hansklav.home.xs4all.nl/oberon.shtml <https://hansklav.home.xs4all.nl/oberon.shtml>

There you can also find a link to a document that deserves to be better accessable
to the Project Oberon community: the book The Oberon System, User Guide and 
Programmer's Manual, by Martin Reiser. This is the first volume of the 'Oberon Trilogy', 
describing an early (1990) version of the Oberon System in a very clear and informative 
way, imho still useful for the present Project Oberon 2013 user and programmer.

The .pdf file resides on the oberoncore.ru <http://oberoncore.ru/> website.

I own a hardcopy of this book, which I bought in 1991 and which sparked my interest
in Oberon. Not only is it very well written but it is the book with the most attractive lay-out 
of all Oberon books!

Hans Klaver

> The guys at Oberon microsystems published a set of Programming Conventions
> for Oberon/L a.k.a. Component Pascal. It is included in the Help file with
> the Blackbox Component Pascal system. Several possible styles i.e. multiple
> statements on one line, statements split over several lines etc. are
> considered to be good practice. Thankfully, nobody is forced or constrained
> by the Oberon language itself (unlike some languages) to use a prescribed
> programming style. 
> Rather than inventing our own programming conventions, we adopted those,
> with the kind permission of Oberon microsystems, for the Astrobe development
> system. If you do not have access to the original Blackbox document refer to
> Chapter 8. 'Programming Conventions and Guidelines' in the 'ARM Cortex-M
> Oberon Programmers Guide' which you can download from:
> https://www.astrobe.com/Oberon.htm
> When I'm writing new code from scratch then I use my own personal
> preferences (which can change from one month to another!) However, if I am
> making minor modifications to existing code I try to follow the principle of
> 'when in Rome do as the Romans do' and adopt a similar style to the original
> author. If these principles are not followed the result can be code that
> looks as ugly as a one-page document written in 17 different fonts.
> Regards,
> Chris Burrows
> CFB Software
> https://www.astrobe.com
> --
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
> https://lists.inf.ethz.ch/mailman/listinfo/oberon

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.inf.ethz.ch/pipermail/oberon/attachments/20200221/bfcca061/attachment.html>

More information about the Oberon mailing list