Search found 54 matches
- Tue Mar 11, 2014 10:37 am
- Forum: Oberon Language
- Topic: Exported pointer variables
- Replies: 15
- Views: 95373
Re: Exported pointer variables
Variables are always exported in read-only mode. This is good news, at least for non-pointer variables. It implies that each exported constant can be changed to an exported variable (if its value needs to be computed at run-time) without changing the client modules. Before we could not export chara...
- Tue Mar 11, 2014 9:36 am
- Forum: Oberon Language
- Topic: Updated Oberon Language Report (Revision 1.10.2013)
- Replies: 21
- Views: 140997
Re: Updated Oberon Language Report (Revision 1.10.2013)
Niklaus Wirth updated the report in February (unfortunately without changing the date). In the current revision 1. the scale factor with "D" has been partially removed 2. all kinds of variables can now be exported (in read-only mode) 3. the grammar symbol for constant declarations is now consistentl...
- Tue Mar 11, 2014 9:23 am
- Forum: Oberon Language
- Topic: Updated Oberon Language Report (Revision 1.10.2013)
- Replies: 21
- Views: 140997
Re: Updated Oberon Language Report (Revision 1.10.2013)
The "D" in the scale factor has bee removed from section 3, yes, but not from the grammar in the appendix. The reason for this according to Wirth is that he didn't want to "invalidate old data sets".It has now been removed.
- Fri Dec 13, 2013 9:38 am
- Forum: Oberon Language
- Topic: Nested procedures
- Replies: 23
- Views: 130023
Re: Nested procedures
OK, I thought every identifier belonged to exactly one scope. Your example does make sense if that was the case.
- Wed Dec 11, 2013 1:57 pm
- Forum: Oberon Language
- Topic: Nested procedures
- Replies: 23
- Views: 130023
Re: Nested procedures
If I understand it correctly even simple recursion in a local procedure like
is not allowed in Oberon-07/13.
Code: Select all
PROCEDURE P;
PROCEDURE Q;
BEGIN
...
Q
END Q;
BEGIN
Q
END P
- Wed Nov 06, 2013 11:25 am
- Forum: Oberon Language
- Topic: Nested procedures
- Replies: 23
- Views: 130023
Re: Nested procedures
My last message seems to have disappeared. Anyway, to me it's not clear why all access to objects from intermediate scopes are disallowed when variables are the only objects which may cause trouble.
- Thu Oct 31, 2013 9:50 am
- Forum: Oberon Language
- Topic: Updated Oberon Language Report (Revision 1.10.2013)
- Replies: 21
- Views: 140997
Re: Updated Oberon Language Report (Revision 1.10.2013)
Even if the types are compatible they are not "the same".
- Wed Oct 30, 2013 2:02 pm
- Forum: Oberon Language
- Topic: Updated Oberon Language Report (Revision 1.10.2013)
- Replies: 21
- Views: 140997
Re: Updated Oberon Language Report (Revision 1.10.2013)
As far as I understand the compatibility between the type BYTE and the type INTEGER means that e.g. for x: BYTE the statement x := x + 1 is valid but not INC(x). Is this correct? In section 9.1 (Assignments) we are told that: The type of the expression must be the same as that of the designator. In ...
- Tue Oct 29, 2013 11:44 am
- Forum: Oberon Language
- Topic: Updated Oberon Language Report (Revision 1.10.2013)
- Replies: 21
- Views: 140997
Re: Updated Oberon Language Report (Revision 1.10.2013)
OK, only section 3 and the grammar need to be corrected then.
- Tue Oct 29, 2013 9:12 am
- Forum: Oberon Language
- Topic: Updated Oberon Language Report (Revision 1.10.2013)
- Replies: 21
- Views: 140997
Re: Updated Oberon Language Report (Revision 1.10.2013)
As far as I can see the type LONGREAL has only been deleted from section 6.1 in the report; the scale factor D is still in the grammar.