Astrobe Forum

I'm not sure if I'm qualified to partecipate because I don't have Astrobe and neither a platform to test the code. MODULE Quiz; VAR a1*, a2*, init: ARRAY 1000 OF INTEGER; i: INTEGER; PROCEDURE Init*; BEGIN a1 := init; a2 := init END Init; BEGIN FOR i := 0 TO LEN(init) - 1 DO init[i] := i END END Qui...

augustk wrote:Have I missed anything?

The SET type is now:

The sets of integers between 0 and an implementation-dependent limit.

Then we've lost the ability to make mutually recursive procedures if both of them are nested?

In my opinion BYTE and INTEGER shouldn't be assignment compatible, I don't see the need to assign an integer value to byte and viceversa because they are used for different stuff (except for the integer constant). Maybe Wirth did this to avoid a new type conversion function

I contacted Prof. Wirth and he stated that the report does not restrict variables to strictly-local-or-strictly-global access: In Oberon-7 "intermediate level" objects are permitted. However, in my new implementation they cannot be accessed, except from the level in which they are declared. Uhm, I'...

Both Oberon-2 and Component Pascal reports are clear for their read-only export mark: 4. Declarations and Scope Rules [...] Variables and record fields marked with a minus in their declaration are read-only in importing modules. 4. Declarations and Scope Rules [...] Variables and record fields marke...

Uhm, I don't get your interpretation, then you consider public field identifers in a record as read only variables?

Hi, I've studied the Oberon-07/11 report in depth and my interpretation about the export mark is different. The report talks about the export mark in three places, in Declarations and scope rules (Ch. 4), Record Types (Ch. 6.3) and Modules (Ch. 11). In the first one, the export mark refers only to t...