[Oberon] Volatile variables in Oberon

[Skulski, Wojciech]

Joerg and Bernhard:

thank you for the very helpful discussion. I duly saved your e-mails for future reference. I would not decipher these tricks from the SYSTEM description in the language report. Your insight was very helpful.

I quickly scanned the Project Oberon from the NW website looking for implementation hints which you outlined. I did not find this discussion anywhere (excuse me if I skipped it). The NW book does not go into this level of implementation detail. I would be great if a short app note was available illustrating HW access via volatile memory structures using your examples. 

Thank you for your help.

Wojtek

________________________________________
From: Treutwein Bernhard [Bernhard.Treutwein at Verwaltung.Uni-Muenchen.DE]
Sent: Monday, August 1, 2016 6:46 AM
To: 'ETH Oberon and related systems'
Subject: RE: [Oberon] Volatile variables in Oberon

Hi Wojciech,

> a high level Oberon array carries the hidden memory tag.

Yes, but as far as I know all recent implementation have the hidden
type tags at negative address offsets. You must know these
implementation details and you are absolutely correct that these are
dirty tricks. Therefore the IMPORT SYSTEM is essential, but I think these
tricks are essential for hardware programming.

--
  Bernhard