<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Here is the language report of Oberon89<div><a href="https://www.research-collection.ethz.ch/bitstream/handle/20.500.11850/68899/eth-3205-01.pdf?sequence=1&isAllowed=y">https://www.research-collection.ethz.ch/bitstream/handle/20.500.11850/68899/eth-3205-01.pdf?sequence=1&isAllowed=y</a></div><div><br>No DEFINITION nor IMPLEMENTATION. Very close to Oberon90. BYTE is still in the language not in SYSTEM yet.</div><div><br><div dir="ltr">br<br><div>Jörg</div></div><div dir="ltr"><br><blockquote type="cite">Am 03.01.2020 um 08:41 schrieb Joerg <joerg.straube@iaeth.ch>:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><span>I tried to quickly collect the differences of Oberon87 and Oberon90. Perhaps I missed some:</span><br><span>1) What is exported?</span><br><span> 87: mentioned in DEFINITION</span><br><span> 90: declaration marked with *</span><br><span>2) What is a string?</span><br><span> 87: enclosed by “ “ or ‘ ‘</span><br><span> 90: enclosed by “ “</span><br><span>3) reserved words</span><br><span> 87: 31+CLOSE, DEFINITION, IMPLEMENTATION</span><br><span> 90: 31+MODULE</span><br><span>4) predefined identifier</span><br><span> 87: 29 + BYTE, ADR, LSH, ROT</span><br><span> 90: 29 + BYTE (this is a typo in the report!!)</span><br><span>5) Module SYSTEM</span><br><span> 87: no</span><br><span> 90: yes (ADR, LSH, ROT, BYTE, BIT, VAL, NEW)</span><br><span>6) WHILE with ELSIF</span><br><span> 87: yes</span><br><span> 90: no</span><br><span>7) formal parameter for any actual parameter</span><br><span> 87: ARRAY OF BYTE</span><br><span> 90: ARRAY OF SYSTEM.BYTE</span><br><span>8) LEN(v) equivalent to LEN(v, 0)</span><br><span> 87: no</span><br><span> 90: yes</span><br><span>9) alias import</span><br><span> 87: IMPORT M : M0;</span><br><span> 90: IMPORT M := M0;</span><br><span></span><br><span>br</span><br><span>Jörg</span><br><span></span><br><blockquote type="cite"><blockquote type="cite"><span>Am 02.01.2020 um 10:54 schrieb Nemo Nusquam <cym224@gmail.com>:</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>On 01/01/20 18:25, Chris Burrows wrote (in part):</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>The first time I heard of Oberon was when the article "From Modula to Oberon" was posted on the bulletin board of the Journal of Pascal, Ada and Modula-2. It was timestamped Tue Feb 23 20:43:46 1988.</span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>There was an article in SP&E vol 18,7 pp 671-690, Jul 1988 (with corrections in vol 19,1 Jan 1989) that specified an Oberon with separate definition/implementation modules.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>N.</span><br></blockquote><blockquote type="cite"><span>--</span><br></blockquote><blockquote type="cite"><span>Oberon@lists.inf.ethz.ch mailing list for ETH Oberon and related systems</span><br></blockquote><blockquote type="cite"><span>https://lists.inf.ethz.ch/mailman/listinfo/oberon</span><br></blockquote><span></span><br><span>--</span><br><span>Oberon@lists.inf.ethz.ch mailing list for ETH Oberon and related systems</span><br><span>https://lists.inf.ethz.ch/mailman/listinfo/oberon</span><br></div></blockquote></div></body></html>