Jon Jagger
Table of Contents 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 Notes DownloadECMA-334 C# Language Specificationpreviousnextprevious at this levelnext at this level 2 Conformance Paragraph 11 Conformance is of interest to the following audiences: Paragraph 21 As such, conformance is most important, and the bulk of this ECMA Standard is aimed at specifying the characteristics that make C# implementations and C# programs conforming ones. Paragraph 31 The text in this ECMA Standard that specifies requirements is considered normative. 2 All other text in this specification is informative; that is, for information purposes only. 3 Unless stated otherwise, all text is normative. 4 Normative text is further broken into required and conditional categories. 5 Conditionally normative text specifies requirements for a feature such that if that feature is provided, its syntax and semantics must be exactly as specified. Paragraph 41 If any requirement of this ECMA Standard is violated, the behavior is undefined. 2 Undefined behavior is otherwise indicated in this ECMA Standard by the words ''undefined behavior'' or by the omission of any explicit definition of behavior. 3 There is no difference in emphasis among these three; they all describe ''behavior that is undefined.'' 4 A strictly conforming program shall use only those features of the language specified in this ECMA Standard as being required. 5 (This means that a strictly conforming program cannot use any conditionally normative feature.) 6 It shall not produce output dependent on any unspecified, undefined, or implementation-defined behavior. Paragraph 51 A conforming implementation of C# must accept any strictly conforming program. Paragraph 61 A conforming implementation of C# must provide and support all the types, values, objects, properties, methods, and program syntax and semantics described in this ECMA Standard. Paragraph 71 A conforming implementation of C# shall interpret characters in conformance with the Unicode Standard, Version 3.0 or later, and ISO/IEC 10646-1. 2 Conforming implementations must accept Unicode source files encoded with the UTF-8 encoding form. Paragraph 81 A conforming implementation of C# shall not successfully translate source containing a #error preprocessing directive unless it is part of a group skipped by conditional compilation. Paragraph 91 A conforming implementation of C# shall produce at least one diagnostic message if the source program violates any rule of syntax, or any negative requirement (defined as a "shall" or "shall not" or "error" or "warning" requirement), unless that requirement is marked with the words "no diagnostic is required". Paragraph 101 A conforming implementation of C# is permitted to provide additional types, values, objects, properties, and methods beyond those described in this ECMA Standard, provided they do not alter the behavior of any strictly conforming program. 2 Conforming implementations are required to diagnose programs that use extensions that are ill formed according to this ECMA Standard. 3 Having done so, however; they can compile and execute such programs. 4 (The ability to have extensions implies that a conforming implementation reserves no identifiers other than those explicitly reserved in this ECMA Standard.) Paragraph 111 A conforming implementation of C# shall be accompanied by a document that defines all implementation-defined characteristics, and all extensions. Paragraph 121 A conforming implementation of C# shall support the class library documented in §D. 2 This library is included by reference in this ECMA Standard. Paragraph 131 A conforming program is one that is acceptable to a conforming implementation. 2 (Such a program may contain extensions or conditionally normative features.)
{ JSL }
Jagger Software Ltd
Company # 4070126
VAT # 762 5213 42
Valid HTML 4.01Valid CSS