CSA CAN/CSA-ISO/IEC 10514-1-00

Abstract

<strong>Goals</strong> <br>The goals of this part of ISO/lEC 10514 are: <br>To provide a rigorous definition of the language Modula-2 and its standard library by providing a mathematical model of both; <br>To provide a resolution of differences among interpretations of other descriptions of Modula-2 and its standard library, while endeavouring to preserve investment in existing practice; <br>To remove features thought to be redundant, inherently flawed, or inadequate; <br>To specify new language and standard library facilities where a need is perceived to exist; <br>To maintain the general principles of Modula-2laid down by its inventor, while allowing for later modernization and standardization. <br><strong>Specifications included in this part of ISO/lEC 10514</strong> <br>This part of ISO/lEC 10514 provides specifications for: <br>- required symbols for Modula-2 program representation, including comments, literals, and source code directives; <br>The lexical structure, the syntactic structure and the semantics of Modula-2 programs, including programs that make use of system modules. <br>The interface to and the semantics of standard Modula-2 library modules. <br>Those separate modules of the standard library that a conforming implementation is required to supply; <br>- violations of the rules for use of the language, system modules and standard library modules that a conforming implementation is required to detect; <br>- certain criteria for the size and complexity of programs that a conforming implementation must accept; <br>- further compliance requirements for implementations, including documentation requirements. <br><strong>Specifications not within the scope of this part of ISO/lEC 10514</strong> <br>This part of ISO/lEC 10514 provides no specifications for: <br>The underlying representation of predefined data types (except in the case of packedset types; see 7.1.7.1); <br>The method by which implementations are invoked (including identification of the program module and associated definition and implementation modules); <br>The method by which compilation modules are stored (including the correspondence between module names and system file names where files are used); <br>The method by which implementations accept input (including the encoding of source text and including the number of compilation modules accepted for each invocation); <br>- performance aspects of implementations, and certain quality aspects not covered by 1.2; <br>The effect of executing a program that uses extensions to the language, extensions to system modules or extensions to standard library modules, or that otherwise deviates from this part of ISO/IEC 10514; <br>The effect of continuing execution of a program in which an exception has occurred and execution has continued without an exception being raised; <br>The meaning of a program that relies on a definition of implementation-dependent values or implementationdependent behaviour.