<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">ETHOberon is written in Oberon-2, as LinzOberon.<br><br><div dir="ltr"><div>JΓΆrg</div></div><div dir="ltr"><br><blockquote type="cite">Am 11.01.2021 um 23:34 schrieb Liam Proven <lproven@gmail.com>:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr">ο»Ώ<div dir="ltr">On Mon, 11 Jan 2021 at 21:09, Chris Burrows <<a href="mailto:chris@cfbsoftware.com">chris@cfbsoftware.com</a>> wrote:<br>><br>> This is potentially confusing now that 'emulators' for Project Oberon exist.<br>> They are different beasts altogether. Further to Paul's comments, at the<br>> risk of being picky I would rephrase what you said as:<br>><br>> "Native Oberon is one platform of what was originally called Oberon System 3<br>> (S3 - it was never called V3) and was later renamed to ETH-Oberon. There are<br>> others hosted on Windows, MacOS and Linux and revived by Peter Matthias as<br>> the Oberon Linux Revival (OLR) ...<br>><br>> Oberon V4, aka Linz Oberon only runs on bare hardware on the ETH Ceres<br>> computer (which uses the National Semiconductor NS32xxx CPU) but is also<br>> hosted on MS-Windows, Solaris (68K and Sparc), HP-UX, Irix, Amiga, OS2 ..."<br>><br>> My main point is that none of these systems are 'emulated'. In every case<br>> instructions generated by the Oberon compiler are natively executed by the<br>> CPU on the target platform.<br>><br>> On the other hand, AFAIK, currently all versions of Project Oberon running<br>> on Windows, MacOS, Linux etc. ARE emulated. In this case, the compiler<br>> generates RISC5 instructions that are then 'interpreted' by a software<br>> emulation of the RISC5 CPU. Each RISC5 instruction results in tens<br>> (hundreds?) of Intel (or whatever CPU is being used to run the OS) CPU<br>> instructions being executed.<br>><br>> Note that Project Oberon running on FPGA hardware is not emulated. Every<br>> RISC5 instruction generated by the compiler is executed directly by the<br>> RISC5 CPU implemented in configurable hardware.<br>><br>> It's as clear as mud ... ;-)<br><br>Useful clarification -- thank you!<div><br></div><div>I must admit, I don't feel so bad about getting it wrong now! π </div><div><br></div><div>I also note that various people have done a lot more work on the Wikipedia article about Oberon, and that it's a whole year since I last worked on it. I feel a bit guilty about that. There's a version history table in there now, but IMHO it still needs a bit more info.</div><div> </div><div>I think I now understand the relationship, more or less, between:</div><div><br></div><div>β’ Oberon System 3, AKA ETH Oberon β on x86 (Native Oberon) & hosted on x86</div><div>β’ Oberon V4, AKA Linz Oberon β implemented in Oberon 2 β on Ceres & hosted on x86</div><div>β’ AOS, AKA Bluebottle, AKA A2 β implemented in Active Oberon β on x86, ARM and hosted</div><div>β’ Project Oberon, AKA Oberon V5 β implemented in Oberon-07 β on RISC5 & emulators</div><div><br></div><div>Is that right?</div><div><br></div><div>What is ETH Oberon written in? Original Oberon, what we might call Oberon 1?</div><div><br></div><div>-- <br>Liam Proven β Profile: <a href="https://about.me/liamproven">https://about.me/liamproven</a><br>Email: <a href="mailto:lproven@cix.co.uk">lproven@cix.co.uk</a> β gMail/gTalk/gHangouts: <a href="mailto:lproven@gmail.com">lproven@gmail.com</a><br>Twitter/Facebook/LinkedIn/Flickr: lproven β Skype: liamproven<br>UK: +44 7939-087884 β ΔR (+ WhatsApp/Telegram/Signal): +420 702 829 053</div></div>
<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></body></html>