Search found 32 matches

by kevinhely
Wed Oct 30, 2013 5:29 pm
Forum: Oberon Language
Topic: Updated Oberon Language Report (Revision 1.10.2013)
Replies: 21
Views: 81105

Re: Updated Oberon Language Report (Revision 1.10.2013)

I suspect that the section needs to be amended with an exception...
I guess that's covered by
The type BYTE is compatible with the type INTEGER, and vice-versa.
in Section 6.1 of the report.
by kevinhely
Wed Oct 30, 2013 5:26 pm
Forum: Oberon Language
Topic: Updated Oberon Language Report (Revision 1.10.2013)
Replies: 21
Views: 81105

Re: Updated Oberon Language Report (Revision 1.10.2013)

That's good as we had already removed it from the compiler
Heh heh! Ditto!
by kevinhely
Tue Oct 29, 2013 1:26 pm
Forum: Oberon Language
Topic: Updated Oberon Language Report (Revision 1.10.2013)
Replies: 21
Views: 81105

Re: Updated Oberon Language Report (Revision 1.10.2013)

Wirth said it was an oversight to leave the "D" business in the report. It will be removed shortly.
by kevinhely
Fri Oct 25, 2013 1:39 am
Forum: Oberon Language
Topic: Updated Oberon Language Report (Revision 1.10.2013)
Replies: 21
Views: 81105

Re: Updated Oberon Language Report (Revision 1.10.2013)

Really?

From the Oberon report (section 6, first sentence):
A data type determines the set of values which variables of that type may assume, and the operators that are applicable.
by kevinhely
Thu Oct 24, 2013 4:34 pm
Forum: Oberon Language
Topic: Updated Oberon Language Report (Revision 1.10.2013)
Replies: 21
Views: 81105

Re: Updated Oberon Language Report (Revision 1.10.2013)

Hi,
The type BYTE is compatible with type INTEGER, and vice-versa.
I guess that means that a runtime check has to be performed for every assignment to a variable of type BYTE, right (except if the expression is a constant)?

K
by kevinhely
Wed Jul 03, 2013 2:30 pm
Forum: Oberon Language
Topic: Nested procedures
Replies: 23
Views: 84367

Re: Nested procedures

Hi, 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. Rega...
by kevinhely
Tue Jun 25, 2013 1:45 pm
Forum: Oberon Language
Topic: Nested procedures
Replies: 23
Views: 84367

Re: Nested procedures

Oh, I've read the associated documentation and I certainly don't think it would make sense to implement local-only access to variables. I can live with the strictly-global-or-strictly-local restriction but, once again, the wording of the report leaves a lot to be desired. :roll:

Thanks,
K
by kevinhely
Mon Jun 24, 2013 11:26 pm
Forum: Oberon Language
Topic: Nested procedures
Replies: 23
Views: 84367

Re: Nested procedures

Hi
... the objects declared in the environment of the procedure are also visible in the procedure (with the exception of variables and
of those objects that have the same name as an object declared locally).
Does this formulation not rule out access to global variables?

K
by kevinhely
Sun Jan 13, 2013 7:59 pm
Forum: Oberon Language
Topic: Comparing pointers (including extensions)
Replies: 4
Views: 16882

Re: Comparing pointers (including extensions)

I took the same view in my compiler. It's just the lack of precision in the official definition that bugs me...
by kevinhely
Sun Jan 13, 2013 2:55 am
Forum: Oberon Language
Topic: Record fields / Array elements as VAR parameters
Replies: 2
Views: 11333

Re: Record fields / Array elements as VAR parameters

No. This is addressed by a section (9.2) on procedure call that I'd forgotten about: In the case of variable parameters, the actual parameter must be a designator denoting a variable. If it designates an element of a structured variable, the selector is evaluated when the formal/actual parameter sub...