Astrobe Forum

Hi, I think you're referring to a question I posted but then deleted because I discovered it had already been answered earlier on this forum. The summary you link to mixes up types and type identifiers, and defines "same type" for two variables but then uses the term "same type" in a context that do...

I would have thought so but it contradicts the quoted statement.

Hi again, The language definition states: The use of the procedure identifier in a call within its declaration implies recursive activation of the procedure. That would seem to rule this out as legitimate code: PROCEDURE P; PROCEDURE P; END P; (*local*) BEGIN P (*which P does this refer to?*) END P;...

Thanks for that. Yes, from the latest revision of the report: In addition to its formal parameters and locally declared objects, the objects declared globally are also visible in the procedure agrees with the quote you gave from PO2013, if the phrase "locally declared objects" means "objects declare...

Ok, thanks for that. An interesting discussion. I need to get on that list!

Hi, The following code: PROCEDURE P;  PROCEDURE Q; (*local*)    ...  END Q;  PROCEDURE R; (*local*)  BEGIN    ...    Q    ...  END R; END P; is disallowed by the definition of Oberon07, that is, local procedure R cannot call local procedure Q, since the identifier Q is not local to R and not global....

Can an open array be the target of an assignment? From the Report: "The type of the expression must be the same as that of the designator" and "Strings can be assigned to any array of characters..." Here's a question: if an open array is assigned to an array of equal base type but shorter length, i...

(I assume that qualident still cannot be a basic type.)

Why? INTEGER is a qualident.

The Oberon report has been updated. <= and >= no longer apply to SET arguments AFAICS. (See section 8.2.4)

Langugae report is now much clear

Hmm. I think the report should say:

In addition to its formal parameters and locally declared objects, the objects declared globally are also visible in the procedure (except objects whose identifiers coincide with those of locally declared objects).