[Oberon] ALU 2015 and 2018

[Andreas Pirklbauer]

fd

> > Writing correct code is already demanding enough, but writing publishable (!)
> > code is exacting!
>
>
> Publishable? RISC5 has been published. Are you arguing that this code
> is "publishable" because it was published? Or are you saying this code
> stands by itself as being publishable because of its > clarity?
> Should this code be presented and taught as is? 

Actually, I was making a general comment on comments and how
I (like to) write Oberon - not RISC5 - code.

It was not specifically about RISC5. Whether the RISC5 code as published
today is actually “publishable”, is .. apparently .. a topic of this thread..