You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note that the only deliberate change from the specification is for `SUBROUTINE` parameters needing to be followed by `: Type` (as for `RECORD` fields), but not where the `SUBROUTINE` is called with arguments.
95
+
Note that the only deliberate changes from the specification are:
96
96
97
-
**Update:** Compound assignment of `RECORD`s now appears in the specification above, as does `OUTPUT`ing of a comma-separated list of `StringExp`s. Support for both of these is anticipated in a future release.
97
+
*`SUBROUTINE` parameters in a definition needing to be followed by `: Type` (as for `RECORD` fields), but not where the `SUBROUTINE` is called with arguments.
98
+
99
+
* Initiializing a variable from a `RECORD` type needs curly braces `{` and `}` and not plain parentheses, this is due to the earlier design of the compiler which means it cannot otherwise distinguish from a `SUBROUTINE` call (with the name of the `RECORD`)
100
+
101
+
102
+
**Update:** Compound assignment of variables from `RECORD`s (in addition to field assignment) now appears in the specification above, as does `OUTPUT`ing of a comma-separated list of `StringExp`s. Support for both of these is provided.
0 commit comments