[Oberon] Multiple RETURN in a procedure
joerg.straube at iaeth.ch
Mon Oct 24 07:05:52 CEST 2022
This whole discussion boils down to:
„How do I port my code?“
And indeed if language A offers GOTOs and language B does not, to un-spaghetti it needs some work
> Am 24.10.2022 um 03:50 schrieb Skulski, Wojciech <skulski at pas.rochester.edu>:
> Oberon 2013 TextFrames are nowhere near Linz V4 TextFrames. Wirth started from his own original. His task was significantly easier. The fact that he bit the bullet should not be taken as a proof that everyone else should.
> "and he had a choice". He could have chosen to rewrite his TextFrames without changing the language. He could have improved his own code without imposing his convictions on others.
> Here is the definition of "conviction" from Oxford Dictionary: "a formal declaration that someone is guilty of a criminal offense". The "criminal offense" seems to be that we followed the earlier definition of the language.
>> That's a perfect example of why multiple RETURNs should not be allowed. There's a corresponding version of textFrames.Edit in Project Oberon. Wirth apparently believed the improvement to the language outweighed the effort of having to rework it for project Oberon 2013 - and he had a choice. I thank him for having the courage of his convictions.
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
More information about the Oberon