<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">As I found this Omi document <i class="">Programming Conventions</i> very useful and instructive for </div><div class="">Oberon and Component Pascal programmers, deserving wider circulation, a few </div><div class="">years ago I made a .pdf document of it (by means of 'printing to PDF'), which can </div><div class="">be found here: <a href="https://hansklav.home.xs4all.nl/oberon.shtml" class="">https://hansklav.home.xs4all.nl/oberon.shtml</a></div><div class=""><br class=""></div><div class="">There you can also find a link to a document that deserves to be better accessable</div><div class="">to the Project Oberon community: the book <i class="">The Oberon System</i>, <i class="">User Guide and </i></div><div class=""><i class="">Programmer's Manual</i>, by Martin Reiser. This is the first volume of the 'Oberon Trilogy', </div><div class="">describing an early (1990) version of the Oberon System in a very clear and informative </div><div class="">way, imho still useful for the present Project Oberon 2013 user and programmer.</div><div class=""><br class=""></div><div class="">The .pdf file resides on the <a href="http://oberoncore.ru" class="">oberoncore.ru</a> website.</div><div class=""><br class=""></div><div class="">I own a hardcopy of this book, which I bought in 1991 and which sparked my interest</div><div class="">in Oberon. Not only is it very well written but it is the book with the most attractive lay-out </div><div class="">of all Oberon books!</div><div class=""><br class=""></div><div class="">--</div><div class="">Hans Klaver</div><div class=""><br class=""></div><br class=""><div><blockquote type="cite" class=""><div class=""><div class="">The guys at Oberon microsystems published a set of Programming Conventions<br class="">for Oberon/L a.k.a. Component Pascal. It is included in the Help file with<br class="">the Blackbox Component Pascal system. Several possible styles i.e. multiple<br class="">statements on one line, statements split over several lines etc. are<br class="">considered to be good practice. Thankfully, nobody is forced or constrained<br class="">by the Oberon language itself (unlike some languages) to use a prescribed<br class="">programming style. <br class=""><br class="">Rather than inventing our own programming conventions, we adopted those,<br class="">with the kind permission of Oberon microsystems, for the Astrobe development<br class="">system. If you do not have access to the original Blackbox document refer to<br class="">Chapter 8. 'Programming Conventions and Guidelines' in the 'ARM Cortex-M<br class="">Oberon Programmers Guide' which you can download from:<br class=""><br class=""><a href="https://www.astrobe.com/Oberon.htm" class="">https://www.astrobe.com/Oberon.htm</a><br class=""><br class="">When I'm writing new code from scratch then I use my own personal<br class="">preferences (which can change from one month to another!) However, if I am<br class="">making minor modifications to existing code I try to follow the principle of<br class="">'when in Rome do as the Romans do' and adopt a similar style to the original<br class="">author. If these principles are not followed the result can be code that<br class="">looks as ugly as a one-page document written in 17 different fonts.<br class=""><br class="">Regards,<br class="">Chris Burrows<br class="">CFB Software<br class="">https://www.astrobe.com<br class=""><br class=""><br class="">--<br class="">Oberon@lists.inf.ethz.ch mailing list for ETH Oberon and related systems<br class="">https://lists.inf.ethz.ch/mailman/listinfo/oberon<br class=""></div></div></blockquote></div><br class=""></body></html>