[Oberon] Volatile variables in Oberon

[Chris Burrows]

> -----Original Message-----
> From: Skulski, Wojciech [mailto:skulski at pas.rochester.edu]
> Sent: Saturday, 30 July 2016 3:36 PM
> To: chris at cfbsoftware.com; ETH Oberon and related systems
> Subject: RE: [Oberon] Volatile variables in Oberon
> 
> In Oberon it would be something like this:
> 
>  CONST address = ....;
>   VAR value: INTEGER AT address; (* address must be constant*)
> 
> Now the question, is this unreasonable?
> 

Modula-2 has a feature like that. It is described as a 'loophole' in Wirth's
paper 'Good Ideas, Through the Looking Glass'. 

The benefit of using SYSTEM.PUT and SYSTEM.GET is that it clearly
distinguishes *where the operation is performed* that this is not the usual
form of variable access. 

Regards,
Chris.