Flylib.com

Books Software

 
 
 

2 Conformance


2 Conformance

A system claiming conformance to this International Standard shall implement all the mandatory requirements of this standard, and shall specify the profile (see Partition IV) that it implements. The minimal implementation is the Kernel Profile (see Partition IV). A conforming implementation may also include additional functionality that does not prevent running code written to rely solely on the profile as specified in this standard. For example, it may provide additional classes, new methods on existing classes, or a new interface on a standardized class, but it shall not add methods or properties to interfaces specified in this standard.

A compiler that generates Common Intermediate Language (CIL, see Partition III) and claims conformance to this International Standard shall produce output files in the format specified in this standard and the CIL it generates shall be valid CIL as specified in this standard. Such a compiler may also claim that it generates verifiable code, in which case the CIL it generates shall be verifiable as specified in this standard.


3 References

ANNOTATION

In the International Standard, this section contains references used in the standard. In this book, the references are at the end of the volume.



4 Conventions

The remainder of this section contains only informative text.


4.1 Organization

The divisions of this International Standard are organized using a hierarchy. At the top level is the Partition. The next level is the Chapter , followed by section then clause . Divisions within a clause are also referred to as clauses rather than subclauses. Partitions are numbered using Roman numerals. All other divisions are numbered using Arabic digits, with their place in the hierarchy indicated by nested numbers . For example, Partition II, 14.4.3.2 refers to clause 2 in clause 3 in section 4 in Chapter 14 in Partition II.

ANNOTATION

To avoid confusion with the use of the term "Chapter," the hierarchical designation used in the International Standard is not used in this book. In this book, only the book chapters are referred to as "Chapter." Sections within partitions are all called "sections," but they are given the full numeric designation—for example, "see Partition I, section 12.4.2.3."


4.2 Informative Text

This International Standard is intended to be used by implementers, academics , and application programmers. As such, it contains explanatory material that, strictly speaking, is not necessary in a formal specification.

Examples are provided to illustrate possible forms of the constructions described. References are used to refer to related sections. Notes are provided to give advice or guidance to implementers or programmers. Annexes provide additional information.

Except for whole sections that are identified as being informative, informative text that is contained within normative sections is identified as follows :

The beginning and end of informative text is marked as shown in this chapter, using pairs of narrow horizontal rules. Some informative passages span pages between opening and closing indicators.

4.3 Hyperlinks

The text of this standard contains numerous hyperlinks that are intended to allow a person viewing it electronically to be able to transfer to the referenced sections. Such hyperlinks are displayed with a double underline, and, depending on the rendered format, may be colored; for example: "see Partition IV ," "see section 8.7 ," "see Chapter 22 ," and "see clause 7.5.3 ." Some tables also contain hyperlinked section number references, such as 5.10 and 6.7 .

ANNOTATION

The hyperlinks in the International Standard are replaced with full references to Partition and section in this book.


End informative text