[Oberon] Serious type loophole in type case statements and a possible fix

August Karlstrom fusionfile at gmail.com
Fri Oct 30 20:28:12 CET 2020

On 2020-10-30 15:37, Andreas Pirklbauer wrote:
> Yes, that’s of course the obvious solution. But that would re-introduce run-time
> overhead that the type case statement avoided in the first place. In that case, one
> might as well get rid of the CASE altogether and just use IF p IS T THEN instead:

To me the greatest benefit of type cases is that it makes the code is 
less cluttered and therefor easier to read without the (explicit) type 
guards all over the place.

-- August

More information about the Oberon mailing list