I guess that's covered byI suspect that the section needs to be amended with an exception...
in Section 6.1 of the report.The type BYTE is compatible with the type INTEGER, and vice-versa.
I guess that's covered byI suspect that the section needs to be amended with an exception...
in Section 6.1 of the report.The type BYTE is compatible with the type INTEGER, and vice-versa.
Heh heh! Ditto!That's good as we had already removed it from the compiler
A data type determines the set of values which variables of that type may assume, and the operators that are applicable.
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)?The type BYTE is compatible with type INTEGER, and vice-versa.
Does this formulation not rule out access to global variables?... 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).