[Oberon] Fwd: Re: Re: Question about Oberon semantics of VAR parameters

[rochus.keller at bluewin.ch]

Ok, I see, thank you very much.

 It should be officially documented in any case. I'm implementing my first true Oberon validator by just following the language report word by word and got tons of inexplicable errors because of rule simply not describe there (neither in the tutorial). If I want to be able to successfully parse the Oberon System (which seems like an obligatory test case) then I consequently have to implement these specialities as well. I'm not very good at reading Oberon source code (yet) though, so I would prefer a precise and complete language report. Your document is already more precise, as it seems.

Best
R.

_______________________________
From: Luca Boasso
Sent on: Sat, 07 Dec 2019 03:02:01 +0100
To: rochus.keller at bluewin.ch
Cc: 
Subject: Re: [Oberon] Fwd: Re: Re: Question about Oberon semantics of VAR parameters

Those particular examples exploit an undocumented loophole in the type system that simplify the writing of lower lever functions. I left that out of my document.


See ORP.Parameter:
ELSIF (par.type.form = ORB.Array) & (par.type.base = ORB.byteType) & 
          (par.type.len >= 0) & (par.type.size = x.type.size) THEN
        ORG.VarParam(x, par.type)




On Fri, Dec 6, 2019, 17:45 rochus.keller at bluewin.ch <rochus.keller at bluewin.ch> wrote:

This is a very helpful document indeed, thank you very much. 

But as it seems it doesn't explain my originally intended examples, e.g FileDir.Mod line 61 or Files.Mod line 104 (the first reported one was unfortunately my mishap, sorry).

Best
R.