☜	Conforming Implementations 1995 Version of ANSI (Equivalent to Current ISO Version) of Standard					☞

3. Conformance
3.1 Implementations

A conforming implementation shall

1. correctly execute all programs conforming to both the Standard and the implementation defined features of the implementation
2. reject all code that contains errors, where such error detection is required by the Standard
3. be accompanied by a document which provides a definition of all implementation-defined features and a conformance statement of the form:

   “xxx version v conforms to X11.1-yyyy with the following exceptions:

   ...

   Supported Character Set Profiles are ...

   Uniqueness of the values of $SYstem is guaranteed by ...”

   where the exceptions are those components of the implementation which violate this Standard or for which minimum values are given that are less than those defined in Section 2.

An MDC conforming implementation shall be a conforming implementation except that the conforming document shall be this Standard together with any such current MDC documents that the vendor chooses to implement. The conformance statement shall be of the form:

An MDC strictly conforming implementation is an MDC conforming implementation whose MDC modification documents only have MDC Type A status and which has no exceptions.

A <National Body> ... implementation is an implementation conforming to one of the above options in which the requirements of Section 2 are replaced by the <National Body> requirements and other extensions required by the <National Body> are implemented.

An implementation may claim more than one level of conformance if it provides a switch by which the user is able to select the conformance level.

Copyright © Standard Documents; 1977-2024 MUMPS Development Committee;
Copyright © Examples: 1995-2024 Ed de Moel;
Copyright © Annotations: 2003-2008 Jacquard Systems Research
Copyright © Annotations: 2008-2024 Ed de Moel.

This page most recently updated on 16-Nov-2023, 17:26:01.

For comments, contact Ed de Moel (demoel@jacquardsystems.com)