ISO/IEC SC22/WG5/N1723 CD 1539-1 08-007r2:2008/03/11
• the physical properties and implementation of storage.
1.4 Conformance
1 A program (2.3.2) is a standard-conforming program if it uses only those forms and relationships described
herein and if the program has an interpretation according to this part of ISO/IEC 1539. A program unit (2.3.1)
conforms to this part of ISO/IEC 1539 if it can be included in a program in a manner that allows the program
to be s tandard conforming.
2 A processor conforms to this part of ISO/IEC 1539 if:
(1) it executes any standard-conforming program in a manner that fulfills the interpretations herein,
subject to any limits that the processor may impose on the size and complexity of the program;
(2) it contains the capability to detect and report the use within a submitted program unit of a form
designated herein as obsolescent, insofar as such use can be detected by reference to the numbered
syntax rules and constraints;
(3) it contains the capability to detect and report the use within a submitted program unit of an ad-
ditional form or relationship that is not permitted by the numbered syntax rules or constraints,
including the deleted features described in Annex B
(4) it contains the capability to detect and report the use within a submitted program unit of an intrinsic
type with a kind type parameter value not supported by the processor (4.4);
(5) it contains the capability to detect and report the use within a submitted program unit of source
form or characters not permitted by Clause 3;
(6) it contains the capability to detect and report the use within a submitted program of name usage
not consistent with the scope rules for names, labels, operators, and assignment symbols in Clause
16;
(7) it contains the capability to detect and report the use within a submitted program unit of intrinsic
procedures whose names are not defined in Clause 13; and
(8) it contains the capability to detect and report the reason for rejecting a submitted program.
3 However, in a format specification that is not part of a FORMAT statement (10.2.1), a processor need not detect
or report the use of deleted or obsolescent features, or the use of additional forms or relationships.
4 A standard-conforming processor may allow additional forms and relationships provided that such additions
do not conflict with the standard forms and relationships. However, a standard-conforming processor may allow
additional intrinsic procedures even though this could cause a conflict with the name of a procedure in a standard-
conforming program. If such a conflict occurs and involves the name of an external procedure, the processor is
permitted to use the intrinsic procedure unless the name is given the EXTERNAL attribute (5.3.9) in the sc oping
unit (2.3.1). A standard-conforming program shall not use nonstandard intrinsic procedures or modules that have
been added by the processor.
5 Because a standard-conforming program may place demands on a processor that are not within the scope of this
part of ISO/IEC 1539 or may include standard items that are not portable, such as external procedures defined
by means other than Fortran, conformance to this part of ISO/IEC 1539 does not ensure that a program will
execute consistently on all or any standard-conforming processors.
6 The semantics of facilities that are identified as processor dependent are not completely specified in this part of
ISO/IEC 1539. They shall be provided, with methods or semantics determined by the processor.
NOTE 1.1
The processor should be accompanied by documentation that specifies the limits it imposes on the size
and complexity of a program and the means of reporting when these limits are exceeded, that defines the
additional forms and relationships it allows, and that defines the means of reporting the use of additional
forms and relationships and the use of deleted or obsolescent forms. In this context, the use of a deleted
form is the use of an additional form.
2 Overview 1.4