WORKING DRAFT J3/04-007 May 10, 2004 11:07 This is an internal working document of J3. MAY 2004 WORKING DRAFT J3/04-007 Contents 1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.2 Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.3 Inclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.4 Exclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.5 Conformance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.6 Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.6.1 Fortran 95 compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.6.2 Fortran 90 compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.6.3 FORTRAN 77 compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.7 Notation used in this standard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.7.1 Informative notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.7.2 Syntax rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.7.3 Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.7.4 Assumed syntax rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1.7.5 Syntax conventions and characteristics . . . . . . . . . . . . . . . . . . . . . . . 6 1.7.6 Text conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1.8 Deleted and obsolescent features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.8.1 Nature of deleted features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.8.2 Nature of obsolescent features . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.9 Normative references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 2 Fortran terms and concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.1 High level syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.2 Program unit concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 2.2.1 Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.2.2 Main program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.2.3 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.2.4 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.3 Execution concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.3.1 Executable/nonexecutable statements . . . . . . . . . . . . . . . . . . . . . . . . 13 2.3.2 Statement order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.3.3 The END statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.3.4 Execution sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.4 Data concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.4.1 Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.4.2 Data value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 2.4.3 Data entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 2.4.4 Scalar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 2.4.5 Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 2.4.6 Pointer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 2.4.7 Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 2.5 Fundamental terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 2.5.1 Name and designator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 2.5.2 Keyword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 2.5.3 Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 2.5.4 Declaration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 i J3/04-007 WORKING DRAFT MAY 2004 2.5.5 Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 2.5.6 Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 2.5.7 Intrinsic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 2.5.8 Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 2.5.9 Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 2.5.10 Companion processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 3 Characters, lexical tokens, and source form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 3.1 Processor character set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 3.1.1 Letters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 3.1.2 Digits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 3.1.3 Underscore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 3.1.4 Special characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 3.1.5 Other characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 3.2 Low-level syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 3.2.1 Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 3.2.2 Constants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 3.2.3 Operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 3.2.4 Statement labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 3.2.5 Delimiters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 3.3 Source form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 3.3.1 Free source form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 3.3.2 Fixed source form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 3.4 Including source text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 4 Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 4.1 The concept of type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 4.1.1 Set of values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 4.1.2 Constants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 4.1.3 Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 4.2 Type parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 4.3 Relationship of types and values to objects . . . . . . . . . . . . . . . . . . . . . . . . . . 35 4.4 Intrinsic types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 4.4.1 Integer type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 4.4.2 Real type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 4.4.3 Complex type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 4.4.4 Character type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 4.4.5 Logical type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 4.5 Derived types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 4.5.1 Derived-type definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 4.5.2 Derived-type parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 4.5.3 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 4.5.4 Type-bound procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 4.5.5 Final subroutines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 4.5.6 Type extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 4.5.7 Derived-type values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 4.5.8 Derived-type specifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 4.5.9 Construction of derived-type values . . . . . . . . . . . . . . . . . . . . . . . . . 63 4.5.10 Derived-type operations and assignment . . . . . . . . . . . . . . . . . . . . . . 65 4.6 Enumerations and enumerators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 4.7 Construction of array values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 5 Data object declarations and specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 5.1 Type declaration statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 ii MAY 2004 WORKING DRAFT J3/04-007 5.1.1 Declaration type specifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 5.1.2 Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 5.2 Attribute specification statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 5.2.1 Accessibility statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 5.2.2 ALLOCATABLE statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 5.2.3 ASYNCHRONOUS statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 5.2.4 BIND statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 5.2.5 DATA statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 5.2.6 DIMENSION statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 5.2.7 INTENT statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 5.2.8 OPTIONAL statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 5.2.9 PARAMETER statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 5.2.10 POINTER statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 5.2.11 PROTECTED statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 5.2.12 SAVE statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 5.2.13 TARGET statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 5.2.14 VALUE statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 5.2.15 VOLATILE statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 5.3 IMPLICIT statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 5.4 NAMELIST statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 5.5 Storage association of data objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 5.5.1 EQUIVALENCE statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 5.5.2 COMMON statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 6 Use of data objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 6.1 Scalars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 6.1.1 Substrings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 6.1.2 Structure components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 6.1.3 Type parameter inquiry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 6.2 Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 6.2.1 Whole arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 6.2.2 Array elements and array sections . . . . . . . . . . . . . . . . . . . . . . . . . . 107 6.3 Dynamic association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 6.3.1 ALLOCATE statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 6.3.2 NULLIFY statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 6.3.3 DEALLOCATE statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 7 Expressions and assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 7.1 Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 7.1.1 Form of an expression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 7.1.2 Intrinsic operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 7.1.3 Defined operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 7.1.4 Type, type parameters, and shape of an expression . . . . . . . . . . . . . . . . 123 7.1.5 Conformability rules for elemental operations . . . . . . . . . . . . . . . . . . . 125 7.1.6 Specification expression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 7.1.7 Initialization expression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 7.1.8 Evaluation of operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 7.2 Interpretation of operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 7.2.1 Numeric intrinsic operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 7.2.2 Character intrinsic operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 7.2.3 Relational intrinsic operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 7.2.4 Logical intrinsic operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 7.3 Precedence of operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 7.4 Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 iii J3/04-007 WORKING DRAFT MAY 2004 7.4.1 Assignment statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 7.4.2 Pointer assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 7.4.3 Masked array assignment ­ WHERE . . . . . . . . . . . . . . . . . . . . . . . . 145 7.4.4 FORALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 8 Execution control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 8.1 Executable constructs containing blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 8.1.1 Rules governing blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 8.1.2 IF construct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 8.1.3 CASE construct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 8.1.4 ASSOCIATE construct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 8.1.5 SELECT TYPE construct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 8.1.6 DO construct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 8.2 Branching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 8.2.1 GO TO statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 8.2.2 Computed GO TO statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 8.2.3 Arithmetic IF statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 8.3 CONTINUE statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 8.4 STOP statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 9 Input/output statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 9.1 Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 9.1.1 Formatted record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 9.1.2 Unformatted record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 9.1.3 Endfile record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 9.2 External files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 9.2.1 File existence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 9.2.2 File access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 9.2.3 File position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 9.2.4 File storage units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 9.3 Internal files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 9.4 File connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 9.4.1 Connection modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 9.4.2 Unit existence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 9.4.3 Connection of a file to a unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 9.4.4 Preconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 9.4.5 The OPEN statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 9.4.6 The CLOSE statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 9.5 Data transfer statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 9.5.1 Control information list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 9.5.2 Data transfer input/output list . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 9.5.3 Execution of a data transfer input/output statement . . . . . . . . . . . . . . . 194 9.5.4 Termination of data transfer statements . . . . . . . . . . . . . . . . . . . . . . 205 9.6 Waiting on pending data transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 9.6.1 WAIT statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 9.6.2 Wait operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 9.7 File positioning statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 9.7.1 BACKSPACE statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 9.7.2 ENDFILE statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 9.7.3 REWIND statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 9.8 FLUSH statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 9.9 File inquiry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 9.9.1 Inquiry specifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 9.9.2 Restrictions on inquiry specifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 iv MAY 2004 WORKING DRAFT J3/04-007 9.9.3 Inquire by output list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 9.10 Error, end-of-record, and end-of-file conditions . . . . . . . . . . . . . . . . . . . . . . . . 216 9.10.1 Error conditions and the ERR= specifier . . . . . . . . . . . . . . . . . . . . . . 217 9.10.2 End-of-file condition and the END= specifier . . . . . . . . . . . . . . . . . . . . 217 9.10.3 End-of-record condition and the EOR= specifier . . . . . . . . . . . . . . . . . . 218 9.10.4 IOSTAT= specifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 9.10.5 IOMSG= specifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 9.11 Restrictions on input/output statements . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 10 Input/output editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 10.1 Explicit format specification methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 10.1.1 FORMAT statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 10.1.2 Character format specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 10.2 Form of a format item list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 10.2.1 Edit descriptors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 10.2.2 Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 10.3 Interaction between input/output list and format . . . . . . . . . . . . . . . . . . . . . . 224 10.4 Positioning by format control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 10.5 Decimal symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 10.6 Data edit descriptors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 10.6.1 Numeric editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 10.6.2 Logical editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 10.6.3 Character editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 10.6.4 Generalized editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 10.6.5 User-defined derived-type editing . . . . . . . . . . . . . . . . . . . . . . . . . . 235 10.7 Control edit descriptors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 10.7.1 Position editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 10.7.2 Slash editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 10.7.3 Colon editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 10.7.4 SS, SP, and S editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 10.7.5 P editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 10.7.6 BN and BZ editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 10.7.7 RU, RD, RZ, RN, RC, and RP editing . . . . . . . . . . . . . . . . . . . . . . . 238 10.7.8 DC and DP editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 10.8 Character string edit descriptors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 10.9 List-directed formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 10.9.1 List-directed input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 10.9.2 List-directed output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 10.10 Namelist formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 10.10.1 Namelist input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 10.10.2 Namelist output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 11 Program units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 11.1 Main program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 11.2 Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 11.2.1 The USE statement and use association . . . . . . . . . . . . . . . . . . . . . . . 251 11.3 Block data program units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 12 Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 12.1 Procedure classifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 12.1.1 Procedure classification by reference . . . . . . . . . . . . . . . . . . . . . . . . . 255 12.1.2 Procedure classification by means of definition . . . . . . . . . . . . . . . . . . . 255 12.2 Characteristics of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 12.2.1 Characteristics of dummy arguments . . . . . . . . . . . . . . . . . . . . . . . . 256 v J3/04-007 WORKING DRAFT MAY 2004 12.2.2 Characteristics of function results . . . . . . . . . . . . . . . . . . . . . . . . . . 257 12.3 Procedure interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 12.3.1 Implicit and explicit interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 12.3.2 Specification of the procedure interface . . . . . . . . . . . . . . . . . . . . . . . 258 12.4 Procedure reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 12.4.1 Actual arguments, dummy arguments, and argument association . . . . . . . . . 268 12.4.2 Function reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 12.4.3 Subroutine reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 12.4.4 Resolving named procedure references . . . . . . . . . . . . . . . . . . . . . . . . 276 12.4.5 Resolving type-bound procedure references . . . . . . . . . . . . . . . . . . . . . 278 12.5 Procedure definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 12.5.1 Intrinsic procedure definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 12.5.2 Procedures defined by subprograms . . . . . . . . . . . . . . . . . . . . . . . . . 279 12.5.3 Definition and invocation of procedures by means other than Fortran . . . . . . 285 12.5.4 Statement function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285 12.6 Pure procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286 12.7 Elemental procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287 12.7.1 Elemental procedure declaration and interface . . . . . . . . . . . . . . . . . . . 287 12.7.2 Elemental function actual arguments and results . . . . . . . . . . . . . . . . . . 288 12.7.3 Elemental subroutine actual arguments . . . . . . . . . . . . . . . . . . . . . . . 289 13 Intrinsic procedures and modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291 13.1 Classes of intrinsic procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291 13.2 Arguments to intrinsic procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291 13.2.1 The shape of array arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292 13.2.2 Mask arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292 13.3 Bit model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292 13.4 Numeric models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 13.5 Standard generic intrinsic procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 13.5.1 Numeric functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 13.5.2 Mathematical functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 13.5.3 Character functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295 13.5.4 Kind functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295 13.5.5 Miscellaneous type conversion functions . . . . . . . . . . . . . . . . . . . . . . . 295 13.5.6 Numeric inquiry functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295 13.5.7 Array inquiry functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296 13.5.8 Other inquiry functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296 13.5.9 Bit manipulation procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296 13.5.10 Floating-point manipulation functions . . . . . . . . . . . . . . . . . . . . . . . . 296 13.5.11 Vector and matrix multiply functions . . . . . . . . . . . . . . . . . . . . . . . . 297 13.5.12 Array reduction functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 13.5.13 Array construction functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 13.5.14 Array location functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 13.5.15 Null function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 13.5.16 Allocation transfer procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 13.5.17 Random number subroutines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 13.5.18 System environment procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . 298 13.6 Specific names for standard intrinsic functions . . . . . . . . . . . . . . . . . . . . . . . . 298 13.7 Specifications of the standard intrinsic procedures . . . . . . . . . . . . . . . . . . . . . . 300 13.8 Standard intrinsic modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 13.8.1 The IEEE modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 13.8.2 The ISO FORTRAN ENV intrinsic module . . . . . . . . . . . . . . . . . . . . 360 13.8.3 The ISO C BINDING module . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 vi MAY 2004 WORKING DRAFT J3/04-007 14 Exceptions and IEEE arithmetic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363 14.1 Derived types and constants defined in the modules . . . . . . . . . . . . . . . . . . . . . 364 14.2 The exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365 14.3 The rounding modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367 14.4 Underflow mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367 14.5 Halting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368 14.6 The floating point status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368 14.7 Exceptional values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368 14.8 IEEE arithmetic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368 14.9 Tables of the procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369 14.9.1 Inquiry functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369 14.9.2 Elemental functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 14.9.3 Kind function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 14.9.4 Elemental subroutines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 14.9.5 Nonelemental subroutines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 14.10 Specifications of the procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371 14.11 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386 15 Interoperability with C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391 15.1 The ISO C BINDING intrinsic module . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391 15.1.1 Named constants and derived types in the module . . . . . . . . . . . . . . . . . 391 15.1.2 Procedures in the module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392 15.2 Interoperability between Fortran and C entities . . . . . . . . . . . . . . . . . . . . . . . 395 15.2.1 Interoperability of intrinsic types . . . . . . . . . . . . . . . . . . . . . . . . . . 396 15.2.2 Interoperability with C pointer types . . . . . . . . . . . . . . . . . . . . . . . . 397 15.2.3 Interoperability of derived types and C struct types . . . . . . . . . . . . . . . . 398 15.2.4 Interoperability of scalar variables . . . . . . . . . . . . . . . . . . . . . . . . . . 399 15.2.5 Interoperability of array variables . . . . . . . . . . . . . . . . . . . . . . . . . . 399 15.2.6 Interoperability of procedures and procedure interfaces . . . . . . . . . . . . . . 400 15.3 Interoperation with C global variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402 15.3.1 Binding labels for common blocks and variables . . . . . . . . . . . . . . . . . . 403 15.4 Interoperation with C functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403 15.4.1 Binding labels for procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403 15.4.2 Exceptions and IEEE arithmetic procedures . . . . . . . . . . . . . . . . . . . . 404 16 Scope, association, and definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405 16.1 Scope of global identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405 16.2 Scope of local identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406 16.2.1 Local identifiers that are the same as common block names . . . . . . . . . . . . 407 16.2.2 Function results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407 16.2.3 Restrictions on generic declarations . . . . . . . . . . . . . . . . . . . . . . . . . 407 16.2.4 Components, type parameters, and bindings . . . . . . . . . . . . . . . . . . . . 408 16.2.5 Argument keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409 16.3 Statement and construct entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409 16.4 Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410 16.4.1 Name association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410 16.4.2 Pointer association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414 16.4.3 Storage association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415 16.4.4 Inheritance association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418 16.4.5 Establishing associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418 16.5 Definition and undefinition of variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419 16.5.1 Definition of objects and subobjects . . . . . . . . . . . . . . . . . . . . . . . . . 419 16.5.2 Variables that are always defined . . . . . . . . . . . . . . . . . . . . . . . . . . 419 16.5.3 Variables that are initially defined . . . . . . . . . . . . . . . . . . . . . . . . . . 419 vii J3/04-007 WORKING DRAFT MAY 2004 16.5.4 Variables that are initially undefined . . . . . . . . . . . . . . . . . . . . . . . . 420 16.5.5 Events that cause variables to become defined . . . . . . . . . . . . . . . . . . . 420 16.5.6 Events that cause variables to become undefined . . . . . . . . . . . . . . . . . . 421 16.5.7 Variable definition context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423 Annex A (informative)Glossary of technical terms . . . . . . . . . . . . . . . . . . . . . . . . . . 425 Annex B (informative)Decremental features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437 B.1 Deleted features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437 B.2 Obsolescent features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438 B.2.1 Alternate return . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438 B.2.2 Computed GO TO statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438 B.2.3 Statement functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438 B.2.4 DATA statements among executables . . . . . . . . . . . . . . . . . . . . . . . . 439 B.2.5 Assumed character length functions . . . . . . . . . . . . . . . . . . . . . . . . . 439 B.2.6 Fixed form source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439 B.2.7 CHARACTER* form of CHARACTER declaration . . . . . . . . . . . . . . . . 439 Annex C (informative)Extended notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441 C.1 Section 4 notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441 C.1.1 Intrinsic and derived types (4.4, 4.5) . . . . . . . . . . . . . . . . . . . . . . . . 441 C.1.2 Selection of the approximation methods (4.4.2) . . . . . . . . . . . . . . . . . . 442 C.1.3 Type extension and component accessibility (4.5.1.1, 4.5.3) . . . . . . . . . . . . 442 C.1.4 Abstract types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 C.1.5 Pointers (4.5.1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444 C.1.6 Structure constructors and generic names . . . . . . . . . . . . . . . . . . . . . . 445 C.1.7 Generic type-bound procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . 447 C.1.8 Final subroutines (4.5.5, 4.5.5.1, 4.5.5.2, 4.5.5.3) . . . . . . . . . . . . . . . . . . 448 C.2 Section 5 notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450 C.2.1 The POINTER attribute (5.1.2.11) . . . . . . . . . . . . . . . . . . . . . . . . . 450 C.2.2 The TARGET attribute (5.1.2.14) . . . . . . . . . . . . . . . . . . . . . . . . . . 451 C.2.3 The VOLATILE attribute (5.1.2.16) . . . . . . . . . . . . . . . . . . . . . . . . . 451 C.3 Section 6 notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452 C.3.1 Structure components (6.1.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452 C.3.2 Allocation with dynamic type (6.3.1) . . . . . . . . . . . . . . . . . . . . . . . . 453 C.3.3 Pointer allocation and association . . . . . . . . . . . . . . . . . . . . . . . . . . 454 C.4 Section 7 notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455 C.4.1 Character assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455 C.4.2 Evaluation of function references . . . . . . . . . . . . . . . . . . . . . . . . . . 455 C.4.3 Pointers in expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455 C.4.4 Pointers on the left side of an assignment . . . . . . . . . . . . . . . . . . . . . . 455 C.4.5 An example of a FORALL construct containing a WHERE construct . . . . . . 456 C.4.6 Examples of FORALL statements . . . . . . . . . . . . . . . . . . . . . . . . . . 457 C.5 Section 8 notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458 C.5.1 Loop control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458 C.5.2 The CASE construct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458 C.5.3 Examples of DO constructs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458 C.5.4 Examples of invalid DO constructs . . . . . . . . . . . . . . . . . . . . . . . . . 460 C.6 Section 9 notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461 C.6.1 External files (9.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461 C.6.2 Nonadvancing input/output (9.2.3.1) . . . . . . . . . . . . . . . . . . . . . . . . 463 C.6.3 Asynchronous input/output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464 C.6.4 OPEN statement (9.4.5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465 C.6.5 Connection properties (9.4.3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466 viii MAY 2004 WORKING DRAFT J3/04-007 C.6.6 CLOSE statement (9.4.6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467 C.7 Section 10 notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467 C.7.1 Number of records (10.3, 10.4, 10.7.2) . . . . . . . . . . . . . . . . . . . . . . . . 467 C.7.2 List-directed input (10.9.1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468 C.8 Section 11 notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468 C.8.1 Main program and block data program unit (11.1, 11.3) . . . . . . . . . . . . . 468 C.8.2 Dependent compilation (11.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469 C.8.3 Examples of the use of modules . . . . . . . . . . . . . . . . . . . . . . . . . . . 471 C.9 Section 12 notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477 C.9.1 Portability problems with external procedures (12.3.2.2) . . . . . . . . . . . . . 477 C.9.2 Procedures defined by means other than Fortran (12.5.3) . . . . . . . . . . . . . 478 C.9.3 Procedure interfaces (12.3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478 C.9.4 Abstract interfaces (12.3) and procedure pointer components (4.5) . . . . . . . . 478 C.9.5 Argument association and evaluation (12.4.1.2) . . . . . . . . . . . . . . . . . . 480 C.9.6 Pointers and targets as arguments (12.4.1.2) . . . . . . . . . . . . . . . . . . . . 481 C.9.7 Polymorphic Argument Association (12.4.1.3) . . . . . . . . . . . . . . . . . . . 482 C.10 Section 15 notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484 C.10.1 Runtime environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484 C.10.2 Examples of Interoperation between Fortran and C Functions . . . . . . . . . . 484 C.11 Section 16 notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489 C.11.1 Examples of host association (16.4.1.3) . . . . . . . . . . . . . . . . . . . . . . . 489 C.11.2 Rules ensuring unambiguous generics (16.2.3) . . . . . . . . . . . . . . . . . . . 490 C.12 Array feature notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495 C.12.1 Summary of features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495 C.12.2 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497 C.12.3 FORmula TRANslation and array processing . . . . . . . . . . . . . . . . . . . 501 C.12.4 Sum of squared residuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502 C.12.5 Vector norms: infinity-norm and one-norm . . . . . . . . . . . . . . . . . . . . . 502 C.12.6 Matrix norms: infinity-norm and one-norm . . . . . . . . . . . . . . . . . . . . . 502 C.12.7 Logical queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503 C.12.8 Parallel computations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503 C.12.9 Example of element-by-element computation . . . . . . . . . . . . . . . . . . . . 504 C.12.10 Bit manipulation and inquiry procedures . . . . . . . . . . . . . . . . . . . . . . 504 Annex D (informative)Syntax rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505 D.1 Extract of all syntax rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505 D.2 Syntax rule cross-reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543 Annex E (informative)Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555 ix J3/04-007 WORKING DRAFT MAY 2004 x MAY 2004 WORKING DRAFT J3/04-007 List of Tables 2.1 Requirements on statement ordering . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.2 Statements allowed in scoping units . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 3.1 Special characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 6.1 Subscript order value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 7.1 Type of operands and results for intrinsic operators . . . . . . . . . . . . . . . . . 121 7.2 Interpretation of the numeric intrinsic operators . . . . . . . . . . . . . . . . . . . 133 7.3 Interpretation of the character intrinsic operator // . . . . . . . . . . . . . . . . . 134 7.4 Interpretation of the relational intrinsic operators . . . . . . . . . . . . . . . . . . 134 7.5 Interpretation of the logical intrinsic operators . . . . . . . . . . . . . . . . . . . . 135 7.6 The values of operations involving logical intrinsic operators . . . . . . . . . . . . 136 7.7 Categories of operations and relative precedence . . . . . . . . . . . . . . . . . . . 136 7.8 Type conformance for the intrinsic assignment statement . . . . . . . . . . . . . . 139 7.9 Numeric conversion and the assignment statement . . . . . . . . . . . . . . . . . . 141 13.1 Characteristics of the result of NULL ( ) . . . . . . . . . . . . . . . . . . . . . . . . 341 15.1 Names of C characters with special semantics . . . . . . . . . . . . . . . . . . . . . 392 15.2 Interoperability between Fortran and C types . . . . . . . . . . . . . . . . . . . . . 396 xi J3/04-007 WORKING DRAFT MAY 2004 Foreword ISO (the International Organization for Standardization) is a worldwide federation of national stan- dards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO technical committees. Each member body interested in a subject for which a techni- cal committee has been established has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of technical committees is to prepare International Standards. Draft International Stan- dards adopted by the technical committees are circulated to the member bodies for voting. Publication as an International Standard requires approval by at least 75% of the member bodies casting a vote. International Standard ISO/IEC 1539-1 was prepared by Joint Technical Committee ISO/IEC/JTC1, Information technology, Subcommittee SC22, Programming languages, their environments and system software interfaces. This fourth edition cancels and replaces the third edition (ISO/IEC 1539-1:1997), which has been tech- nically revised. ISO/IEC 1539 consists of the following parts, under the general title Information technology -- Pro- gramming languages -- Fortran: -- Part 1: Base language -- Part 2: Varying length character strings -- Part 3: Conditional Compilation The annexes of this part of ISO/IEC 1539 are for information only. xii MAY 2004 WORKING DRAFT J3/04-007 Introduction International Standard programming language Fortran This part of the International Standard comprises the specification of the base Fortran language, infor- mally known as Fortran 2003. With the limitations noted in 1.6.2, the syntax and semantics of Fortran 95 are contained entirely within Fortran 2003. Therefore, any standard-conforming Fortran 95 program not affected by such limitations is a standard conforming Fortran 2003 program. New features of Fortran 2003 can be compatibly incorporated into such Fortran 95 programs, with any exceptions indicated in the text of this part of the standard. Fortran 2003 contains several extensions to Fortran 95; among them are: (1) Derived-type enhancements: parameterized derived types (allows the kind, length, or shape of a derived type's components to be chosen when the derived type is used), mixed compo- nent accessibility (allows different components to have different accessibility), public entities of private type, improved structure constructors, and finalizers. (2) Object oriented programming support: enhanced data abstraction (allows one type to ex- tend the definition of another type), polymorphism (allows the type of a variable to vary at runtime), dynamic type allocation, SELECT TYPE construct (allows a choice of execu- tion flow depending upon the type a polymorphic object currently has), and type-bound procedures. (3) The ASSOCIATE construct (allows a complex expression or object to be denoted by a simple symbol). (4) Data manipulation enhancements: allocatable components, deferred type parameters, VOL- ATILE attribute, explicit type specification in array constructors, INTENT specification of pointer arguments, specified lower bounds of pointer assignment and pointer rank remap- ping, extended initialization expressions, MAX and MIN intrinsics for character type, and enhanced complex constants. (5) Input/output enhancements: asynchronous transfer operations (allows a program to con- tinue to process data while an input/output transfer occurs), stream access (allows access to a file without reference to any record structure), user specified transfer operations for derived types, user specified control of rounding during format conversions, the FLUSH statement, named constants for preconnected units, regularization of input/output keywords, and ac- cess to input/output error messages. (6) Procedure pointers. (7) Scoping enhancements: the ability to rename defined operators (supports greater data ab- straction) and control of host association into interface bodies. (8) Support for IEC 60559 (IEEE 754) exceptions and arithmetic (to the extent a processor's arithmetic supports the IEC International Standard). (9) Interoperability with the C programming language (allows portable access to many libraries and the low-level facilities provided by C and allows the portable use of Fortran libraries by programs written in C). (10) Support for international usage: (ISO 10646) and choice of decimal or comma in numeric formatted input/output. (11) Enhanced integration with the host operating system: access to command line arguments, environment variables, and the processor's error messages. xiii J3/04-007 WORKING DRAFT MAY 2004 Organization of this part of ISO/IEC 1539 This part of ISO/IEC 1539 is organized in 16 sections, dealing with 8 conceptual areas. These 8 areas, and the sections in which they are treated, are: High/low level concepts Sections 1, 2, 3 Data concepts Sections 4, 5, 6 Computations Sections 7, 13, 14 Execution control Section 8 Input/output Sections 9, 10 Program units Sections 11, 12 Interoperability with C Section 15 Scoping and association rules Section 16 It also contains the following nonnormative material: Glossary A Decremental features B Extended notes C Syntax rules D Index E xiv MAY 2004 WORKING DRAFT J3/04-007 1Information technology -- Programming languages -- 2Fortran -- 3Part 1: 4Base Language 5Section 1: Overview 61.1 Scope 7ISO/IEC 1539 is a multipart International Standard; the parts are published separately. This publi- 8cation, ISO/IEC 1539-1, which is the first part, specifies the form and establishes the interpretation 9of programs expressed in the base Fortran language. The purpose of this part of ISO/IEC 1539 is to 10promote portability, reliability, maintainability, and efficient execution of Fortran programs for use on 11a variety of computing systems. The second part, ISO/IEC 1539-2, defines additional facilities for the 12manipulation of character strings of variable length. The third part, ISO/IEC 1539-3, defines a stan- 13dard conditional compilation facility for Fortran. A processor conforming to part 1 need not conform to 14ISO/IEC 1539-2 or ISO/IEC 1539-3; however, conformance to either assumes conformance to this part. 15Throughout this publication, the term "this standard" refers to ISO/IEC 1539-1. 161.2 Processor 17The combination of a computing system and the mechanism by which programs are transformed for use 18on that computing system is called a processor in this standard. 191.3 Inclusions 20This standard specifies 21 (1) The forms that a program written in the Fortran language may take, 22 (2) The rules for interpreting the meaning of a program and its data, 23 (3) The form of the input data to be processed by such a program, and 24 (4) The form of the output data resulting from the use of such a program. 251.4 Exclusions 26This standard does not specify 27 (1) The mechanism by which programs are transformed for use on computing systems, 28 (2) The operations required for setup and control of the use of programs on computing systems, 29 (3) The method of transcription of programs or their input or output data to or from a storage 30 medium, 31 (4) The program and processor behavior when this standard fails to establish an interpretation 32 except for the processor detection and reporting requirements in items (2) through (8) of 1 J3/04-007 WORKING DRAFT MAY 2004 1 1.5, 2 (5) The size or complexity of a program and its data that will exceed the capacity of any 3 particular computing system or the capability of a particular processor, 4 (6) The physical properties of the representation of quantities and the method of rounding, 5 approximating, or computing numeric values on a particular processor, 6 (7) The physical properties of input/output records, files, and units, or 7 (8) The physical properties and implementation of storage. 81.5 Conformance 9A program (2.2.1) is a standard-conforming program if it uses only those forms and relationships 10described herein and if the program has an interpretation according to this standard. A program unit 11(2.2) conforms to this standard if it can be included in a program in a manner that allows the program 12to be standard conforming. 13A processor conforms to this standard if 14 (1) It executes any standard-conforming program in a manner that fulfills the interpretations 15 herein, subject to any limits that the processor may impose on the size and complexity of 16 the program; 17 (2) It contains the capability to detect and report the use within a submitted program unit of 18 a form designated herein as obsolescent, insofar as such use can be detected by reference to 19 the numbered syntax rules and constraints; 20 (3) It contains the capability to detect and report the use within a submitted program unit of 21 an additional form or relationship that is not permitted by the numbered syntax rules or 22 constraints, including the deleted features described in Annex B; 23 (4) It contains the capability to detect and report the use within a submitted program unit of 24 an intrinsic type with a kind type parameter value not supported by the processor (4.4); 25 (5) It contains the capability to detect and report the use within a submitted program unit of 26 source form or characters not permitted by Section 3; 27 (6) It contains the capability to detect and report the use within a submitted program of name 28 usage not consistent with the scope rules for names, labels, operators, and assignment 29 symbols in Section 16; 30 (7) It contains the capability to detect and report the use within a submitted program unit of 31 intrinsic procedures whose names are not defined in Section 13; and 32 (8) It contains the capability to detect and report the reason for rejecting a submitted program. 33However, in a format specification that is not part of a FORMAT statement (10.1.1), a processor need not 34detect or report the use of deleted or obsolescent features, or the use of additional forms or relationships. 35A standard-conforming processor may allow additional forms and relationships provided that such ad- 36ditions do not conflict with the standard forms and relationships. However, a standard-conforming 37processor may allow additional intrinsic procedures even though this could cause a conflict with the 38name of a procedure in a standard-conforming program. If such a conflict occurs and involves the name 39of an external procedure, the processor is permitted to use the intrinsic procedure unless the name is 40given the EXTERNAL attribute (5.1.2.6) in the scoping unit (16). A standard-conforming program 41shall not use nonstandard intrinsic procedures or modules that have been added by the processor. 42Because a standard-conforming program may place demands on a processor that are not within the 43scope of this standard or may include standard items that are not portable, such as external procedures 44defined by means other than Fortran, conformance to this standard does not ensure that a program will 45execute consistently on all or any standard-conforming processors. 2 MAY 2004 WORKING DRAFT J3/04-007 1In some cases, this standard allows the provision of facilities that are not completely specified in the 2standard. These facilities are identified as processor dependent. They shall be provided, with methods 3or 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. The processor should be accompanied by documentation that specifies the methods or semantics of processor-dependent facilities. 41.6 Compatibility 5Each Fortran International Standard since ISO 1539:1980 (informally referred to as Fortran 77), defines 6more intrinsic procedures than the previous one. Therefore, a Fortran program conforming to an older 7standard may have a different interpretation under a newer standard if it invokes an external procedure 8having the same name as one of the new standard intrinsic procedures, unless that procedure is specified 9to have the EXTERNAL attribute. 101.6.1 Fortran 95 compatibility 11Except as identified in this section, this standard is an upward compatible extension to the preceding 12Fortran International Standard, ISO/IEC 1539-1:1997 (Fortran 95). Any standard-conforming Fortran 1395 program remains standard-conforming under this standard. The following Fortran 95 features may 14have different interpretations in this standard: 15 (1) Earlier Fortran standards had the concept of printing, meaning that column one of formatted 16 output had special meaning for a processor-dependent (possibly empty) set of external 17 files. This could be neither detected nor specified by a standard-specified means. The 18 interpretation of the first column is not specified by this standard. 19 (2) This standard specifies a different output format for real zero values in list-directed and 20 namelist output. 21 (3) If the processor can distinguish between positive and negative real zero, this standard re- 22 quires different returned values for ATAN2(Y,X) when X < 0 and Y is negative real zero 23 and for LOG(X) and SQRT(X) when X is complex with REAL(X) < 0 and negative zero 24 imaginary part. 251.6.2 Fortran 90 compatibility 26Except for the deleted features noted in Annex B.1, and except as identified in this section, this stan- 27dard is an upward compatible extension to ISO/IEC 1539:1991 (Fortran 90). Any standard-conforming 28Fortran 90 program that does not use one of the deleted features remains standard-conforming under 29this standard. 30The PAD= specifier in the INQUIRE statement in this standard returns the value UNDEFINED if there 31is no connection or the connection is for unformatted input/output. Fortran 90 specified YES. 32Fortran 90 specified that if the second argument to MOD or MODULO was zero, the result was processor 33dependent. This standard specifies that the second argument shall not be zero. 3 J3/04-007 WORKING DRAFT MAY 2004 11.6.3 FORTRAN 77 compatibility 2Except for the deleted features noted in Annex B.1, and except as identified in this section, this standard 3is an upward compatible extension to ISO 1539:1980 (Fortran 77). Any standard-conforming For- 4tran 77 program that does not use one of the deleted features noted in Annex B.1 and that does not 5depend on the differences specified here remains standard conforming under this standard. This stan- 6dard restricts the behavior for some features that were processor dependent in Fortran 77. Therefore, 7a standard-conforming Fortran 77 program that uses one of these processor-dependent features may 8have a different interpretation under this standard, yet remain a standard-conforming program. The 9following Fortran 77 features may have different interpretations in this standard: 10 (1) Fortran 77 permitted a processor to supply more precision derived from a real constant 11 than can be represented in a real datum when the constant is used to initialize a data 12 object of type double precision real in a DATA statement. This standard does not permit 13 a processor this option. 14 (2) If a named variable that was not in a common block was initialized in a DATA statement and 15 did not have the SAVE attribute specified, Fortran 77 left its SAVE attribute processor 16 dependent. This standard specifies (5.2.5) that this named variable has the SAVE attribute. 17 (3) Fortran 77 specified that the number of characters required by the input list was to be 18 less than or equal to the number of characters in the record during formatted input. This 19 standard specifies (9.5.3.4.2) that the input record is logically padded with blanks if there 20 are not enough characters in the record, unless the PAD= specifier with the value 'NO' is 21 specified in an appropriate OPEN or READ statement. 22 (4) A value of 0 for a list item in a formatted output statement will be formatted in a differ- 23 ent form for some G edit descriptors. In addition, this standard specifies how rounding of 24 values will affect the output field form, but Fortran 77 did not address this issue. There- 25 fore, some Fortran 77 processors may produce an output form different from the output 26 form produced by Fortran 2003 processors for certain combinations of values and G edit 27 descriptors. 28 (5) If the processor can distinguish between positive and negative real zero, the behavior of the 29 SIGN intrinsic function when the second argument is negative real zero is changed by this 30 standard. 311.7 Notation used in this standard 32In this standard, "shall" is to be interpreted as a requirement; conversely, "shall not" is to be interpreted 33as a prohibition. Except where stated otherwise, such requirements and prohibitions apply to programs 34rather than processors. 351.7.1 Informative notes 36Informative notes of explanation, rationale, examples, and other material are interspersed with the 37normative body of this publication. The informative material is nonnormative; it is identified by being 38in shaded, framed boxes that have numbered headings beginning with "NOTE." 391.7.2 Syntax rules 40Syntax rules describe the forms that Fortran lexical tokens, statements, and constructs may take. These 41syntax rules are expressed in a variation of Backus-Naur form (BNF) in which: 42 (1) Characters from the Fortran character set (3.1) are interpreted literally as shown, except 43 where otherwise noted. 4 MAY 2004 WORKING DRAFT J3/04-007 1 (2) Lower-case italicized letters and words (often hyphenated and abbreviated) represent gen- 2 eral syntactic classes for which particular syntactic entities shall be substituted in actual 3 statements. 4 Common abbreviations used in syntactic terms are: arg for argument attr for attribute decl for declaration def for definition desc for descriptor expr for expression int for integer op for operator spec for specifier stmt for statement 5 (3) The syntactic metasymbols used are: is introduces a syntactic class definition or introduces a syntactic class alternative [ ] encloses an optional item [ ] ... encloses an optionally repeated item that may occur zero or more times continues a syntax rule 6 (4) Each syntax rule is given a unique identifying number of the form Rsnn, where s is a one- 7 or two-digit section number and nn is a two-digit sequence number within that section. 8 The syntax rules are distributed as appropriate throughout the text, and are referenced by 9 number as needed. Some rules in Sections 2 and 3 are more fully described in later sections; 10 in such cases, the section number s is the number of the later section where the rule is 11 repeated. 12 (5) The syntax rules are not a complete and accurate syntax description of Fortran, and cannot 13 be used to generate a Fortran parser automatically; where a syntax rule is incomplete, it is 14 restricted by corresponding constraints and text. NOTE 1.2 An example of the use of the syntax rules is: digit-string is digit [ digit ] ... The following are examples of forms for a digit string allowed by the above rule: digit digit digit digit digit digit digit digit digit digit digit digit digit digit digit If particular entities are substituted for digit, actual digit strings might be: 4 67 1999 10243852 151.7.3 Constraints 16Each constraint is given a unique identifying number of the form Csnn, where s is a one- or two-digit 17section number and nn is a two-digit sequence number within that section. 5 J3/04-007 WORKING DRAFT MAY 2004 1Often a constraint is associated with a particular syntax rule. Where that is the case, the constraint is 2annotated with the syntax rule number in parentheses. A constraint that is associated with a syntax 3rule constitutes part of the definition of the syntax term defined by the rule. It thus applies in all places 4where the syntax term appears. 5Some constraints are not associated with particular syntax rules. The effect of such a constraint is similar 6to that of a restriction stated in the text, except that a processor is required to have the capability to 7detect and report violations of constraints (1.5). In some cases, a broad requirement is stated in text 8and a subset of the same requirement is also stated as a constraint. This indicates that a standard- 9conforming program is required to adhere to the broad requirement, but that a standard-conforming 10processor is required only to have the capability of diagnosing violations of the constraint. 111.7.4 Assumed syntax rules 12In order to minimize the number of additional syntax rules and convey appropriate constraint informa- 13tion, the following rules are assumed; an explicit syntax rule for a term overrides an assumed rule. The 14letters "xyz" stand for any syntactic class phrase: 15R101 xyz-list is xyz [ , xyz ] ... 16R102 xyz-name is name 17R103 scalar-xyz is xyz 18C101 (R103) scalar-xyz shall be scalar. 191.7.5 Syntax conventions and characteristics 20 (1) Any syntactic class name ending in "-stmt" follows the source form statement rules: it shall 21 be delimited by end-of-line or semicolon, and may be labeled unless it forms part of another 22 statement (such as an IF or WHERE statement). Conversely, everything considered to be 23 a source form statement is given a "-stmt" ending in the syntax rules. 24 (2) The rules on statement ordering are described rigorously in the definition of program-unit 25 (R202). Expression hierarchy is described rigorously in the definition of expr (R722). 26 (3) The suffix "-spec" is used consistently for specifiers, such as input/output statement speci- 27 fiers. It also is used for type declaration attribute specifications (for example, "array-spec" 28 in R510), and in a few other cases. 29 (4) Where reference is made to a type parameter, including the surrounding parentheses, the 30 suffix "-selector" is used. See, for example, "kind-selector" (R404) and "length-selector" 31 (R425). 32 (5) The term "subscript" (for example, R618, R619, and R620) is used consistently in array 33 definitions. 341.7.6 Text conventions 35In the descriptive text, an equivalent English word is frequently used in place of a syntactic term. 36Particular statements and attributes are identified in the text by an upper-case keyword, e.g., "END 37statement". Boldface words are used in the text where they are first defined with a specialized meaning. 38The descriptions of obsolescent features appear in a smaller type size. NOTE 1.3 This sentence is an example of the type size used for obsolescent features. 6 MAY 2004 WORKING DRAFT J3/04-007 11.8 Deleted and obsolescent features 2This standard protects the users' investment in existing software by including all but five of the language 3elements of Fortran 90 that are not processor dependent. This standard identifies two categories of 4outmoded features. There are five in the first category, deleted features, which consists of features 5considered to have been redundant in Fortran 77 and largely unused in Fortran 90. Those in the second 6category, obsolescent features, are considered to have been redundant in Fortran 90 and Fortran 95, 7but are still frequently used. 81.8.1 Nature of deleted features 9 (1) Better methods existed in Fortran 77. 10 (2) These features are not included in Fortran 95 or this revision of Fortran. 111.8.2 Nature of obsolescent features 12 (1) Better methods existed in Fortran 90 and Fortran 95. 13 (2) It is recommended that programmers use these better methods in new programs and convert 14 existing code to these methods. 15 (3) These features are identified in the text of this document by a distinguishing type font 16 (1.7.6). 17 (4) If the use of these features becomes insignificant, future Fortran standards committees should 18 consider deleting them. 19 (5) The next Fortran standards committee should consider for deletion only those language 20 features that appear in the list of obsolescent features. 21 (6) Processors supporting the Fortran language should support these features as long as they 22 continue to be used widely in Fortran programs. 231.9 Normative references 24The following referenced standards are indispensable for the application of this standard. For dated 25references, only the edition cited applies. For undated references, the latest edition of the referenced 26standard (including any amendments) applies. 27ISO/IEC 646:1991, Information technology--ISO 7-bit coded character set for information interchange. 28ISO 8601:1988, Data elements and interchange formats--Information interchange-- 29Representation of dates and times. 30ISO/IEC 9899:1999, Information technology--Programming languages--C. 31ISO/IEC 10646-1:2000, Information technology--Universal multiple-octet coded character set (UCS)-- 32Part 1: Architecture and basic multilingual plane. 33IEC 60559 (1989-01), Binary floating-point arithmetic for microprocessor systems. 34ISO/IEC 646:1991 (International Reference Version) is the international equivalent of ANSI X3.4-1986, 35commonly known as ASCII. 36This standard refers to ISO/IEC 9899:1999 as the C International Standard. 37Because IEC 60559 (1989-01) was originally IEEE 754-1985, Standard for binary floating-point arith- 38metic, and is widely known by this name, this standard refers to it as the IEEE International Standard. 7 J3/04-007 WORKING DRAFT MAY 2004 8 MAY 2004 WORKING DRAFT J3/04-007 1Section 2: Fortran terms and concepts 22.1 High level syntax 3This section introduces the terms associated with program units and other Fortran concepts above the 4construct, statement, and expression levels and illustrates their relationships. The notation used in this 5standard is described in 1.7. NOTE 2.1 Constraints and other information related to the rules that do not begin with R2 appear in the appropriate section. 6R201 program is program-unit 7 [ program-unit ] ... 8A program shall contain exactly one main-program program-unit or a main program defined by means 9other than Fortran, but not both. 10R202 program-unit is main-program 11 or external-subprogram 12 or module 13 or block-data 14R1101 main-program is [ program-stmt ] 15 [ specification-part ] 16 [ execution-part ] 17 [ internal-subprogram-part ] 18 end-program-stmt 19R203 external-subprogram is function-subprogram 20 or subroutine-subprogram 21R1223 function-subprogram is function-stmt 22 [ specification-part ] 23 [ execution-part ] 24 [ internal-subprogram-part ] 25 end-function-stmt 26R1231 subroutine-subprogram is subroutine-stmt 27 [ specification-part ] 28 [ execution-part ] 29 [ internal-subprogram-part ] 30 end-subroutine-stmt 31R1104 module is module-stmt 32 [ specification-part ] 33 [ module-subprogram-part ] 34 end-module-stmt 35R1116 block-data is block-data-stmt 36 [ specification-part ] 37 end-block-data-stmt 38R204 specification-part is [ use-stmt ] ... 39 [ import-stmt ] ... 40 [ implicit-part ] 41 [ declaration-construct ] ... 9 J3/04-007 WORKING DRAFT MAY 2004 1R205 implicit-part is [ implicit-part-stmt ] ... 2 implicit-stmt 3R206 implicit-part-stmt is implicit-stmt 4 or parameter-stmt 5 or format-stmt 6 or entry-stmt 7R207 declaration-construct is derived-type-def 8 or entry-stmt 9 or enum-def 10 or format-stmt 11 or interface-block 12 or parameter-stmt 13 or procedure-declaration-stmt 14 or specification-stmt 15 or type-declaration-stmt 16 or stmt-function-stmt 17R208 execution-part is executable-construct 18 [ execution-part-construct ] ... 19R209 execution-part-construct is executable-construct 20 or format-stmt 21 or entry-stmt 22 or data-stmt 23R210 internal-subprogram-part is contains-stmt 24 internal-subprogram 25 [ internal-subprogram ] ... 26R211 internal-subprogram is function-subprogram 27 or subroutine-subprogram 28R1107 module-subprogram-part is contains-stmt 29 module-subprogram 30 [ module-subprogram ] ... 31R1108 module-subprogram is function-subprogram 32 or subroutine-subprogram 33R212 specification-stmt is access-stmt 34 or allocatable-stmt 35 or asynchronous-stmt 36 or bind-stmt 37 or common-stmt 38 or data-stmt 39 or dimension-stmt 40 or equivalence-stmt 41 or external-stmt 42 or intent-stmt 43 or intrinsic-stmt 44 or namelist-stmt 45 or optional-stmt 46 or pointer-stmt 47 or protected-stmt 48 or save-stmt 49 or target-stmt 50 or volatile-stmt 51 or value-stmt 52R213 executable-construct is action-stmt 53 or associate-construct 54 or case-construct 10 MAY 2004 WORKING DRAFT J3/04-007 1 or do-construct 2 or forall-construct 3 or if-construct 4 or select-type-construct 5 or where-construct 6R214 action-stmt is allocate-stmt 7 or assignment-stmt 8 or backspace-stmt 9 or call-stmt 10 or close-stmt 11 or continue-stmt 12 or cycle-stmt 13 or deallocate-stmt 14 or endfile-stmt 15 or end-function-stmt 16 or end-program-stmt 17 or end-subroutine-stmt 18 or exit-stmt 19 or flush-stmt 20 or forall-stmt 21 or goto-stmt 22 or if-stmt 23 or inquire-stmt 24 or nullify-stmt 25 or open-stmt 26 or pointer-assignment-stmt 27 or print-stmt 28 or read-stmt 29 or return-stmt 30 or rewind-stmt 31 or stop-stmt 32 or wait-stmt 33 or where-stmt 34 or write-stmt 35 or arithmetic-if-stmt 36 or computed-goto-stmt 37C201 (R208) An execution-part shall not contain an end-function-stmt, end-program-stmt, or end- 38 subroutine-stmt. 392.2 Program unit concepts 40Program units are the fundamental components of a Fortran program. A program unit may be 41a main program, an external subprogram, a module, or a block data program unit. A subprogram 42may be a function subprogram or a subroutine subprogram. A module contains definitions that are 43to be made accessible to other program units. A block data program unit is used to specify initial 44values for data objects in named common blocks. Each type of program unit is described in Section 4511 or 12. An external subprogram is a subprogram that is not in a main program, a module, or 46another subprogram. An internal subprogram is a subprogram that is in a main program or another 47subprogram. A module subprogram is a subprogram that is in a module but is not an internal 48subprogram. 49A program unit consists of a set of nonoverlapping scoping units. A scoping unit is 11 J3/04-007 WORKING DRAFT MAY 2004 1 (1) A program unit or subprogram, excluding any scoping units in it, 2 (2) A derived-type definition (4.5.1), or 3 (3) An interface body, excluding any scoping units in it. 4A scoping unit that immediately surrounds another scoping unit is called the host scoping unit (often 5abbreviated to host). 62.2.1 Program 7A program consists of exactly one main program, any number (including zero) of other kinds of program 8units, and any number (including zero) of external procedures and other entities defined by means other 9than Fortran. NOTE 2.2 There is a restriction that there shall be no more than one unnamed block data program unit (11.3). This standard places no ordering requirement on the program units that constitute a program, but because the public portions of a module are required to be available by the time a module reference (11.2.1) is processed, a processor may require a particular order of processing of the program units. 102.2.2 Main program 11The Fortran main program is described in 11.1. 122.2.3 Procedure 13A procedure encapsulates an arbitrary sequence of actions that may be invoked directly during program 14execution. Procedures are either functions or subroutines. A function is a procedure that is invoked 15in an expression; its invocation causes a value to be computed which is then used in evaluating the 16expression. The variable that returns the value of a function is called the result variable. A subroutine 17is a procedure that is invoked in a CALL statement, by a defined assignment statement, or by some 18operations on derived-type entities. Unless it is a pure procedure, a subroutine may be used to change 19the program state by changing the values of any of the data objects accessible to the subroutine; unless 20it is a pure procedure, a function may do this in addition to computing the function value. 21Procedures are described further in Section 12. 222.2.3.1 External procedure 23An external procedure is a procedure that is defined by an external subprogram or by means other 24than Fortran. An external procedure may be invoked by the main program or by any procedure of a 25program. 262.2.3.2 Module procedure 27A module procedure is a procedure that is defined by a module subprogram (R1108). The module 28containing the subprogram is the host scoping unit of the module procedure. 292.2.3.3 Internal procedure 30An internal procedure is a procedure that is defined by an internal subprogram (R211). The containing 31main program or subprogram is the host scoping unit of the internal procedure. An internal procedure 12 MAY 2004 WORKING DRAFT J3/04-007 1is local to its host in the sense that the internal procedure is accessible within the host scoping unit and 2all its other internal procedures but is not accessible elsewhere. 32.2.3.4 Interface block 4An interface body describes an abstract interface or the interface of a dummy procedure, external 5procedure, procedure pointer, or type-bound procedure. 6An interface block is a specific interface block, an abstract interface block, or a generic interface block. 7A specific interface block is a collection of interface bodies. A generic interface block may also be used 8to specify that procedures may be invoked 9 (1) By using a generic name, 10 (2) By using a defined operator, 11 (3) By using a defined assignment, or 12 (4) For derived-type input/output. 132.2.4 Module 14A module contains (or accesses from other modules) definitions that are to be made accessible to other 15program units. These definitions include data object declarations, type definitions, procedure definitions, 16and interface blocks. A scoping unit in another program unit may access the definitions in a module. 17Modules are further described in Section 11. 182.3 Execution concepts 19Each Fortran statement is classified as either an executable statement or a nonexecutable statement. 20There are restrictions on the order in which statements may appear in a program unit, and not all 21executable statements may appear in all contexts. 222.3.1 Executable/nonexecutable statements 23Program execution is a sequence, in time, of actions. An executable statement is an instruction to 24perform or control one or more of these actions. Thus, the executable statements of a program unit 25determine the behavior of the program unit. The executable statements are all of those that make up 26the syntactic class executable-construct. 27Nonexecutable statements do not specify actions; they are used to configure the program environment 28in which actions take place. The nonexecutable statements are all those not classified as executable. 292.3.2 Statement order 30The syntax rules of subclause 2.1 specify the statement order within program units and subprograms. 31These rules are illustrated in Table 2.1 and Table 2.2. Table 2.1 shows the ordering rules for statements 32and applies to all program units, subprograms, and interface bodies. Vertical lines delineate varieties of 33statements that may be interspersed and horizontal lines delineate varieties of statements that shall not 34be interspersed. Internal or module subprograms shall follow a CONTAINS statement. Between USE 35and CONTAINS statements in a subprogram, nonexecutable statements generally precede executable 36statements, although the ENTRY statement, FORMAT statement, and DATA statement may appear 37among the executable statements. Table 2.2 shows which statements are allowed in a scoping unit. 13 J3/04-007 WORKING DRAFT MAY 2004 Table 2.1: Requirements on statement ordering PROGRAM, FUNCTION, SUBROUTINE, MODULE, or BLOCK DATA statement USE statements IMPORT statements IMPLICIT NONE PARAMETER IMPLICIT statements statements Derived-type definitions, FORMAT interface blocks, and PARAMETER type declaration statements, ENTRY and DATA enumeration definitions, statements statements procedure declarations, specification statements, and statement function statements DATA Executable statements constructs CONTAINS statement Internal subprograms or module subprograms END statement Table 2.2: Statements allowed in scoping units Kind of scoping unit: Main Module Block External Module Internal Interface program data subprog subprog subprog body USE statement Yes Yes Yes Yes Yes Yes Yes IMPORT statement No No No No No No Yes ENTRY statement No No No Yes Yes No No FORMAT statement Yes No No Yes Yes Yes No Misc. decls (see note) Yes Yes Yes Yes Yes Yes Yes DATA statement Yes Yes Yes Yes Yes Yes No Derived-type definition Yes Yes Yes Yes Yes Yes Yes Interface block Yes Yes No Yes Yes Yes Yes Executable statement Yes No No Yes Yes Yes No CONTAINS statement Yes Yes No Yes Yes No No Statement function statement Yes No No Yes Yes Yes No Notes for Table 2.2: 1) Misc. declarations are PARAMETER statements, IMPLICIT statements, type declaration statements, enumeration definitions, procedure declaration statements, and specification statements. 2) The scoping unit of a module does not include any module subprograms that the module contains. 12.3.3 The END statement 2An end-program-stmt, end-function-stmt, end-subroutine-stmt, end-module-stmt, or end-block-data-stmt 3is an END statement. Each program unit, module subprogram, and internal subprogram shall have 4exactly one END statement. The end-program-stmt, end-function-stmt, and end-subroutine-stmt state- 5ments are executable, and may be branch target statements (8.2). Executing an end-program-stmt causes 6normal termination of execution of the program. Executing an end-function-stmt or end-subroutine-stmt 14 MAY 2004 WORKING DRAFT J3/04-007 1is equivalent to executing a return-stmt with no scalar-int-expr. 2The end-module-stmt and end-block-data-stmt statements are nonexecutable. 32.3.4 Execution sequence 4If a program contains a Fortran main program, execution of the program begins with the first executable 5construct of the main program. The execution of a main program or subprogram involves execution of 6the executable constructs within its scoping unit. When a procedure is invoked, execution begins with 7the first executable construct appearing after the invoked entry point. With the following exceptions, 8the effect of execution is as if the executable constructs are executed in the order in which they appear 9in the main program or subprogram until a STOP, RETURN, or END statement is executed. The 10exceptions are the following: 11 (1) Execution of a branching statement (8.2) changes the execution sequence. These statements 12 explicitly specify a new starting place for the execution sequence. 13 (2) CASE constructs, DO constructs, IF constructs, and SELECT TYPE constructs contain 14 an internal statement structure and execution of these constructs involves implicit internal 15 branching. See Section 8 for the detailed semantics of each of these constructs. 16 (3) END=, ERR=, and EOR= specifiers may result in a branch. 17 (4) Alternate returns may result in a branch. 18Internal subprograms may precede the END statement of a main program or a subprogram. The 19execution sequence excludes all such definitions. 20Normal termination of execution of the program occurs if a STOP statement or end-program-stmt is 21executed. Normal termination of execution of a program also may occur during execution of a procedure 22defined by a companion processor (C International Standard 5.1.2.2.3 and 7.20.4.3). If normal termina- 23tion of execution occurs within a Fortran program unit and the program incorporates procedures defined 24by a companion processor, the process of execution termination shall include the effect of executing the 25C exit() function (C International Standard 7.20.4.3). 262.4 Data concepts 27Nonexecutable statements are used to specify the characteristics of the data environment. This includes 28typing variables, declaring arrays, and defining new types. 292.4.1 Type 30A type is a named category of data that is characterized by a set of values, a syntax for denoting 31these values, and a set of operations that interpret and manipulate the values. This central concept is 32described in 4.1. 33A type may be parameterized, in which case the set of data values, the syntax for denoting them, and 34the set of operations depend on the values of one or more parameters. Such a parameter is called a type 35parameter (4.2). 36There are two categories of types: intrinsic types and derived types. 372.4.1.1 Intrinsic type 38An intrinsic type is a type that is defined by the language, along with operations, and is always 39accessible. The intrinsic types are integer, real, complex, character, and logical. The properties of 40intrinsic types are described in 4.4. The intrinsic type parameters are KIND and LEN. 15 J3/04-007 WORKING DRAFT MAY 2004 1The kind type parameter indicates the decimal exponent range for the integer type (4.4.1), the 2decimal precision and exponent range for the real and complex types (4.4.2, 4.4.3), and the representation 3methods for the character and logical types (4.4.4, 4.4.5). The character length parameter specifies 4the number of characters for the character type. 52.4.1.2 Derived type 6A derived type is a type that is not defined by the language but requires a type definition to declare its 7components. A scalar object of such a derived type is called a structure (5.1.1.1). Derived types may 8be parameterized. Assignment of structures is defined intrinsically (7.4.1.3), but there are no intrinsic 9operations for structures. For each derived type, a structure constructor is available to provide values 10(4.5.9). In addition, data objects of derived type may be used as procedure arguments and function 11results, and may appear in input/output lists. If additional operations are needed for a derived type, 12they shall be supplied as procedure definitions. 13Derived types are described further in 4.5. 142.4.2 Data value 15Each intrinsic type has associated with it a set of values that a datum of that type may take, depending 16on the values of the type parameters. The values for each intrinsic type are described in 4.4. The values 17that objects of a derived type may assume are determined by the type definition, type parameter values, 18and the sets of values of its components. 192.4.3 Data entity 20A data entity is a data object, the result of the evaluation of an expression, or the result of the execution 21of a function reference (called the function result). A data entity has a type and type parameters; it 22may have a data value (an exception is an undefined variable). Every data entity has a rank and is thus 23either a scalar or an array. 242.4.3.1 Data object 25A data object (often abbreviated to object) is a constant (4.1.2), a variable (6), or a subobject of a 26constant. The type and type parameters of a named data object may be specified explicitly (5.1) or 27implicitly (5.3). 28Subobjects are portions of certain objects that may be referenced and defined (variables only) inde- 29pendently of the other portions. These include portions of arrays (array elements and array sections), 30portions of character strings (substrings), portions of complex objects (real and imaginary parts), and 31portions of structures (components). Subobjects are themselves data objects, but subobjects are refer- 32enced only by object designators or intrinsic functions. A subobject of a variable is a variable. Subobjects 33are described in Section 6. 34Objects referenced by a name are: a named scalar (a scalar object) 35 a named array (an array object) 36Subobjects referenced by an object designator are: an array element (a scalar subobject) an array section (an array subobject) a structure component (a scalar or an array subobject) 37 a substring (a scalar subobject) 16 MAY 2004 WORKING DRAFT J3/04-007 1Subobjects of complex objects may also be referenced by intrinsic functions. 22.4.3.1.1 Variable 3A variable may have a value and may be defined and redefined during execution of a program. 4A named local variable of the scoping unit of a module, main program, or subprogram, is a named 5variable that is a local entity of the scoping unit, is not a dummy argument, is not in COMMON, does 6not have the BIND attribute, and is not accessed by use or host association. A subobject of a named 7local variable is also a local variable. 82.4.3.1.2 Constant 9A constant has a value and cannot become defined, redefined, or undefined during execution of a 10program. A constant with a name is called a named constant and has the PARAMETER attribute 11(5.1.2.10). A constant without a name is called a literal constant (4.4). 122.4.3.1.3 Subobject of a constant 13A subobject of a constant is a portion of a constant. The portion referenced may depend on the 14value of a variable. NOTE 2.3 For example, given: CHARACTER (LEN = 10), PARAMETER :: DIGITS = '0123456789' CHARACTER (LEN = 1) :: DIGIT INTEGER :: I ... DIGIT = DIGITS (I:I) DIGITS is a named constant and DIGITS (I:I) designates a subobject of the constant DIGITS. 152.4.3.2 Expression 16An expression (7.1) produces a data entity when evaluated. An expression represents either a data 17reference or a computation; it is formed from operands, operators, and parentheses. The type, type 18parameters, value, and rank of an expression result are determined by the rules in Section 7. 192.4.3.3 Function reference 20A function reference (12.4.2) produces a data entity when the function is executed during expression 21evaluation. The type, type parameters, and rank of a function result are determined by the interface of 22the function (12.2.2). The value of a function result is determined by execution of the function. 232.4.4 Scalar 24A scalar is a datum that is not an array. Scalars may be of any intrinsic type or derived type. NOTE 2.4 A structure is scalar even if it has arrays as components. 25The rank of a scalar is zero. The shape of a scalar is represented by a rank-one array of size zero. 17 J3/04-007 WORKING DRAFT MAY 2004 12.4.5 Array 2An array is a set of scalar data, all of the same type and type parameters, whose individual elements 3are arranged in a rectangular pattern. An array element is one of the individual elements in the array 4and is a scalar. An array section is a subset of the elements of an array and is itself an array. 5An array may have up to seven dimensions, and any extent (number of elements) in any dimension. 6The rank of the array is the number of dimensions; its size is the total number of elements, which is 7equal to the product of the extents. An array may have zero size. The shape of an array is determined 8by its rank and its extent in each dimension, and may be represented as a rank-one array whose elements 9are the extents. All named arrays shall be declared, and the rank of a named array is specified in its 10declaration. The rank of a named array, once declared, is constant; the extents may be constant or may 11vary during execution. 12Two arrays are conformable if they have the same shape. A scalar is conformable with any array. Any 13intrinsic operation defined for scalar objects may be applied to conformable objects. Such operations 14are performed element-by-element to produce a resultant array conformable with the array operands. 15Element-by-element operation means corresponding elements of the operand arrays are involved in a 16scalar operation to produce the corresponding element in the result array, and all such element operations 17may be performed in any order or simultaneously. Such an operation is described as elemental. 18A rank-one array may be constructed from scalars and other arrays and may be reshaped into any 19allowable array shape (4.7). 20Arrays may be of any intrinsic type or derived type and are described further in 6.2. 212.4.6 Pointer 22A data pointer is a data entity that has the POINTER attribute. A procedure pointer is a procedure 23entity that has the POINTER attribute. A pointer is either a data pointer or a procedure pointer. 24A pointer is associated with a target by pointer assignment (7.4.2). A data pointer may also be 25associated with a target by allocation (6.3.1). A pointer is disassociated following execution of a 26NULLIFY statement, following pointer assignment with a disassociated pointer, by default initialization, 27or by explicit initialization. A data pointer may also be disassociated by execution of a DEALLOCATE 28statement. A disassociated pointer is not associated with a target (16.4.2). 29A pointer that is not associated shall not be referenced or defined. 30If a data pointer is an array, the rank is declared, but the extents are determined when the pointer is 31associated with a target. 322.4.7 Storage 33Many of the facilities of this standard make no assumptions about the physical storage characteristics of 34data objects. However, program units that include storage association dependent features shall observe 35the storage restrictions described in 16.4.3. 362.5 Fundamental terms 37For the purposes of this standard, the definitions of terms in this subclause apply. 18 MAY 2004 WORKING DRAFT J3/04-007 12.5.1 Name and designator 2A name is used to identify a program constituent, such as a program unit, named variable, named 3constant, dummy argument, or derived type. The rules governing the construction of names are given 4in 3.2.1. A designator is a name followed by zero or more component selectors, array section selectors, 5array element selectors, and substring selectors. 6An object designator is a designator for a data object. A procedure designator is a designator for 7a procedure. NOTE 2.5 An object name is a special case of an object designator. 82.5.2 Keyword 9The term keyword is used in two ways. 10 (1) It is used to describe a word that is part of the syntax of a statement. These keywords are 11 not reserved words; that is, names with the same spellings are allowed. In the syntax rules, 12 such keywords appear literally. In descriptive text, this meaning is denoted by the term 13 "keyword" without any modifier. Examples of statement keywords are: IF, READ, UNIT, 14 KIND, and INTEGER. 15 (2) It is used to denote names that identify items in a list. In actual argument lists, type 16 parameter lists, and structure constructors, items may be identified by a preceding keyword= 17 rather than their position within the list. An argument keyword is the name of a dummy 18 argument in the interface for the procedure being referenced, a type parameter keyword 19 is the name of a type parameter in the type being specified, and a component keyword 20 is the name of a component in a structure constructor. 21R215 keyword is name NOTE 2.6 Use of keywords rather than position to identify items in a list can make such lists more readable and allows them to be reordered. This facilitates specification of a list in cases where optional items are omitted. 222.5.3 Association 23Association is name association (16.4.1), pointer association (16.4.2), storage association (16.4.3), 24or inheritance association (16.4.4). Name association is argument association, host association, use 25association, linkage association, or construct association. 26Storage association causes different entities to use the same storage. Any association permits an entity 27to be identified by different names in the same scoping unit or by the same name or different names in 28different scoping units. 292.5.4 Declaration 30The term declaration refers to the specification of attributes for various program entities. Often this 31involves specifying the type of a named data object or specifying the shape of a named array object. 322.5.5 Definition 33The term definition is used in two ways. 19 J3/04-007 WORKING DRAFT MAY 2004 1 (1) It refers to the specification of derived types and procedures. 2 (2) When an object is given a valid value during program execution, it is said to become 3 defined. This is often accomplished by execution of an assignment or input statement. 4 When a variable does not have a predictable value, it is said to be undefined. Similarly, 5 when a pointer is associated with a target or nullified, its pointer association status is said 6 to become defined. When the association status of a pointer is not predictable, its pointer 7 association status is said to be undefined. 8Section 16 describes the ways in which variables may become defined and undefined. 92.5.6 Reference 10A data object reference is the appearance of the data object designator in a context requiring its 11value at that point during execution. 12A procedure reference is the appearance of the procedure designator, operator symbol, or assignment 13symbol in a context requiring execution of the procedure at that point. An occurrence of user-defined 14derived-type input/output (10.6.5) or derived-type finalization (4.5.5.1) is also a procedure reference. 15The appearance of a data object designator or procedure designator in an actual argument list does not 16constitute a reference to that data object or procedure unless such a reference is necessary to complete 17the specification of the actual argument. 18A module reference is the appearance of a module name in a USE statement (11.2.1). 192.5.7 Intrinsic 20The qualifier intrinsic has two meanings. 21 (1) The qualifier signifies that the term to which it is applied is defined in this standard. In- 22 trinsic applies to types, procedures, modules, assignment statements, and operators. All 23 intrinsic types, procedures, assignments, and operators may be used in any scoping unit 24 without further definition or specification. Intrinsic modules may be accessed by use as- 25 sociation. Intrinsic procedures and modules defined in this standard are called standard 26 intrinsic procedures and standard intrinsic modules, respectively. 27 (2) The qualifier applies to procedures or modules that are provided by a processor but are not 28 defined in this standard (13, 14, 15.1). Such procedures and modules are called nonstandard 29 intrinsic procedures and nonstandard intrinsic modules, respectively. 302.5.8 Operator 31An operator specifies a computation involving one (unary operator) or two (binary operator) data values 32(operands). This standard specifies a number of intrinsic operators (e.g., the arithmetic operators +, ­, 33*, /, and ** with numeric operands and the logical operators .AND., .OR., etc. with logical operands). 34Additional operators may be defined within a program (7.1.3). 352.5.9 Sequence 36A sequence is a set ordered by a one-to-one correspondence with the numbers 1, 2, through n. The 37number of elements in the sequence is n. A sequence may be empty, in which case it contains no elements. 38The elements of a nonempty sequence are referred to as the first element, second element, etc. The 39nth element, where n is the number of elements in the sequence, is called the last element. An empty 40sequence has no first or last element. 20 MAY 2004 WORKING DRAFT J3/04-007 12.5.10 Companion processors 2A processor has one or more companion processors. A companion processor is a processor-dependent 3mechanism by which global data and procedures may be referenced or defined. A companion processor 4may be a mechanism that references and defines such entities by a means other than Fortran (12.5.3), 5it may be the Fortran processor itself, or it may be another Fortran processor. If there is more than 6one companion processor, the means by which the Fortran processor selects among them are processor 7dependent. 8If a procedure is defined by means of a companion processor that is not the Fortran processor itself, 9this standard refers to the C function that defines the procedure, although the procedure need not be 10defined by means of the C programming language. NOTE 2.7 A companion processor might or might not be a mechanism that conforms to the requirements of the C International Standard. For example, a processor may allow a procedure defined by some language other than Fortran or C to be invoked if it can be described by a C prototype as defined in 6.5.5.3 of the C International Standard. 21 J3/04-007 WORKING DRAFT MAY 2004 22 MAY 2004 WORKING DRAFT J3/04-007 1Section 3: Characters, lexical tokens, and source form 2This section describes the Fortran character set and the various lexical tokens such as names and oper- 3ators. This section also describes the rules for the forms that Fortran programs may take. 43.1 Processor character set 5The processor character set is processor dependent. The structure of a processor character set is: 6 (1) Control characters 7 (2) Graphic characters 8 (a) Letters (3.1.1) 9 (b) Digits (3.1.2) 10 (c) Underscore (3.1.3) 11 (d) Special characters (3.1.4) 12 (e) Other characters (3.1.5) 13The letters, digits, underscore, and special characters make up the Fortran character set. 14R301 character is alphanumeric-character 15 or special-character 16R302 alphanumeric-character is letter 17 or digit 18 or underscore 19Except for the currency symbol, the graphics used for the characters shall be as given in 3.1.1, 3.1.2, 203.1.3, and 3.1.4. However, the style of any graphic is not specified. 21The default character type shall support a character set that includes the Fortran character set. By sup- 22plying nondefault character types, the processor may support additional character sets. The characters 23available in the ASCII and ISO 10646 character sets are specified by ISO/IEC 646:1991 (International 24Reference Version) and ISO/IEC 10646-1:2000 UCS-4, respectively; the characters available in other non- 25default character types are not specified by this standard, except that one character in each nondefault 26character type shall be designated as a blank character to be used as a padding character. 273.1.1 Letters 28The twenty-six letters are: 29 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z 30The set of letters defines the syntactic class letter. The processor character set shall include lower- 31case and upper-case letters. A lower-case letter is equivalent to the corresponding upper-case letter in 32program units except in a character context (3.3). NOTE 3.1 The following statements are equivalent: CALL BIG_COMPLEX_OPERATION (NDATE) call big_complex_operation (ndate) 23 J3/04-007 WORKING DRAFT MAY 2004 NOTE 3.1 (cont.) Call Big_Complex_Operation (NDate) 13.1.2 Digits 2The ten digits are: 3 0 1 2 3 4 5 6 7 8 9 4The ten digits define the syntactic class digit. 53.1.3 Underscore 6R303 underscore is 7The underscore may be used as a significant character in a name. 83.1.4 Special characters 9The special characters are shown in Table 3.1. Table 3.1: Special characters Character Name of character Character Name of character Blank ; Semicolon = Equals ! Exclamation point + Plus " Quotation mark or quote - Minus % Percent * Asterisk & Ampersand / Slash ~ Tilde \ Backslash < Less than ( Left parenthesis > Greater than ) Right parenthesis ? Question mark [ Left square bracket ' Apostrophe ] Right square bracket ` Grave accent { Left curly bracket ^ Circumflex accent } Right curly bracket | Vertical line , Comma $ Currency symbol . Decimal point or period # Number sign : Colon @ Commercial at 10The special characters define the syntactic class special-character. Some of the special characters are 11used for operator symbols, bracketing, and various forms of separating and delimiting other lexical 12tokens. 133.1.5 Other characters 14Additional characters may be representable in the processor, but may appear only in comments (3.3.1.1, 153.3.2.1), character constants (4.4.4), input/output records (9.1.1), and character string edit descriptors 16(10.2.1). 24 MAY 2004 WORKING DRAFT J3/04-007 13.2 Low-level syntax 2The low-level syntax describes the fundamental lexical tokens of a program unit. Lexical tokens are 3sequences of characters that constitute the building blocks of a program. They are keywords, names, 4literal constants other than complex literal constants, operators, labels, delimiters, comma, =, =>, :, ::, 5;, and %. 63.2.1 Names 7Names are used for various entities such as variables, program units, dummy arguments, named con- 8stants, and derived types. 9R304 name is letter [ alphanumeric-character ] ... 10C301 (R304) The maximum length of a name is 63 characters. NOTE 3.2 Examples of names: A1 NAME LENGTH (single underscore) S P R E A D O U T (two consecutive underscores) TRAILER (trailing underscore) NOTE 3.3 The word "name" always denotes this particular syntactic form. The word "identifier" is used where entities may be identified by other syntactic forms or by values; its particular meaning depends on the context in which it is used. 113.2.2 Constants 12R305 constant is literal-constant 13 or named-constant 14R306 literal-constant is int-literal-constant 15 or real-literal-constant 16 or complex-literal-constant 17 or logical-literal-constant 18 or char-literal-constant 19 or boz-literal-constant 20R307 named-constant is name 21R308 int-constant is constant 22C302 (R308)int-constant shall be of type integer. 23R309 char-constant is constant 24C303 (R309) char-constant shall be of type character. 253.2.3 Operators 26R310 intrinsic-operator is power-op 27 or mult-op 28 or add-op 29 or concat-op 25 J3/04-007 WORKING DRAFT MAY 2004 1 or rel-op 2 or not-op 3 or and-op 4 or or-op 5 or equiv-op 6R707 power-op is ** 7R708 mult-op is * 8 or / 9R709 add-op is + 10 or ­ 11R711 concat-op is // 12R713 rel-op is .EQ. 13 or .NE. 14 or .LT. 15 or .LE. 16 or .GT. 17 or .GE. 18 or == 19 or /= 20 or < 21 or <= 22 or > 23 or >= 24R718 not-op is .NOT. 25R719 and-op is .AND. 26R720 or-op is .OR. 27R721 equiv-op is .EQV. 28 or .NEQV. 29R311 defined-operator is defined-unary-op 30 or defined-binary-op 31 or extended-intrinsic-op 32R703 defined-unary-op is . letter [ letter ] ... . 33R723 defined-binary-op is . letter [ letter ] ... . 34R312 extended-intrinsic-op is intrinsic-operator 353.2.4 Statement labels 36A statement label provides a means of referring to an individual statement. 37R313 label is digit [ digit [ digit [ digit [ digit ] ] ] ] 38C304 (R313) At least one digit in a label shall be nonzero. 39If a statement is labeled, the statement shall contain a nonblank character. The same statement label 40shall not be given to more than one statement in a scoping unit. Leading zeros are not significant in 41distinguishing between statement labels. NOTE 3.4 For example: 99999 10 010 26 MAY 2004 WORKING DRAFT J3/04-007 NOTE 3.4 (cont.) are all statement labels. The last two are equivalent. There are 99999 unique statement labels and a processor shall accept any of them as a statement label. However, a processor may have an implementation limit on the total number of unique statement labels in one program unit. 1Any statement may have a statement label, but the labels are used only in the following ways: 2 (1) The label on a branch target statement (8.2) is used to identify that statement as the 3 possible destination of a branch. 4 (2) The label on a FORMAT statement (10.1.1) is used to identify that statement as the format 5 specification for a data transfer statement (9.5). 6 (3) In some forms of the DO construct (8.1.6), the range of the DO construct is identified by 7 the label on the last statement in that range. 83.2.5 Delimiters 9Delimiters are used to enclose syntactic lists. The following pairs are delimiters: 10( ... ) 11/ ... / 12[ ... ] 13(/ ... /) 143.3 Source form 15A Fortran program unit is a sequence of one or more lines, organized as Fortran statements, comments, 16and INCLUDE lines. A line is a sequence of zero or more characters. Lines following a program unit 17END statement are not part of that program unit. A Fortran statement is a sequence of one or more 18complete or partial lines. 19A character context means characters within a character literal constant (4.4.4) or within a character 20string edit descriptor (10.2.1). 21A comment may contain any character that may occur in any character context. 22There are two source forms: free and fixed. Free form and fixed form shall not be mixed in the same program unit. 23 The means for specifying the source form of a program unit are processor dependent. 243.3.1 Free source form 25In free source form there are no restrictions on where a statement (or portion of a statement) may 26appear within a line. A line may contain zero characters. If a line consists entirely of characters of 27default kind (4.4.4), it may contain at most 132 characters. If a line contains any character that is not 28of default kind, the maximum number of characters allowed on the line is processor dependent. 29Blank characters shall not appear within lexical tokens other than in a character context or in a format 30specification. Blanks may be inserted freely between tokens to improve readability; for example, blanks 31may occur between the tokens that form a complex literal constant. A sequence of blank characters 32outside of a character context is equivalent to a single blank character. 27 J3/04-007 WORKING DRAFT MAY 2004 1A blank shall be used to separate names, constants, or labels from adjacent keywords, names, constants, 2or labels. NOTE 3.5 For example, the blanks after REAL, READ, 30, and DO are required in the following: REAL X READ 10 30 DO K=1,3 3One or more blanks shall be used to separate adjacent keywords except in the following cases, where 4blanks are optional: Adjacent keywords where separating blanks are optional BLOCK DATA DOUBLE PRECISION ELSE IF ELSE WHERE END ASSOCIATE END BLOCK DATA END DO END ENUM END FILE END FORALL END FUNCTION END IF END INTERFACE END MODULE END PROGRAM END SELECT END SUBROUTINE END TYPE END WHERE GO TO IN OUT SELECT CASE SELECT TYPE 53.3.1.1 Free form commentary 6The character "!" initiates a comment except where it appears within a character context. The 7comment extends to the end of the line. If the first nonblank character on a line is an "!", the line 8is a comment line. Lines containing only blanks or containing no characters are also comment lines. 9Comments may appear anywhere in a program unit and may precede the first statement of a program 10unit or may follow the last statement of a program unit. Comments have no effect on the interpretation 11of the program unit. NOTE 3.6 The standard does not restrict the number of consecutive comment lines. 123.3.1.2 Free form statement continuation 13The character "&" is used to indicate that the current statement is continued on the next line that is not 14a comment line. Comment lines cannot be continued; an "&" in a comment has no effect. Comments may 15occur within a continued statement. When used for continuation, the "&" is not part of the statement. 16No line shall contain a single "&" as the only nonblank character or as the only nonblank character 17before an "!" that initiates a comment. 18If a noncharacter context is to be continued, an "&" shall be the last nonblank character on the line, 19or the last nonblank character before an "!". There shall be a later line that is not a comment; the 20statement is continued on the next such line. If the first nonblank character on that line is an "&", the 21statement continues at the next character position following that "&"; otherwise, it continues with the 22first character position of that line. 28 MAY 2004 WORKING DRAFT J3/04-007 1 If a lexical token is split across the end of a line, the first nonblank character on the first following 2 noncomment line shall be an "&" immediately followed by the successive characters of the split token. 3 If a character context is to be continued, an "&" shall be the last nonblank character on the line and 4 shall not be followed by commentary. There shall be a later line that is not a comment; an "&" shall be 5 the first nonblank character on the next such line and the statement continues with the next character 6 following that "&". 7 3.3.1.3 Free form statement termination 8 If a statement is not continued, a comment or the end of the line terminates the statement. 9 A statement may alternatively be terminated by a ";" character that appears other than in a character 10 context or in a comment. The ";" is not part of the statement. After a ";" terminator, another statement 11 may appear on the same line, or begin on that line and be continued. A ";" shall not appear as the first 12 nonblank character on a line. A sequence consisting only of zero or more blanks and one or more ";" 13 terminators, in any order, is equivalent to a single ";" terminator. 14 3.3.1.4 Free form statements 15 A label may precede any statement not forming part of another statement. NOTE 3.7 No Fortran statement begins with a digit. 16 A statement shall not have more than 255 continuation lines. 17 3.3.2 Fixed source form 18 In fixed source form, there are restrictions on where a statement may appear within a line. If a source line contains only 19 default kind characters, it shall contain exactly 72 characters; otherwise, its maximum number of characters is processor 20 dependent. 21 Except in a character context, blanks are insignificant and may be used freely throughout the program. 22 3.3.2.1 Fixed form commentary 23 The character "!" initiates a comment except where it appears within a character context or in character position 6. The 24 comment extends to the end of the line. If the first nonblank character on a line is an "!" in any character position other 25 than character position 6, the line is a comment line. Lines beginning with a "C" or "*" in character position 1 and lines 26 containing only blanks are also comment lines. Comments may appear anywhere in a program unit and may precede the 27 first statement of the program unit or may follow the last statement of a program unit. Comments have no effect on the 28 interpretation of the program unit. NOTE 3.8 The standard does not restrict the number of consecutive comment lines. 293.3.2.2 Fixed form statement continuation 30 Except within commentary, character position 6 is used to indicate continuation. If character position 6 contains a blank 31 or zero, the line is the initial line of a new statement, which begins in character position 7. If character position 6 contains 32 any character other than blank or zero, character positions 7­72 of the line constitute a continuation of the preceding 33 noncomment line. NOTE 3.9 An "!" or ";" in character position 6 is interpreted as a continuation indicator unless it appears within commentary indicated by a "C" or "*" in character position 1 or by an "!" in character positions 1­5. 29 J3/04-007 WORKING DRAFT MAY 2004 1 Comment lines cannot be continued. Comment lines may occur within a continued statement. 23.3.2.3 Fixed form statement termination 3 If a statement is not continued, a comment or the end of the line terminates the statement. 4 A statement may alternatively be terminated by a ";" character that appears other than in a character context, in a 5 comment, or in character position 6. The ";" is not part of the statement. After a ";" terminator, another statement may 6 begin on the same line, or begin on that line and be continued. A ";" shall not appear as the first nonblank character on 7 a line, except in character position 6. A sequence consisting only of zero or more blanks and one or more ";" terminators, 8 in any order, is equivalent to a single ";" terminator. 93.3.2.4 Fixed form statements 10 A label, if present, shall occur in character positions 1 through 5 of the first line of a statement; otherwise, positions 1 11 through 5 shall be blank. Blanks may appear anywhere within a label. A statement following a ";" on the same line shall 12 not be labeled. Character positions 1 through 5 of any continuation lines shall be blank. A statement shall not have more 13 than 255 continuation lines. The program unit END statement shall not be continued. A statement whose initial line 14 appears to be a program unit END statement shall not be continued. 153.4 Including source text 16Additional text may be incorporated into the source text of a program unit during processing. This is 17accomplished with the INCLUDE line, which has the form 18 INCLUDE char-literal-constant 19The char-literal-constant shall not have a kind type parameter value that is a named-constant. 20An INCLUDE line is not a Fortran statement. 21An INCLUDE line shall appear on a single source line where a statement may appear; it shall be the 22only nonblank text on this line other than an optional trailing comment. Thus, a statement label is not 23allowed. 24The effect of the INCLUDE line is as if the referenced source text physically replaced the INCLUDE line 25prior to program processing. Included text may contain any source text, including additional INCLUDE 26lines; such nested INCLUDE lines are similarly replaced with the specified source text. The maximum 27depth of nesting of any nested INCLUDE lines is processor dependent. Inclusion of the source text 28referenced by an INCLUDE line shall not, at any level of nesting, result in inclusion of the same source 29text. 30When an INCLUDE line is resolved, the first included statement line shall not be a continuation line 31and the last included statement line shall not be continued. 32The interpretation of char-literal-constant is processor dependent. An example of a possible valid inter- 33pretation is that char-literal-constant is the name of a file that contains the source text to be included. NOTE 3.10 In some circumstances, for example where source code is maintained in an INCLUDE file for use in programs whose source form might be either fixed or free, observing the following rules allows the code to be used with either source form: (1) Confine statement labels to character positions 1 to 5 and statements to character positions 7 to 72; (2) Treat blanks as being significant; 30 MAY 2004 WORKING DRAFT J3/04-007 NOTE 3.10 (cont.) (3) Use only the exclamation mark (!) to indicate a comment, but do not start the comment in character position 6; (4) For continued statements, place an ampersand (&) in both character position 73 of a continued line and character position 6 of a continuing line. 31 J3/04-007 WORKING DRAFT MAY 2004 32 MAY 2004 WORKING DRAFT J3/04-007 1Section 4: Types 2Fortran provides an abstract means whereby data may be categorized without relying on a particular 3physical representation. This abstract means is the concept of type. 4An intrinsic type is one that is defined by the language. The intrinsic types are integer, real, complex, 5character, and logical. 6A derived type is one that is defined by a derived-type definition (4.5.1). 7A derived type may be used only where its definition is accessible (4.5.1.1). An intrinsic type is always 8accessible. 9A type is specified in several contexts by a type specifier. 10R401 type-spec is intrinsic-type-spec 11 or derived-type-spec 12C401 (R401) The derived-type-spec shall not specify an abstract type (4.5.6). 134.1 The concept of type 14A type has a name, a set of valid values, a means to denote such values (constants), and a set of 15operations to manipulate the values. NOTE 4.1 For example, the logical type has a set of two values, denoted by the lexical tokens .TRUE. and .FALSE., which are manipulated by logical operations. An example of a less restricted type is the integer type. This type has a processor-dependent set of integer numeric values, each of which is denoted by an optional sign followed by a string of digits, and which may be manipulated by integer arithmetic operations and relational operations. 164.1.1 Set of values 17For each type, there is a set of valid values. The set of valid values may be completely determined, as is 18the case for logical, or may be determined by a processor-dependent method, as is the case for integer, 19character, and real. For complex, the set of valid values consists of the set of all the combinations of the 20values of the individual components. For derived types, the set of valid values is as defined in 4.5.7. 214.1.2 Constants 22The syntax for literal constants of each intrinsic type is specified in 4.4. 23The syntax for denoting a value indicates the type, type parameters, and the particular value. 24A constant value may be given a name (5.1.2.10, 5.2.9). 25A structure constructor (4.5.9) may be used to construct a constant value of derived type from an 26appropriate sequence of initialization expressions (7.1.7). Such a constant value is considered to be a 27scalar even though the value may have components that are arrays. 33 J3/04-007 WORKING DRAFT MAY 2004 14.1.3 Operations 2For each of the intrinsic types, a set of operations and corresponding operators is defined intrinsically. 3These are described in Section 7. The intrinsic set may be augmented with operations and operators 4defined by functions with the OPERATOR interface (12.3.2.1). Operator definitions are described in 5Sections 7 and 12. 6For derived types, there are no intrinsic operations. Operations on derived types may be defined by the 7program (4.5.10). 84.2 Type parameters 9A type may be parameterized. In this case, the set of values, the syntax for denoting the values, and 10the set of operations on the values of the type depend on the values of the parameters. 11The intrinsic types are all parameterized. Derived types may be defined to be parameterized. 12A type parameter is either a kind type parameter or a length type parameter. 13A kind type parameter may be used in initialization and specification expressions within the derived-type 14definition (4.5.1) for the type; it participates in generic resolution (16.2.3). Each of the intrinsic types 15has a kind type parameter named KIND, which is used to distinguish multiple representations of the 16intrinsic type. NOTE 4.2 By design, the value of a kind type parameter is known at compile time. Some parameterizations that involve multiple representation forms need to be distinguished at compile time for practical implementation and performance. Examples include the multiple precisions of the intrinsic real type and the possible multiple character sets of the intrinsic character type. A type parameter of a derived type may be specified to be a kind type parameter in order to allow generic resolution based on the parameter; that is to allow a single generic to include two specific procedures that have interfaces distinguished only by the value of a kind type parameter of a dummy argument. Generics are designed to be resolvable at compile time. 17A length type parameter may be used in specification expressions within the derived-type definition for 18the type, but it shall not be used in initialization expressions. The intrinsic character type has a length 19type parameter named LEN, which is the length of the string. NOTE 4.3 The adjective "length" is used for type parameters other than kind type parameters because they often specify a length, as for intrinsic character type. However, they may be used for other purposes. The important difference from kind type parameters is that their values need not be known at compile time and might change during execution. 20A type parameter value may be specified with a type specification (4.4, 4.5.8). 21R402 type-param-value is scalar-int-expr 22 or * 23 or : 24C402 (R402) The type-param-value for a kind type parameter shall be an initialization expression. 25C403 (R402) A colon may be used as a type-param-value only in the declaration of an entity or 34 MAY 2004 WORKING DRAFT J3/04-007 1 component that has the POINTER or ALLOCATABLE attribute. 2A deferred type parameter is a length type parameter whose value can change during execution of 3the program. A colon as a type-param-value specifies a deferred type parameter. 4The values of the deferred type parameters of an object are determined by successful execution of an 5ALLOCATE statement (6.3.1), execution of an intrinsic assignment statement (7.4.1.3), execution of a 6pointer assignment statement (7.4.2), or by argument association (12.4.1.2). NOTE 4.4 Deferred type parameters of functions, including function procedure pointers, have no values. Instead, they indicate that those type parameters of the function result will be determined by execution of the function, if it returns an allocated allocatable result or an associated pointer result. 7An assumed type parameter is a length type parameter for a dummy argument that assumes the 8type parameter value from the corresponding actual argument; it is also used for an associate name in a 9SELECT TYPE construct that assumes the type parameter value from the corresponding selector. An 10asterisk as a type-param-value specifies an assumed type parameter. 114.3 Relationship of types and values to objects 12The name of a type serves as a type specifier and may be used to declare objects of that type. A 13declaration specifies the type of a named object. A data object may be declared explicitly or implicitly. 14Data objects may have attributes in addition to their types. Section 5 describes the way in which a data 15object is declared and how its type and other attributes are specified. 16Scalar data of any intrinsic or derived type may be shaped in a rectangular pattern to compose an array 17of the same type and type parameters. An array object has a type and type parameters just as a scalar 18object does. 19A variable is a data object. The type and type parameters of a variable determine which values that 20variable may take. Assignment provides one means of defining or redefining the value of a variable of 21any type. Assignment is defined intrinsically for all types where the type, type parameters, and shape 22of both the variable and the value to be assigned to it are identical. Assignment between objects of 23certain differing intrinsic types, type parameters, and shapes is described in Section 7. A subroutine and 24a generic interface (4.5.1, 12.3.2.1) whose generic specifier is ASSIGNMENT (=) define an assignment 25that is not defined intrinsically or redefine an intrinsic derived-type assignment (7.4.1.4). NOTE 4.5 For example, assignment of a real value to an integer variable is defined intrinsically. 26The type of a variable determines the operations that may be used to manipulate the variable. 274.4 Intrinsic types 28The intrinsic types are: numeric types: integer, real, and complex 29 nonnumeric types: character and logical 30The numeric types are provided for numerical computation. The normal operations of arithmetic, 31addition (+), subtraction (­), multiplication (*), division (/), exponentiation (**), identity (unary +), 35 J3/04-007 WORKING DRAFT MAY 2004 1and negation (unary ­), are defined intrinsically for the numeric types. 2R403 intrinsic-type-spec is INTEGER [ kind-selector ] 3 or REAL [ kind-selector ] 4 or DOUBLE PRECISION 5 or COMPLEX [ kind-selector ] 6 or CHARACTER [ char-selector ] 7 or LOGICAL [ kind-selector ] 8R404 kind-selector is ( [ KIND = ] scalar-int-initialization-expr ) 9C404 (R404) The value of scalar-int-initialization-expr shall be nonnegative and shall specify a rep- 10 resentation method that exists on the processor. 114.4.1 Integer type 12The set of values for the integer type is a subset of the mathematical integers. A processor shall 13provide one or more representation methods that define sets of values for data of type integer. Each 14such method is characterized by a value for a type parameter called the kind type parameter. The kind 15type parameter of a representation method is returned by the intrinsic inquiry function KIND (13.7.59). 16The decimal exponent range of a representation method is returned by the intrinsic function RANGE 17(13.7.96). The intrinsic function SELECTED INT KIND (13.7.105) returns a kind value based on a 18specified decimal range requirement. The integer type includes a zero value, which is considered neither 19negative nor positive. The value of a signed integer zero is the same as the value of an unsigned integer 20zero. 21The type specifier for the integer type uses the keyword INTEGER. 22If the kind type parameter is not specified, the default kind value is KIND (0) and the type specified is 23default integer. 24Any integer value may be represented as a signed-int-literal-constant. 25R405 signed-int-literal-constant is [ sign ] int-literal-constant 26R406 int-literal-constant is digit-string [ kind-param ] 27R407 kind-param is digit-string 28 or scalar-int-constant-name 29R408 signed-digit-string is [ sign ] digit-string 30R409 digit-string is digit [ digit ] ... 31R410 sign is + 32 or ­ 33C405 (R407) A scalar-int-constant-name shall be a named constant of type integer. 34C406 (R407) The value of kind-param shall be nonnegative. 35C407 (R406) The value of kind-param shall specify a representation method that exists on the pro- 36 cessor. 37The optional kind type parameter following digit-string specifies the kind type parameter of the integer 38constant; if it is not present, the constant is of type default integer. 39An integer constant is interpreted as a decimal value. NOTE 4.6 Examples of signed integer literal constants are: 36 MAY 2004 WORKING DRAFT J3/04-007 NOTE 4.6 (cont.) 473 +56 -101 21_2 21_SHORT 1976354279568241_8 where SHORT is a scalar integer named constant. 1R411 boz-literal-constant is binary-constant 2 or octal-constant 3 or hex-constant 4R412 binary-constant is B ' digit [ digit ] ... ' 5 or B " digit [ digit ] ... " 6C408 (R412) digit shall have one of the values 0 or 1. 7R413 octal-constant is O ' digit [ digit ] ... ' 8 or O " digit [ digit ] ... " 9C409 (R413) digit shall have one of the values 0 through 7. 10R414 hex-constant is Z ' hex-digit [ hex-digit ] ... ' 11 or Z " hex-digit [ hex-digit ] ... " 12R415 hex-digit is digit 13 or A 14 or B 15 or C 16 or D 17 or E 18 or F 19Binary, octal and hexadecimal constants are interpreted according to their respective number systems. 20The hex-digits A through F represent the numbers ten through fifteen, respectively; they may be repre- 21sented by their lower-case equivalents. 22C410 (R411) A boz-literal-constant shall appear only as a data-stmt-constant in a DATA statement, as 23 the actual argument associated with the dummy argument A of the numeric intrinsic functions 24 DBLE, REAL or INT, or as the actual argument associated with the X or Y dummy argument 25 of the intrinsic function CMPLX. 264.4.2 Real type 27The real type has values that approximate the mathematical real numbers. A processor shall provide 28two or more approximation methods that define sets of values for data of type real. Each such method 29has a representation method and is characterized by a value for a type parameter called the kind type 30parameter. The kind type parameter of an approximation method is returned by the intrinsic inquiry 31function KIND (13.7.59). The decimal precision and decimal exponent range of an approximation 32method are returned by the intrinsic functions PRECISION (13.7.90) and RANGE (13.7.96). The 33intrinsic function SELECTED REAL KIND (13.7.106) returns a kind value based on specified precision 34and decimal range requirements. 37 J3/04-007 WORKING DRAFT MAY 2004 NOTE 4.7 See C.1.2 for remarks concerning selection of approximation methods. 1The real type includes a zero value. Processors that distinguish between positive and negative zeros 2shall treat them as equivalent 3 (1) in all relational operations, 4 (2) as actual arguments to intrinsic procedures other than those for which it is explicitly specified 5 that negative zero is distinguished, and 6 (3) as the scalar-numeric-expr in an arithmetic IF. NOTE 4.8 On a processor that can distinguish between 0.0 and -0.0, ( X >= 0.0 ) evaluates to true if X = 0.0 or if X = -0.0, ( X < 0.0 ) evaluates to false for X = -0.0, and IF (X) 1,2,3 causes a transfer of control to the branch target statement with the statement label "2" for both X = 0.0 and X = -0.0. In order to distinguish between 0.0 and -0.0, a program should use the SIGN function. SIGN(1.0,X) will return -1.0 if X < 0.0 or if the processor distinguishes between 0.0 and -0.0 and X has the value -0.0. 7The type specifier for the real type uses the keyword REAL. The keyword DOUBLE PRECISION is an 8alternate specifier for one kind of real type. 9If the type keyword REAL is specified and the kind type parameter is not specified, the default kind 10value is KIND (0.0) and the type specified is default real. If the type keyword DOUBLE PRECISION 11is specified, the kind value is KIND (0.0D0) and the type specified is double precision real. The 12decimal precision of the double precision real approximation method shall be greater than that of the 13default real method. 14R416 signed-real-literal-constant is [ sign ] real-literal-constant 15R417 real-literal-constant is significand [ exponent-letter exponent ] [ kind-param ] 16 or digit-string exponent-letter exponent [ kind-param ] 17R418 significand is digit-string . [ digit-string ] 18 or . digit-string 19R419 exponent-letter is E 20 or D 21R420 exponent is signed-digit-string 22C411 (R417) If both kind-param and exponent-letter are present, exponent-letter shall be E. 23C412 (R417) The value of kind-param shall specify an approximation method that exists on the 24 processor. 25A real literal constant without a kind type parameter is a default real constant if it is without an 38 MAY 2004 WORKING DRAFT J3/04-007 1exponent part or has exponent letter E, and is a double precision real constant if it has exponent letter 2D. A real literal constant written with a kind type parameter is a real constant with the specified kind 3type parameter. 4The exponent represents the power of ten scaling to be applied to the significand or digit string. The 5meaning of these constants is as in decimal scientific notation. 6The significand may be written with more digits than a processor will use to approximate the value of 7the constant. NOTE 4.9 Examples of signed real literal constants are: -12.78 +1.6E3 2.1 -16.E4_8 0.45D-4 10.93E7_QUAD .123 3E4 where QUAD is a scalar integer named constant. 84.4.3 Complex type 9The complex type has values that approximate the mathematical complex numbers. The values of a 10complex type are ordered pairs of real values. The first real value is called the real part, and the second 11real value is called the imaginary part. 12Each approximation method used to represent data entities of type real shall be available for both the 13real and imaginary parts of a data entity of type complex. A kind type parameter may be specified for 14a complex entity and selects for both parts the real approximation method characterized by this kind 15type parameter value. The kind type parameter of an approximation method is returned by the intrinsic 16inquiry function KIND (13.7.59). 17The type specifier for the complex type uses the keyword COMPLEX. There is no keyword for double 18precision complex. If the type keyword COMPLEX is specified and the kind type parameter is not 19specified, the default kind value is the same as that for default real, the type of both parts is default 20real, and the type specified is default complex. 21R421 complex-literal-constant is ( real-part , imag-part ) 22R422 real-part is signed-int-literal-constant 23 or signed-real-literal-constant 24 or named-constant 25R423 imag-part is signed-int-literal-constant 26 or signed-real-literal-constant 27 or named-constant 28C413 (R421) Each named constant in a complex literal constant shall be of type integer or real. 29If the real part and the imaginary part of a complex literal constant are both real, the kind type 30parameter value of the complex literal constant is the kind type parameter value of the part with the 31greater decimal precision; if the precisions are the same, it is the kind type parameter value of one of the 32parts as determined by the processor. If a part has a kind type parameter value different from that of 39 J3/04-007 WORKING DRAFT MAY 2004 1the complex literal constant, the part is converted to the approximation method of the complex literal 2constant. 3If both the real and imaginary parts are integer, they are converted to the default real approximation 4method and the constant is of type default complex. If only one of the parts is an integer, it is converted 5to the approximation method selected for the part that is real and the kind type parameter value of the 6complex literal constant is that of the part that is real. NOTE 4.10 Examples of complex literal constants are: (1.0, -1.0) (3, 3.1E6) (4.0_4, 3.6E7_8) ( 0., PI) where PI is a previously declared named real constant. 74.4.4 Character type 8The character type has a set of values composed of character strings. A character string is a sequence 9of characters, numbered from left to right 1, 2, 3, ... up to the number of characters in the string. The 10number of characters in the string is called the length of the string. The length is a type parameter; its 11value is greater than or equal to zero. Strings of different lengths are all of type character. 12A processor shall provide one or more representation methods that define sets of values for data of 13type character. Each such method is characterized by a value for a type parameter called the kind type 14parameter. The kind type parameter of a representation method is returned by the intrinsic inquiry 15function KIND (13.7.59). The intrinsic function SELECTED CHAR KIND (13.7.104) returns a kind 16value based on the name of a character type. Any character of a particular representation method 17representable in the processor may occur in a character string of that representation method. 18The character set defined by ISO/IEC 646:1991 (International Reference Version) is referred to as the 19ASCII character set or the ASCII character type. The character set defined by ISO/IEC 10646- 201:2000 UCS-4 is referred to as the ISO 10646 character set or the ISO 10646 character type. 214.4.4.1 Character type specifier 22The type specifier for the character type uses the keyword CHARACTER. 23If the kind type parameter is not specified, the default kind value is KIND ('A') and the type specified 24is default character. 25R424 char-selector is length-selector 26 or ( LEN = type-param-value , 27 KIND = scalar-int-initialization-expr ) 28 or ( type-param-value , 29 [ KIND = ] scalar-int-initialization-expr ) 30 or ( KIND = scalar-int-initialization-expr 31 [ , LEN =type-param-value ] ) 32R425 length-selector is ( [ LEN = ] type-param-value ) 33 or * char-length [ , ] 34R426 char-length is ( type-param-value ) 40 MAY 2004 WORKING DRAFT J3/04-007 1 or scalar-int-literal-constant 2C414 (R424) The value of scalar-int-initialization-expr shall be nonnegative and shall specify a rep- 3 resentation method that exists on the processor. 4C415 (R426) The scalar-int-literal-constant shall not include a kind-param. 5C416 (R424 R425 R426) A type-param-value of * may be used only in the following ways: 6 (1) to declare a dummy argument, 7 (2) to declare a named constant, 8 (3) in the type-spec of an ALLOCATE statement wherein each allocate-object is a dummy 9 argument of type CHARACTER with an assumed character length, or 10 (4) in an external function, to declare the character length parameter of the function result. 11C417 A function name shall not be declared with an asterisk type-param-value unless it is of type CHAR- 12 ACTER and is the name of the result of an external function or the name of a dummy function. 13C418 A function name declared with an asterisk type-param-value shall not be an array, a pointer, recursive, or pure. 14C419 (R425) The optional comma in a length-selector is permitted only in a declaration-type-spec in a type-declaration- 15 stmt. 16C420 (R425) The optional comma in a length-selector is permitted only if no double-colon separator appears in the 17 type-declaration-stmt. 18C421 (R424) The length specified for a character statement function or for a statement function dummy argument of 19 type character shall be an initialization expression. 20The char-selector in a CHARACTER intrinsic-type-spec and the * char-length in an entity-decl or in 21a component-decl of a type definition specify character length. The * char-length in an entity-decl or 22a component-decl specifies an individual length and overrides the length specified in the char-selector, 23if any. If a * char-length is not specified in an entity-decl or a component-decl, the length-selector or 24type-param-value specified in the char-selector is the character length. If the length is not specified in a 25char-selector or a * char-length, the length is 1. 26If the character length parameter value evaluates to a negative value, the length of character entities 27declared is zero. A character length parameter value of : indicates a deferred type parameter (4.2). A 28char-length type parameter value of * has the following meaning: 29 (1) If used to declare a dummy argument of a procedure, the dummy argument assumes the 30 length of the associated actual argument. 31 (2) If used to declare a named constant, the length is that of the constant value. 32 (3) If used in the type-spec of an ALLOCATE statement, each allocate-object assumes its length 33 from the associated actual argument. 34 (4) If used to specify the character length parameter of a function result, any scoping unit invoking the function 35 shall declare the function name with a character length parameter value other than * or access such a 36 definition by host or use association. When the function is invoked, the length of the result variable in the 37 function is assumed from the value of this type parameter. 384.4.4.2 Character literal constant 39A character literal constant is written as a sequence of characters, delimited by either apostrophes 40or quotation marks. 41 J3/04-007 WORKING DRAFT MAY 2004 1R427 char-literal-constant is [ kind-param ] ' [ rep-char ] ... ' 2 or [ kind-param ] " [ rep-char ] ... " 3C422 (R427) The value of kind-param shall specify a representation method that exists on the pro- 4 cessor. 5The optional kind type parameter preceding the leading delimiter specifies the kind type parameter of 6the character constant; if it is not present, the constant is of type default character. 7For the type character with kind kind-param, if present, and for type default character otherwise, a 8representable character, rep-char, is defined as follows: 9 (1) In free source form, it is any graphic character in the processor-dependent character set. 10 (2) In fixed source form, it is any character in the processor-dependent character set. A processor may restrict 11 the occurrence of some or all of the control characters. NOTE 4.11 Fortran 77 allowed any character to occur in a character context. This standard allows a source program to contain characters of more than one kind. Some processors may identify characters of nondefault kinds by control characters (called "escape" or "shift" characters). It is difficult, if not impossible, to process, edit, and print files where some instances of control characters have their intended meaning and some instances might not. Almost all control characters have uses or effects that effectively preclude their use in character contexts and this is why free source form allows only graphic characters as representable characters. Nevertheless, for compatibility with Fortran 77, control characters remain permitted in principle in fixed source form. 12The delimiting apostrophes or quotation marks are not part of the value of the character literal constant. 13An apostrophe character within a character constant delimited by apostrophes is represented by two 14consecutive apostrophes (without intervening blanks); in this case, the two apostrophes are counted as 15one character. Similarly, a quotation mark character within a character constant delimited by quotation 16marks is represented by two consecutive quotation marks (without intervening blanks) and the two 17quotation marks are counted as one character. 18A zero-length character literal constant is represented by two consecutive apostrophes (without inter- 19vening blanks) or two consecutive quotation marks (without intervening blanks) outside of a character 20context. 21The intrinsic operation concatenation (//) is defined between two data entities of type character (7.2.2) 22with the same kind type parameter. NOTE 4.12 Examples of character literal constants are: "DON'T" 'DON''T' both of which have the value DON'T and '' which has the zero-length character string as its value. 42 MAY 2004 WORKING DRAFT J3/04-007 NOTE 4.13 An example of a nondefault character literal constant, where the processor supports the corre- sponding character set, is: ˇ ˘ Ł ¤ ˘ Ą ¦ § NIHONGO ' ' where NIHONGO is a named constant whose value is the kind type parameter for Nihongo (Japanese) characters. 14.4.4.3 Collating sequence 2Each implementation defines a collating sequence for the character set of each kind of character. A 3collating sequence is a one-to-one mapping of the characters into the nonnegative integers such that 4each character corresponds to a different nonnegative integer. The intrinsic functions CHAR (13.7.19) 5and ICHAR (13.7.50) provide conversions between the characters and the integers according to this 6mapping. NOTE 4.14 For example: ICHAR ( 'X' ) returns the integer value of the character 'X' according to the collating sequence of the processor. 7For the default character type, the only constraints on the collating sequence are the following: 8 (1) ICHAR ('A') < ICHAR ('B') < ... < ICHAR ('Z') for the twenty-six upper-case letters. 9 (2) ICHAR ('0') < ICHAR ('1') < ... < ICHAR ('9') for the ten digits. 10 (3) ICHAR (' ') < ICHAR ('0') < ICHAR ('9') < ICHAR ('A') or 11 ICHAR (' ') < ICHAR ('A') < ICHAR ('Z') < ICHAR ('0'). 12 (4) ICHAR ('a') < ICHAR ('b') < ... < ICHAR ('z') for the twenty-six lower-case letters. 13 (5) ICHAR (' ') < ICHAR ('0') < ICHAR ('9') < ICHAR ('a') or 14 ICHAR (' ') < ICHAR ('a') < ICHAR ('z') < ICHAR ('0'). 15Except for blank, there are no constraints on the location of the special characters and underscore in 16the collating sequence, nor is there any specified collating sequence relationship between the upper-case 17and lower-case letters. 18The collating sequence for the ASCII character type is as defined by ISO/IEC 646:1991 (International 19Reference Version); this collating sequence is called the ASCII collating sequence in this standard. 20The collating sequence for the ISO 10646 character type is as defined by ISO/IEC 10646-1:2000. NOTE 4.15 The intrinsic functions ACHAR (13.7.2) and IACHAR (13.7.45) provide conversion between char- acters and corresponding integer values according to the ASCII collating sequence. 21The intrinsic functions LGT, LGE, LLE, and LLT (13.7.63-13.7.66) provide comparisons between strings 22based on the ASCII collating sequence. International portability is guaranteed if the set of characters 23used is limited to the letters, digits, underscore, and special characters. 244.4.5 Logical type 25The logical type has two values, which represent true and false. 43 J3/04-007 WORKING DRAFT MAY 2004 1A processor shall provide one or more representation methods for data of type logical. Each such 2method is characterized by a value for a type parameter called the kind type parameter. The kind type 3parameter of a representation method is returned by the intrinsic inquiry function KIND (13.7.59). 4The type specifier for the logical type uses the keyword LOGICAL. 5If the kind type parameter is not specified, the default kind value is KIND (.FALSE.) and the type 6specified is default logical. 7R428 logical-literal-constant is .TRUE. [ kind-param ] 8 or .FALSE. [ kind-param ] 9C423 (R428) The value of kind-param shall specify a representation method that exists on the pro- 10 cessor. 11The optional kind type parameter following the trailing delimiter specifies the kind type parameter of 12the logical constant; if it is not present, the constant is of type default logical. 13The intrinsic operations defined for data entities of logical type are: negation (.NOT.), conjunction 14(.AND.), inclusive disjunction (.OR.), logical equivalence (.EQV.), and logical nonequivalence (.NEQV.) 15as described in 7.2.4. There is also a set of intrinsically defined relational operators that compare the 16values of data entities of other types and yield a value of type default logical. These operations are 17described in 7.2.3. 184.5 Derived types 19Additional types may be derived from the intrinsic types and other derived types. A type definition is 20required to define the name of the type and the names and attributes of its components and type-bound 21procedures. 22A derived type may be parameterized by multiple type parameters, each of which is defined to be either 23a kind or length type parameter and may have a default value. 24The ultimate components of an object of derived type are the components that are of intrinsic type 25or have the POINTER or ALLOCATABLE attribute, plus the ultimate components of the components 26of the object that are of derived type and have neither the ALLOCATABLE nor POINTER attribute. NOTE 4.16 The ultimate components of objects of the derived type kids defined below are name, age, and other kids. type :: person character(len=20) :: name integer :: age end type person type :: kids type(person) :: oldest_child type(person), allocatable, dimension(:) :: other_kids end type kids 27By default, no storage sequence is implied by the order of the component definitions. However, a storage 28order is implied for a sequence type (4.5.1.2). If the derived type has the BIND attribute, the storage 29sequence is that required by the companion processor (2.5.10, 15.2.3). 44 MAY 2004 WORKING DRAFT J3/04-007 14.5.1 Derived-type definition 2R429 derived-type-def is derived-type-stmt 3 [ type-param-def-stmt ] ... 4 [ private-or-sequence ] ... 5 [ component-part ] 6 [ type-bound-procedure-part ] 7 end-type-stmt 8R430 derived-type-stmt is TYPE [ [ , type-attr-spec-list ] :: ] type-name 9 [ ( type-param-name-list ) ] 10R431 type-attr-spec is access-spec 11 or EXTENDS ( parent-type-name ) 12 or ABSTRACT 13 or BIND (C) 14C424 (R430) A derived type type-name shall not be DOUBLEPRECISION or the same as the name 15 of any intrinsic type defined in this standard. 16C425 (R430) The same type-attr-spec shall not appear more than once in a given derived-type-stmt. 17C426 (R431) A parent-type-name shall be the name of a previously defined extensible type (4.5.6). 18C427 (R429) If the type definition contains or inherits (4.5.6.1) a deferred binding (4.5.4), ABSTRACT 19 shall appear. 20C428 (R429) If ABSTRACT appears, the type shall be extensible. 21C429 (R429) If EXTENDS appears, SEQUENCE shall not appear. 22R432 private-or-sequence is private-components-stmt 23 or sequence-stmt 24C430 (R429) The same private-or-sequence shall not appear more than once in a given derived-type- 25 def . 26R433 end-type-stmt is END TYPE [ type-name ] 27C431 (R433) If END TYPE is followed by a type-name, the type-name shall be the same as that in 28 the corresponding derived-type-stmt. 29Derived types with the BIND attribute are subject to additional constraints as specified in 15.2.3. NOTE 4.17 An example of a derived-type definition is: TYPE PERSON INTEGER AGE CHARACTER (LEN = 50) NAME END TYPE PERSON An example of declaring a variable CHAIRMAN of type PERSON is: TYPE (PERSON) :: CHAIRMAN 45 J3/04-007 WORKING DRAFT MAY 2004 14.5.1.1 Accessibility 2Types that are defined in a module or accessible in that module by use association have either the 3PUBLIC or PRIVATE attribute. Types for which an access-spec is not explicitly specified in that 4module have the default accessibility attribute for that module. The default accessibility attribute for a 5module is PUBLIC unless it has been changed by a PRIVATE statement (5.2.1). Only types that have 6the PUBLIC attribute in that module are available to be accessed from that module by use association. 7The accessibility of a type does not affect, and is not affected by, the accessibility of its components and 8bindings. 9If a type definition is private, then the type name, and thus the structure constructor (4.5.9) for the 10type, are accessible only within the module containing the definition. NOTE 4.18 An example of a type with a private name is: TYPE, PRIVATE :: AUXILIARY LOGICAL :: DIAGNOSTIC CHARACTER (LEN = 20) :: MESSAGE END TYPE AUXILIARY Such a type would be accessible only within the module in which it is defined. 114.5.1.2 Sequence type 12R434 sequence-stmt is SEQUENCE 13C432 (R438) If SEQUENCE appears, each data component shall be declared to be of an intrinsic type 14 or of a sequence derived type. 15C433 (R429) If SEQUENCE appears, a type-bound-procedure-part shall not appear. 16If the SEQUENCE statement appears, the type is a sequence type. The order of the component 17definitions in a sequence type specifies a storage sequence for objects of that type. The type is a 18numeric sequence type if there are no type parameters, no pointer or allocatable components, and 19each component is of type default integer, default real, double precision real, default complex, default 20logical, or a numeric sequence type. The type is a character sequence type if there are no type 21parameters, no pointer or allocatable components, and each component is of type default character or a 22character sequence type. NOTE 4.19 An example of a numeric sequence type is: TYPE NUMERIC_SEQ SEQUENCE INTEGER :: INT_VAL REAL :: REAL_VAL LOGICAL :: LOG_VAL END TYPE NUMERIC_SEQ NOTE 4.20 A structure resolves into a sequence of components. Unless the structure includes a SEQUENCE statement, the use of this terminology in no way implies that these components are stored in 46 MAY 2004 WORKING DRAFT J3/04-007 NOTE 4.20 (cont.) this, or any other, order. Nor is there any requirement that contiguous storage be used. The sequence merely refers to the fact that in writing the definitions there will necessarily be an order in which the components appear, and this will define a sequence of components. This order is of limited significance because a component of an object of derived type will always be accessed by a component name except in the following contexts: the sequence of expressions in a derived-type value constructor, intrinsic assignment, the data values in namelist input data, and the inclusion of the structure in an input/output list of a formatted data transfer, where it is expanded to this sequence of components. Provided the processor adheres to the defined order in these cases, it is otherwise free to organize the storage of the components for any nonsequence structure in memory as best suited to the particular architecture. 14.5.1.3 Determination of derived types 2Derived-type definitions with the same type name may appear in different scoping units, in which case 3they may be independent and describe different derived types or they may describe the same type. 4Two data entities have the same type if they are declared with reference to the same derived-type 5definition. The definition may be accessed from a module or from a host scoping unit. Data entities in 6different scoping units also have the same type if they are declared with reference to different derived-type 7definitions that specify the same type name, all have the SEQUENCE property or all have the BIND 8attribute, have no components with PRIVATE accessibility, and have type parameters and components 9that agree in order, name, and attributes. Otherwise, they are of different derived types. A data entity 10declared using a type with the SEQUENCE property or with the BIND attribute is not of the same type 11as an entity of a type declared to be PRIVATE or that has any components that are PRIVATE. NOTE 4.21 An example of declaring two entities with reference to the same derived-type definition is: TYPE POINT REAL X, Y END TYPE POINT TYPE (POINT) :: X1 CALL SUB (X1) ... CONTAINS SUBROUTINE SUB (A) TYPE (POINT) :: A ... END SUBROUTINE SUB The definition of derived type POINT is known in subroutine SUB by host association. Because the declarations of X1 and A both reference the same derived-type definition, X1 and A have the same type. X1 and A also would have the same type if the derived-type definition were in a module and both SUB and its containing program unit accessed the module. NOTE 4.22 An example of data entities in different scoping units having the same type is: PROGRAM PGM TYPE EMPLOYEE SEQUENCE 47 J3/04-007 WORKING DRAFT MAY 2004 NOTE 4.22 (cont.) INTEGER ID_NUMBER CHARACTER (50) NAME END TYPE EMPLOYEE TYPE (EMPLOYEE) PROGRAMMER CALL SUB (PROGRAMMER) ... END PROGRAM PGM SUBROUTINE SUB (POSITION) TYPE EMPLOYEE SEQUENCE INTEGER ID_NUMBER CHARACTER (50) NAME END TYPE EMPLOYEE TYPE (EMPLOYEE) POSITION ... END SUBROUTINE SUB The actual argument PROGRAMMER and the dummy argument POSITION have the same type because they are declared with reference to a derived-type definition with the same name, the SEQUENCE property, and components that agree in order, name, and attributes. Suppose the component name ID NUMBER was ID NUM in the subroutine. Because all the component names are not identical to the component names in derived type EMPLOYEE in the main program, the actual argument PROGRAMMER would not be of the same type as the dummy argument POSITION. Thus, the program would not be standard conforming. NOTE 4.23 The requirement that the two types have the same name applies to the type-names of the respective derived-type-stmts, not to local names introduced via renaming in USE statements. 14.5.2 Derived-type parameters 2R435 type-param-def-stmt is INTEGER [ kind-selector ] , type-param-attr-spec :: 3 type-param-decl-list 4R436 type-param-decl is type-param-name [ = scalar-int-initialization-expr ] 5C434 (R435) A type-param-name in a type-param-def-stmt in a derived-type-def shall be one of the 6 type-param-names in the derived-type-stmt of that derived-type-def . 7C435 (R435) Each type-param-name in the derived-type-stmt in a derived-type-def shall appear as a 8 type-param-name in a type-param-def-stmt in that derived-type-def . 9R437 type-param-attr-spec is KIND 10 or LEN 11The derived type is parameterized if the derived-type-stmt has any type-param-names. 12Each type parameter is itself of type integer. If its kind selector is omitted, the kind type parameter is 13default integer. 14The type-param-attr-spec explicitly specifies whether a type parameter is a kind parameter or a length 15parameter. 48 MAY 2004 WORKING DRAFT J3/04-007 1If a type-param-decl has a scalar-int-initialization-expr, the type parameter has a default value which 2is specified by the expression. If necessary, the value is converted according to the rules of intrinsic 3assignment (7.4.1.3) to a value of the same kind as the type parameter. 4A type parameter may be used as a primary in a specification expression (7.1.6) in the derived-type- 5def . A kind type parameter may also be used as a primary in an initialization expression (7.1.7) in the 6derived-type-def . NOTE 4.24 The following example uses derived-type parameters. TYPE humongous_matrix(k, d) INTEGER, KIND :: k = kind(0.0) INTEGER(selected_int_kind(12)), LEN :: d !-- Specify a nondefault kind for d. REAL(k) :: element(d,d) END TYPE In the following example, dim is declared to be a kind parameter, allowing generic overloading of procedures distinguished only by dim. TYPE general_point(dim) INTEGER, KIND :: dim REAL :: coordinates(dim) END TYPE 74.5.2.1 Type parameter order 8Type parameter order is an ordering of the type parameters of a derived type; it is used for derived- 9type specifiers. 10The type parameter order of a nonextended type is the order of the type parameter list in the derived- 11type definition. The type parameter order of an extended type consists of the type parameter order of 12its parent type followed by any additional type parameters in the order of the type parameter list in the 13derived-type definition. NOTE 4.25 Given TYPE :: t1(k1,k2) INTEGER,KIND :: k1,k2 REAL(k1) a(k2) END TYPE TYPE,EXTENDS(t1) :: t2(k3) INTEGER,KIND :: k3 LOGICAL(k3) flag END TYPE the type parameter order for type T1 is K1 then K2, and the type parameter order for type T2 is K1 then K2 then K3. 144.5.3 Components 15R438 component-part is [ component-def-stmt ] ... 49 J3/04-007 WORKING DRAFT MAY 2004 1R439 component-def-stmt is data-component-def-stmt 2 or proc-component-def-stmt 3R440 data-component-def-stmt is declaration-type-spec [ [ , component-attr-spec-list ] :: ] 4 component-decl-list 5R441 component-attr-spec is POINTER 6 or DIMENSION ( component-array-spec ) 7 or ALLOCATABLE 8 or access-spec 9R442 component-decl is component-name [ ( component-array-spec ) ] 10 [ * char-length ] [ component-initialization ] 11R443 component-array-spec is explicit-shape-spec-list 12 or deferred-shape-spec-list 13R444 component-initialization is = initialization-expr 14 or => null-init 15C436 (R440) No component-attr-spec shall appear more than once in a given component-def-stmt. 16C437 (R440) A component declared with the CLASS keyword (5.1.1.2) shall have the ALLOCATABLE 17 or POINTER attribute. 18C438 (R440) If the POINTER attribute is not specified for a component, the declaration-type-spec 19 in the component-def-stmt shall be CLASS(*) or shall specify an intrinsic type or a previously 20 defined derived type. 21C439 (R440) If the POINTER attribute is specified for a component, the declaration-type-spec in the 22 component-def-stmt shall be CLASS(*) or shall specify an intrinsic type or any accessible derived 23 type including the type being defined. 24C440 (R440) If the POINTER or ALLOCATABLE attribute is specified, each component-array-spec 25 shall be a deferred-shape-spec-list. 26C441 (R440) If neither the POINTER attribute nor the ALLOCATABLE attribute is specified, each 27 component-array-spec shall be an explicit-shape-spec-list. 28C442 (R443) Each bound in the explicit-shape-spec shall either be an initialization expression or be a 29 specification expression that does not contain references to specification functions or any object 30 designators other than named constants or subobjects thereof. 31C443 (R440) A component shall not have both the ALLOCATABLE and the POINTER attribute. 32C444 (R442) The * char-length option is permitted only if the type specified is character. 33C445 (R439) Each type-param-value within a component-def-stmt shall either be a colon, be an ini- 34 tialization expression, or be a specification expression that contains neither references to speci- 35 fication functions nor any object designators other than named constants or subobjects thereof. NOTE 4.26 Because a type parameter is not an object, a type-param-value or a bound in an explicit-shape-spec may contain a type-param-name. 36C446 (R440) If component-initialization appears, a double-colon separator shall appear before the 37 component-decl-list. 38C447 (R440) If => appears in component-initialization, POINTER shall appear in the component- 39 attr-spec-list. If = appears in component-initialization, POINTER or ALLOCATABLE shall 40 not appear in the component-attr-spec-list. 50 MAY 2004 WORKING DRAFT J3/04-007 1R445 proc-component-def-stmt is PROCEDURE ( [ proc-interface ] ) , 2 proc-component-attr-spec-list :: proc-decl-list NOTE 4.27 See 12.3.2.3 for definitions of proc-interface and proc-decl. 3R446 proc-component-attr-spec is POINTER 4 or PASS [ (arg-name) ] 5 or NOPASS 6 or access-spec 7C448 (R445) The same proc-component-attr-spec shall not appear more than once in a given proc- 8 component-def-stmt. 9C449 (R445) POINTER shall appear in each proc-component-attr-spec-list. 10C450 (R445) If the procedure pointer component has an implicit interface or has no arguments, 11 NOPASS shall be specified. 12C451 (R445) If PASS (arg-name) appears, the interface shall have a dummy argument named arg- 13 name. 14C452 (R445) PASS and NOPASS shall not both appear in the same proc-component-attr-spec-list. 154.5.3.1 Array components 16A data component is an array if its component-decl contains a component-array-spec or its data-compo- 17nent-def-stmt contains the DIMENSION attribute. If the component-decl contains a component-array- 18spec, it specifies the array rank, and if the array is explicit shape (5.1.2.5.1), the array bounds; otherwise, 19the component-array-spec in the DIMENSION attribute specifies the array rank, and if the array is 20explicit shape, the array bounds. NOTE 4.28 An example of a derived type definition with an array component is: TYPE LINE REAL, DIMENSION (2, 2) :: COORD ! ! COORD(:,1) has the value of (/X1, Y1/) ! COORD(:,2) has the value of (/X2, Y2/) REAL :: WIDTH ! Line width in centimeters INTEGER :: PATTERN ! 1 for solid, 2 for dash, 3 for dot END TYPE LINE An example of declaring a variable LINE SEGMENT to be of the type LINE is: TYPE (LINE) :: LINE_SEGMENT The scalar variable LINE SEGMENT has a component that is an array. In this case, the array is a subobject of a scalar. The double colon in the definition for COORD is required; the double colon in the definition for WIDTH and PATTERN is optional. NOTE 4.29 An example of a derived type definition with an allocatable component is: 51 J3/04-007 WORKING DRAFT MAY 2004 NOTE 4.29 (cont.) TYPE STACK INTEGER :: INDEX INTEGER, ALLOCATABLE :: CONTENTS (:) END TYPE STACK For each scalar variable of type STACK, the shape of the component CONTENTS is determined by execution of an ALLOCATE statement or assignment statement, or by argument association. NOTE 4.30 Default initialization of an explicit-shape array component may be specified by an initialization expression consisting of an array constructor (4.7), or of a single scalar that becomes the value of each array element. 14.5.3.2 Pointer components 2A component is a pointer (2.4.6) if its component-attr-spec-list contains the POINTER attribute. A 3pointer component may be a data pointer or a procedure pointer. NOTE 4.31 An example of a derived type definition with a pointer component is: TYPE REFERENCE INTEGER :: VOLUME, YEAR, PAGE CHARACTER (LEN = 50) :: TITLE CHARACTER, DIMENSION (:), POINTER :: SYNOPSIS END TYPE REFERENCE Any object of type REFERENCE will have the four nonpointer components VOLUME, YEAR, PAGE, and TITLE, plus a pointer to an array of characters holding SYNOPSIS. The size of this target array will be determined by the length of the abstract. The space for the target may be allocated (6.3.1) or the pointer component may be associated with a target by a pointer assignment statement (7.4.2). 44.5.3.3 The passed-object dummy argument 5A passed-object dummy argument is a distinguished dummy argument of a procedure pointer 6component or type-bound procedure. It affects procedure overriding (4.5.6.2) and argument association 7(12.4.1.1). 8If NOPASS is specified, the procedure pointer component or type-bound procedure has no passed-object 9dummy argument. 10If neither PASS nor NOPASS is specified or PASS is specified without arg-name, the first dummy argu- 11ment of a procedure pointer component or type-bound procedure is its passed-object dummy argument. 12If PASS (arg-name) is specified, the dummy argument named arg-name is the passed-object dummy 13argument of the procedure pointer component or named type-bound procedure. 14C453 The passed-object dummy argument shall be a scalar, nonpointer, nonallocatable dummy data 15 object with the same declared type as the type being defined; all of its length type parameters 16 shall be assumed; it shall be polymorphic (5.1.1.2) if and only if the type being defined is 52 MAY 2004 WORKING DRAFT J3/04-007 1 extensible (4.5.6). NOTE 4.32 If a procedure is bound to several types as a type-bound procedure, different dummy arguments might be the passed-object dummy argument in different contexts. 24.5.3.4 Default initialization for components 3Default initialization provides a means of automatically initializing pointer components to be disasso- 4ciated, and nonpointer nonallocatable components to have a particular value. Allocatable components 5are always initialized to not allocated. 6If null-init appears for a pointer component, that component in any object of the type has an initial 7association status of disassociated (16.4.2.1) or becomes disassociated as specified in 16.4.2.1.2. 8If initialization-expr appears for a nonpointer component, that component in any object of the type 9is initially defined (16.5.3) or becomes defined as specified in 16.5.5 with the value determined from 10initialization-expr. If necessary, the value is converted according to the rules of intrinsic assignment 11(7.4.1.3) to a value that agrees in type, type parameters, and shape with the component. If the compo- 12nent is of a type for which default initialization is specified for a component, the default initialization 13specified by initialization-expr overrides the default initialization specified for that component. When 14one initialization overrides another it is as if only the overriding initialization were specified (see Note 154.34). Explicit initialization in a type declaration statement (5.1) overrides default initialization (see 16Note 4.33). Unlike explicit initialization, default initialization does not imply that the object has the 17SAVE attribute. 18A subcomponent (6.1.2) is default-initialized if the type of the object of which it is a component 19specifies default initialization for that component, and the subcomponent is not a subobject of an object 20that is default-initialized or explicitly initialized. NOTE 4.33 It is not required that initialization be specified for each component of a derived type. For example: TYPE DATE INTEGER DAY CHARACTER (LEN = 5) MONTH INTEGER :: YEAR = 1994 ! Partial default initialization END TYPE DATE In the following example, the default initial value for the YEAR component of TODAY is overridden by explicit initialization in the type declaration statement: TYPE (DATE), PARAMETER :: TODAY = DATE (21, "Feb.", 1995) NOTE 4.34 The default initial value of a component of derived type may be overridden by default initialization specified in the definition of the type. Continuing the example of Note 4.33: TYPE SINGLE_SCORE TYPE(DATE) :: PLAY_DAY = TODAY INTEGER SCORE TYPE(SINGLE_SCORE), POINTER :: NEXT => NULL ( ) 53 J3/04-007 WORKING DRAFT MAY 2004 NOTE 4.34 (cont.) END TYPE SINGLE_SCORE TYPE(SINGLE_SCORE) SETUP The PLAY DAY component of SETUP receives its initial value from TODAY, overriding the initialization for the YEAR component. NOTE 4.35 Arrays of structures may be declared with elements that are partially or totally initialized by default. Continuing the example of Note 4.34 : TYPE MEMBER (NAME_LEN) INTEGER, LEN :: NAME_LEN CHARACTER (LEN = NAME_LEN) NAME = '' INTEGER :: TEAM_NO, HANDICAP = 0 TYPE (SINGLE_SCORE), POINTER :: HISTORY => NULL ( ) END TYPE MEMBER TYPE (MEMBER(9)) LEAGUE (36) ! Array of partially initialized elements TYPE (MEMBER(9)) :: ORGANIZER = MEMBER ("I. Manage",1,5,NULL ( )) ORGANIZER is explicitly initialized, overriding the default initialization for an object of type MEMBER. Allocated objects may also be initialized partially or totally. For example: ALLOCATE (ORGANIZER % HISTORY) ! A partially initialized object of type ! SINGLE_SCORE is created. NOTE 4.36 A pointer component of a derived type may have as its target an object of that derived type. The type definition may specify that in objects declared to be of this type, such a pointer is default initialized to disassociated. For example: TYPE NODE INTEGER :: VALUE = 0 TYPE (NODE), POINTER :: NEXT_NODE => NULL ( ) END TYPE A type such as this may be used to construct linked lists of objects of type NODE. See C.1.5 for an example. 14.5.3.5 Component order 2Component order is an ordering of the nonparent components of a derived type; it is used for intrinsic 3formatted input/output and structure constructors (where component keywords are not used). Parent 4components are excluded from the component order of an extended type (4.5.6). 5The component order of a nonextended type is the order of the declarations of the components in the 6derived-type definition. The component order of an extended type consists of the component order of 7its parent type followed by any additional components in the order of their declarations in the extended 8derived-type definition. 54 MAY 2004 WORKING DRAFT J3/04-007 NOTE 4.37 Given the same type definitions as in Note 4.5.2.1, the component order of type T1 is just A (there is only one component), and the component order of type T2 is A then FLAG. The parent component (T1) does not participate in the component order. 14.5.3.6 Component accessibility 2R447 private-components-stmt is PRIVATE 3C454 (R447) A private-components-stmt is permitted only if the type definition is within the specifi- 4 cation part of a module. 5The default accessibility for the components that are declared in a type's component-part is private 6if the type definition contains a private-components-stmt, and public otherwise. The accessibility of a 7component may be explicitly declared by an access-spec; otherwise its accessibility is the default for the 8type definition in which it is declared. 9If a component is private, that component name is accessible only within the module containing the 10definition. NOTE 4.38 Type parameters are not components. They are effectively always public. NOTE 4.39 The accessibility of the components of a type is independent of the accessibility of the type name. It is possible to have all four combinations: a public type name with a public component, a private type name with a private component, a public type name with a private component, and a private type name with a public component. NOTE 4.40 An example of a type with private components is: MODULE DEFINITIONS TYPE POINT PRIVATE REAL :: X, Y END TYPE POINT END MODULE DEFINITIONS Such a type definition is accessible in any scoping unit accessing the module via a USE statement; however, the components X and Y are accessible only within the module. NOTE 4.41 The following example illustrates the use of an individual component access-spec to override the default accessibility: TYPE MIXED PRIVATE INTEGER :: I INTEGER, PUBLIC :: J END TYPE MIXED 55 J3/04-007 WORKING DRAFT MAY 2004 NOTE 4.41 (cont.) TYPE (MIXED) :: M The component M%J is accessible in any scoping unit where M is accessible; M%I is accessible only within the module containing the TYPE MIXED definition. 14.5.4 Type-bound procedures 2R448 type-bound-procedure-part is contains-stmt 3 [ binding-private-stmt ] 4 proc-binding-stmt 5 [ proc-binding-stmt ] ... 6R449 binding-private-stmt is PRIVATE 7C455 (R448) A binding-private-stmt is permitted only if the type definition is within the specification 8 part of a module. 9R450 proc-binding-stmt is specific-binding 10 or generic-binding 11 or final-binding 12R451 specific-binding is PROCEDURE [ (interface-name) ] 13 [ [ , binding-attr-list ] :: ] 14 binding-name [ => procedure-name ] 15C456 (R451) If => procedure-name appears, the double-colon separator shall appear. 16C457 (R451) If => procedure-name appears, interface-name shall not appear. 17C458 (R451) The procedure-name shall be the name of an accessible module procedure or an external 18 procedure that has an explicit interface. 19If neither => procedure-name nor interface-name appears, it is as though => procedure-name had 20appeared with a procedure name the same as the binding name. 21R452 generic-binding is GENERIC 22 [, access-spec ] :: generic-spec => binding-name-list 23C459 (R452) Within the specification-part of a module, each generic-binding shall specify, either 24 implicitly or explicitly, the same accessibility as every other generic-binding with that generic- 25 spec in the same derived type. 26C460 (R452) Each binding-name in binding-name-list shall be the name of a specific binding of the 27 type. 28C461 (R452) If generic-spec is not generic-name, each of its specific bindings shall have a passed-object 29 dummy argument (4.5.3.3). 30C462 (R452) If generic-spec is OPERATOR ( defined-operator ), the interface of each binding shall 31 be as specified in 12.3.2.1.1. 32C463 (R452) If generic-spec is ASSIGNMENT ( = ), the interface of each binding shall be as specified 33 in 12.3.2.1.2. 34C464 (R452) If generic-spec is dtio-generic-spec, the interface of each binding shall be as specified in 35 9.5.3.7. The type of the dtv argument shall be type-name. 56 MAY 2004 WORKING DRAFT J3/04-007 1R453 binding-attr is PASS [ (arg-name) ] 2 or NOPASS 3 or NON OVERRIDABLE 4 or DEFERRED 5 or access-spec 6C465 (R453) The same binding-attr shall not appear more than once in a given binding-attr-list. 7C466 (R451) If the interface of the binding has no dummy argument of the type being defined, 8 NOPASS shall appear. 9C467 (R451) If PASS (arg-name) appears, the interface of the binding shall have a dummy argument 10 named arg-name. 11C468 (R453) PASS and NOPASS shall not both appear in the same binding-attr-list. 12C469 (R453) NON OVERRIDABLE and DEFERRED shall not both appear in the same binding- 13 attr-list. 14C470 (R453) DEFERRED shall appear if and only if interface-name appears. 15C471 (R451) An overriding binding (4.5.6.2) shall have the DEFERRED attribute only if the binding 16 it overrides is deferred. 17C472 (R451) A binding shall not override an inherited binding (4.5.6.1) that has the NON OVER- 18 RIDABLE attribute. 19Each binding in a proc-binding-stmt specifies a type-bound procedure. A type-bound procedure 20may have a passed-object dummy argument (4.5.3.3). A generic-binding specifies a type-bound generic 21interface for its specific bindings. A binding that specifies the DEFERRED attribute is a deferred 22binding. A deferred binding shall appear only in the definition of an abstract type. 23A type-bound procedure may be identified by a binding name in the scope of the type definition. 24This name is the binding-name for a specific binding, and the generic-name for a generic binding whose 25generic-spec is generic-name. A final binding, or a generic binding whose generic-spec is not generic- 26name, has no binding name. 27The interface of a specific binding is that of the procedure specified by procedure-name or the interface 28specified by interface-name. NOTE 4.42 An example of a type and a type-bound procedure is: TYPE POINT REAL :: X, Y CONTAINS PROCEDURE, PASS :: LENGTH => POINT_LENGTH END TYPE POINT ... and in the module-subprogram-part of the same module: REAL FUNCTION POINT_LENGTH (A, B) CLASS (POINT), INTENT (IN) :: A, B POINT_LENGTH = SQRT ( (A%X - B%X)**2 + (A%Y - B%Y)**2 ) END FUNCTION POINT_LENGTH 57 J3/04-007 WORKING DRAFT MAY 2004 1The same generic-spec may be used in several generic-bindings within a single derived-type definition. 2Each additional generic-binding with the same generic-spec extends the generic interface. NOTE 4.43 Unlike the situation with generic procedure names, a generic type-bound procedure name is not permitted to be the same as a specific type-bound procedure name in the same type (16.2). 3The default accessibility for the procedure bindings of a type is private if the type definition contains a 4binding-private-stmt, and public otherwise. The accessibility of a procedure binding may be explicitly 5declared by an access-spec; otherwise its accessibility is the default for the type definition in which it is 6declared. 7A public type-bound procedure is accessible via any accessible object of the type. A private type-bound 8procedure is accessible only within the module containing the type definition. NOTE 4.44 The accessibility of a type-bound procedure is not affected by a PRIVATE statement in the component-part; the accessibility of a data component is not affected by a PRIVATE statement in the type-bound-procedure-part. 94.5.5 Final subroutines 10R454 final-binding is FINAL [ :: ] final-subroutine-name-list 11C473 (R454) A final-subroutine-name shall be the name of a module procedure with exactly one 12 dummy argument. That argument shall be nonoptional and shall be a nonpointer, nonallocat- 13 able, nonpolymorphic variable of the derived type being defined. All length type parameters of 14 the dummy argument shall be assumed. The dummy argument shall not be INTENT(OUT). 15C474 (R454) A final-subroutine-name shall not be one previously specified as a final subroutine for 16 that type. 17C475 (R454) A final subroutine shall not have a dummy argument with the same kind type parameters 18 and rank as the dummy argument of another final subroutine of that type. 19The FINAL keyword specifies a list of final subroutines. A final subroutine might be executed when 20a data entity of that type is finalized (4.5.5.1). 21A derived type is finalizable if it has any final subroutines or if it has any nonpointer, nonallocatable 22component whose type is finalizable. A nonpointer data entity is finalizable if its type is finalizable. NOTE 4.45 Final subroutines are effectively always "accessible". They are called for entity finalization re- gardless of the accessibility of the type, its other type-bound procedures, or the subroutine name itself. NOTE 4.46 Final subroutines are not inherited through type extension and cannot be overridden. The final subroutines of the parent type are called after any additional final subroutines of an extended type are called. 58 MAY 2004 WORKING DRAFT J3/04-007 14.5.5.1 The finalization process 2Only finalizable entities are finalized. When an entity is finalized, the following steps are carried out 3in sequence: 4 (1) If the dynamic type of the entity has a final subroutine whose dummy argument has the 5 same kind type parameters and rank as the entity being finalized, it is called with the entity 6 as an actual argument. Otherwise, if there is an elemental final subroutine whose dummy 7 argument has the same kind type parameters as the entity being finalized, it is called with 8 the entity as an actual argument. Otherwise, no subroutine is called at this point. 9 (2) Each finalizable component that appears in the type definition is finalized. If the entity 10 being finalized is an array, each finalizable component of each element of that entity is 11 finalized separately. 12 (3) If the entity is of extended type and the parent type is finalizable, the parent component is 13 finalized. 14If several entities are to be finalized as a consequence of an event specified in 4.5.5.2, the order in which 15they are finalized is processor-dependent. A final subroutine shall not reference or define an object that 16has already been finalized. 17If an object is not finalized, it retains its definition status and does not become undefined. 184.5.5.2 When finalization occurs 19When a pointer is deallocated its target is finalized. When an allocatable entity is deallocated, it is 20finalized. 21A nonpointer, nonallocatable object that is not a dummy argument or function result is finalized im- 22mediately before it would become undefined due to execution of a RETURN or END statement (16.5.6, 23item (3)). If the object is defined in a module and there are no longer any active procedures referencing 24the module, it is processor-dependent whether it is finalized. 25If an executable construct references a function, the result is finalized after execution of the innermost 26executable construct containing the reference. 27If an executable construct references a structure constructor, the entity created by the structure con- 28structor is finalized after execution of the innermost executable construct containing the reference. 29If a specification expression in a scoping unit references a function, the result is finalized before execution 30of the first executable statement in the scoping unit. 31When a procedure is invoked, a nonpointer, nonallocatable object that is an actual argument associated 32with an INTENT(OUT) dummy argument is finalized. 33When an intrinsic assignment statement is executed, variable is finalized after evaluation of expr and 34before the definition of variable. NOTE 4.47 If finalization is used for storage management, it often needs to be combined with defined assign- ment. 35If an object is allocated via pointer allocation and later becomes unreachable due to all pointers to that 36object having their pointer association status changed, it is processor dependent whether it is finalized. 37If it is finalized, it is processor dependent as to when the final subroutines are called. 59 J3/04-007 WORKING DRAFT MAY 2004 14.5.5.3 Entities that are not finalized 2If program execution is terminated, either by an error (e.g. an allocation failure) or by execution of 3a STOP or END PROGRAM statement, entities existing immediately prior to termination are not 4finalized. NOTE 4.48 A nonpointer, nonallocatable object that has the SAVE attribute or that occurs in the main pro- gram is never finalized as a direct consequence of the execution of a RETURN or END statement. A variable in a module is not finalized if it retains its definition status and value, even when there is no active procedure referencing the module. 54.5.6 Type extension 6A nonsequence derived type that does not have the BIND attribute is an extensible type. 7An extensible type that does not have the EXTENDS attribute is a base type. A type that has the 8EXTENDS attribute is an extended type. The parent type of an extended type is the type named 9in the EXTENDS attribute specification. NOTE 4.49 The name of the parent type might be a local name introduced via renaming in a USE statement. 10A base type is an extension type of itself only. An extended type is an extension of itself and of all 11types for which its parent type is an extension. 12An abstract type is a type that has the ABSTRACT attribute. NOTE 4.50 A deferred binding (4.5.4) defers the implementation of a type-bound procedure to extensions of the type; it may appear only in an abstract type. The dynamic type of an object cannot be abstract; therefore, a deferred binding cannot be invoked. An extension of an abstract type need not be abstract if it has no deferred bindings. A short example of an abstract type is: TYPE, ABSTRACT :: FILE_HANDLE CONTAINS PROCEDURE(OPEN_FILE), DEFERRED, PASS(HANDLE) :: OPEN ... END TYPE For a more elaborate example see C.1.4. 134.5.6.1 Inheritance 14An extended type includes all of the type parameters, all of the components, and the nonoverridden 15(4.5.6.2) nonfinal procedure bindings of its parent type. These are said to be inherited by the extended 16type from the parent type. They retain all of the attributes that they had in the parent type. Additional 17type parameters, components, and procedure bindings may be declared in the derived-type definition of 18the extended type. 60 MAY 2004 WORKING DRAFT J3/04-007 NOTE 4.51 Inaccessible components and bindings of the parent type are also inherited, but they remain inac- cessible in the extended type. Inaccessible entities occur if the type being extended is accessed via use association and has a private entity. NOTE 4.52 A base type is not required to have any components, bindings, or parameters; an extended type is not required to have more components, bindings, or parameters than its parent type. 1An extended type has a scalar, nonpointer, nonallocatable, parent component with the type and 2type parameters of the parent type. The name of this component is the parent type name. It has the 3accessibility of the parent type. Components of the parent component are inheritance associated 4(16.4.4) with the corresponding components inherited from the parent type. An ancestor component 5of a type is the parent component of the type or an ancestor component of the parent component. NOTE 4.53 A component or type parameter declared in an extended type shall not have the same name as any accessible component or type parameter of its parent type. NOTE 4.54 Examples: TYPE POINT ! A base type REAL :: X, Y END TYPE POINT TYPE, EXTENDS(POINT) :: COLOR_POINT ! An extension of TYPE(POINT) ! Components X and Y, and component name POINT, inherited from parent INTEGER :: COLOR END TYPE COLOR_POINT 64.5.6.2 Type-bound procedure overriding 7If a nongeneric binding specified in a type definition has the same binding name as a binding from the 8parent type then the binding specified in the type definition overrides the one from the parent type. 9The overriding binding and the overridden binding shall satisfy the following conditions: 10 (1) Either both shall have a passed-object dummy argument or neither shall. 11 (2) If the overridden binding is pure then the overriding binding shall also be pure. 12 (3) Either both shall be elemental or neither shall. 13 (4) They shall have the same number of dummy arguments. 14 (5) Passed-object dummy arguments, if any, shall correspond by name and position. 15 (6) Dummy arguments that correspond by position shall have the same names and characteris- 16 tics, except for the type of the passed-object dummy arguments. 17 (7) Either both shall be subroutines or both shall be functions having the same result charac- 18 teristics (12.2.2). 19 (8) If the overridden binding is PUBLIC then the overriding binding shall not be PRIVATE. 61 J3/04-007 WORKING DRAFT MAY 2004 NOTE 4.55 The following is an example of procedure overriding, expanding on the example in Note 4.42. TYPE, EXTENDS (POINT) :: POINT_3D REAL :: Z CONTAINS PROCEDURE, PASS :: LENGTH => POINT_3D_LENGTH END TYPE POINT_3D ... and in the module-subprogram-part of the same module: REAL FUNCTION POINT_3D_LENGTH ( A, B ) CLASS (POINT_3D), INTENT (IN) :: A CLASS (POINT), INTENT (IN) :: B SELECT TYPE(B) CLASS IS(POINT_3D) POINT_3D_LENGTH = SQRT( (A%X-B%X)**2 + (A%Y-B%Y)**2 + (A%Z-B%Z)**2 ) RETURN END SELECT PRINT *, 'In POINT_3D_LENGTH, dynamic type of argument is incorrect.' STOP END FUNCTION POINT_3D_LENGTH 1If a generic binding specified in a type definition has the same generic-spec as an inherited binding, it 2extends the generic interface and shall satisfy the requirements specified in 16.2.3. 3If a generic binding in a type definition has the same dtio-generic-spec as one inherited from the parent, it 4extends the type-bound generic interface for dtio-generic-spec and shall satisfy the requirements specified 5in 16.2.3. 6A binding of a type and a binding of an extension of that type are said to correspond if the latter binding 7is the same binding as the former, overrides a corresponding binding, or is an inherited corresponding 8binding. 94.5.7 Derived-type values 10The component value of 11 (1) a pointer component is its pointer association; 12 (2) an allocatable component is its allocation status and, if it is allocated, its dynamic type and 13 type parameters, bounds and value; 14 (3) a nonpointer nonallocatable component is its value. 15The set of values of a particular derived type consists of all possible sequences of the component values 16of its components. 174.5.8 Derived-type specifier 18A derived-type specifier is used in several contexts to specify a particular derived type and type param- 19eters. 62 MAY 2004 WORKING DRAFT J3/04-007 1R455 derived-type-spec is type-name [ ( type-param-spec-list ) ] 2R456 type-param-spec is [ keyword = ] type-param-value 3C476 (R455) type-name shall be the name of an accessible derived type. 4C477 (R455) type-param-spec-list shall appear only if the type is parameterized. 5C478 (R455) There shall be at most one type-param-spec corresponding to each parameter of the type. 6 If a type parameter does not have a default value, there shall be a type-param-spec corresponding 7 to that type parameter. 8C479 (R456) The keyword= may be omitted from a type-param-spec only if the keyword= has been 9 omitted from each preceding type-param-spec in the type-param-spec-list. 10C480 (R456) Each keyword shall be the name of a parameter of the type. 11C481 (R456) An asterisk may be used as a type-param-value in a type-param-spec only in the decla- 12 ration of a dummy argument or associate name or in the allocation of a dummy argument. 13Type parameter values that do not have type parameter keywords specified correspond to type param- 14eters in type parameter order (4.5.2.1). If a type parameter keyword is present, the value is assigned to 15the type parameter named by the keyword. If necessary, the value is converted according to the rules of 16intrinsic assignment (7.4.1.3) to a value of the same kind as the type parameter. 17The value of a type parameter for which no type-param-value has been specified is its default value. 184.5.9 Construction of derived-type values 19A derived-type definition implicitly defines a corresponding structure constructor that allows con- 20struction of values of that derived type. The type and type parameters of a constructed value are 21specified by a derived type specifier. 22R457 structure-constructor is derived-type-spec ( [ component-spec-list ] ) 23R458 component-spec is [ keyword = ] component-data-source 24R459 component-data-source is expr 25 or data-target 26 or proc-target 27C482 (R457) The derived-type-spec shall not specify an abstract type (4.5.6). 28C483 (R457) At most one component-spec shall be provided for a component. 29C484 (R457) If a component-spec is provided for a component, no component-spec shall be provided 30 for any component with which it is inheritance associated. 31C485 (R457) A component-spec shall be provided for a component unless it has default initialization 32 or is inheritance associated with another component for which a component-spec is provided or 33 that has default initialization. 34C486 (R458) The keyword= may be omitted from a component-spec only if the keyword= has been 35 omitted from each preceding component-spec in the constructor. 36C487 (R458) Each keyword shall be the name of a component of the type. 37C488 (R457) The type name and all components of the type for which a component-spec appears shall 38 be accessible in the scoping unit containing the structure constructor. 39C489 (R457) If derived-type-spec is a type name that is the same as a generic name, the component- 63 J3/04-007 WORKING DRAFT MAY 2004 1 spec-list shall not be a valid actual-arg-spec-list for a function reference that is resolvable as a 2 generic reference (12.4.4.1). 3C490 (R459) A data-target shall correspond to a nonprocedure pointer component; a proc-target shall 4 correspond to a procedure pointer component. 5C491 (R459) A data-target shall have the same rank as its corresponding component. NOTE 4.56 The form 'name(...)' is interpreted as a generic function-reference if possible; it is interpreted as a structure-constructor only if it cannot be interpreted as a generic function-reference. 6In the absence of a component keyword, each component-data-source is assigned to the corresponding 7component in component order (4.5.3.5). If a component keyword appears, the expr is assigned to the 8component named by the keyword. For a nonpointer component, the declared type and type parameters 9of the component and expr shall conform in the same way as for a variable and expr in an intrinsic 10assignment statement (7.4.1.2), as specified in Table 7.8. If necessary, each value of intrinsic type is 11converted according to the rules of intrinsic assignment (7.4.1.3) to a value that agrees in type and type 12parameters with the corresponding component of the derived type. For a nonpointer nonallocatable 13component, the shape of the expression shall conform with the shape of the component. 14If a component with default initialization has no corresponding component-data-source, then the default 15initialization is applied to that component. NOTE 4.57 Because no parent components appear in the defined component ordering, a value for a parent component may be specified only with a component keyword. Examples of equivalent values using types defined in Note 4.54: ! Create values with components x = 1.0, y = 2.0, color = 3. TYPE(POINT) :: PV = POINT(1.0, 2.0) ! Assume components of TYPE(POINT) ! are accessible here. ... COLOR_POINT( point=point(1,2), color=3) ! Value for parent component COLOR_POINT( point=PV, color=3) ! Available even if TYPE(point) ! has private components COLOR_POINT( 1, 2, 3) ! All components of TYPE(point) ! need to be accessible. 16A structure constructor shall not appear before the referenced type is defined. NOTE 4.58 This example illustrates a derived-type constant expression using a derived type defined in Note 4.17: PERSON (21, 'JOHN SMITH') This could also be written as PERSON (NAME = 'JOHN SMITH', AGE = 21) 64 MAY 2004 WORKING DRAFT J3/04-007 NOTE 4.59 An example constructor using the derived type GENERAL POINT defined in Note 4.24 is general_point(dim=3) ( (/ 1., 2., 3. /) ) 1For a pointer component, the corresponding component-data-source shall be an allowable data-target or 2proc-target for such a pointer in a pointer assignment statement (7.4.2). If the component data source is 3a pointer, the association of the component is that of the pointer; otherwise, the component is pointer 4associated with the component data source. NOTE 4.60 For example, if the variable TEXT were declared (5.1) to be CHARACTER, DIMENSION (1:400), TARGET :: TEXT and BIBLIO were declared using the derived-type definition REFERENCE in Note 4.31 TYPE (REFERENCE) :: BIBLIO the statement BIBLIO = REFERENCE (1, 1987, 1, "This is the title of the referenced & &paper", TEXT) is valid and associates the pointer component SYNOPSIS of the object BIBLIO with the target object TEXT. 5If a component of a derived type is allocatable, the corresponding constructor expression shall either be 6a reference to the intrinsic function NULL with no arguments, an allocatable entity of the same rank, 7or shall evaluate to an entity of the same rank. If the expression is a reference to the intrinsic function 8NULL, the corresponding component of the constructor has a status of unallocated. If the expression 9is an allocatable entity, the corresponding component of the constructor has the same allocation status 10as that allocatable entity and, if it is allocated, the same dynamic type, bounds, and value; if a length 11parameter of the component is deferred, its value is the same as the corresponding parameter of the 12expression. Otherwise the corresponding component of the constructor has an allocation status of 13allocated and has the same bounds and value as the expression. NOTE 4.61 When the constructor is an actual argument, the allocation status of the allocatable component is available through the associated dummy argument. 144.5.10 Derived-type operations and assignment 15Intrinsic assignment of derived-type entities is described in 7.4.1. This standard does not specify any 16intrinsic operations on derived-type entities. Any operation on derived-type entities or defined assign- 17ment (7.4.1.4) for derived-type entities shall be defined explicitly by a function or a subroutine, and a 18generic interface (4.5.1, 12.3.2.1). 65 J3/04-007 WORKING DRAFT MAY 2004 14.6 Enumerations and enumerators 2An enumeration is a set of enumerators. An enumerator is a named integer constant. An enumeration 3definition specifies the enumeration and its set of enumerators of the corresponding integer kind. 4R460 enum-def is enum-def-stmt 5 enumerator-def-stmt 6 [ enumerator-def-stmt ] ... 7 end-enum-stmt 8R461 enum-def-stmt is ENUM, BIND(C) 9R462 enumerator-def-stmt is ENUMERATOR [ :: ] enumerator-list 10R463 enumerator is named-constant [ = scalar-int-initialization-expr ] 11R464 end-enum-stmt is END ENUM 12C492 (R462) If = appears in an enumerator, a double-colon separator shall appear before the enu- 13 merator-list. 14For an enumeration, the kind is selected such that an integer type with that kind is interoperable (15.2.1) 15with the corresponding C enumeration type. The corresponding C enumeration type is the type that 16would be declared by a C enumeration specifier (6.7.2.2 of the C International Standard) that specified 17C enumeration constants with the same values as those specified by the enum-def , in the same order as 18specified by the enum-def . 19The companion processor (2.5.10) shall be one that uses the same representation for the types declared 20by all C enumeration specifiers that specify the same values in the same order. NOTE 4.62 If a companion processor uses an unsigned type to represent a given enumeration type, the Fortran processor will use the signed integer type of the same width for the enumeration, even though some of the values of the enumerators cannot be represented in this signed integer type. The values of any such enumerators will be interoperable with the values declared in the C enumeration. NOTE 4.63 The C International Standard guarantees the enumeration constants fit in a C int (6.7.2.2 of the C International Standard). Therefore, the Fortran processor can evaluate all enumerator values using the integer type with kind parameter C INT, and then determine the kind parameter of the integer type that is interoperable with the corresponding C enumerated type. NOTE 4.64 The C International Standard specifies that two enumeration types are compatible only if they specify enumeration constants with the same names and same values in the same order. This standard further requires that a C processor that is to be a companion processor of a Fortran processor use the same representation for two enumeration types if they both specify enumeration constants with the same values in the same order, even if the names are different. 21An enumerator is treated as if it were explicitly declared with the PARAMETER attribute. The enu- 22merator is defined in accordance with the rules of intrinsic assignment (7.4) with the value determined 23as follows: 24 (1) If scalar-int-initialization-expr is specified, the value of the enumerator is the result of 25 scalar-int-initialization-expr. 26 (2) If scalar-int-initialization-expr is not specified and the enumerator is the first enumerator 27 in enum-def , the enumerator has the value 0. 66 MAY 2004 WORKING DRAFT J3/04-007 1 (3) If scalar-int-initialization-expr is not specified and the enumerator is not the first enumer- 2 ator in enum-def , its value is the result of adding 1 to the value of the enumerator that 3 immediately precedes it in the enum-def . NOTE 4.65 Example of an enumeration definition: ENUM, BIND(C) ENUMERATOR :: RED = 4, BLUE = 9 ENUMERATOR YELLOW END ENUM The kind type parameter for this enumeration is processor dependent, but the processor is required to select a kind sufficient to represent the values 4, 9, and 10, which are the values of its enumerators. The following declaration might be equivalent to the above enumeration definition. INTEGER(SELECTED_INT_KIND(2)), PARAMETER :: RED = 4, BLUE = 9, YELLOW = 10 An entity of the same kind type parameter value can be declared using the intrinsic function KIND with one of the enumerators as its argument, for example INTEGER(KIND(RED)) :: X NOTE 4.66 There is no difference in the effect of declaring the enumerators in multiple ENUMERATOR statements or in a single ENUMERATOR statement. The order in which the enumerators in an enumeration definition are declared is significant, but the number of ENUMERATOR statements is not. 44.7 Construction of array values 5An array constructor is defined as a sequence of scalar values and is interpreted as a rank-one array 6where the element values are those specified in the sequence. 7R465 array-constructor is (/ ac-spec /) 8 or left-square-bracket ac-spec right-square-bracket 9R466 ac-spec is type-spec :: 10 or [type-spec ::] ac-value-list 11R467 left-square-bracket is [ 12R468 right-square-bracket is ] 13R469 ac-value is expr 14 or ac-implied-do 15R470 ac-implied-do is ( ac-value-list , ac-implied-do-control ) 16R471 ac-implied-do-control is ac-do-variable = scalar-int-expr , scalar-int-expr 17 [ , scalar-int-expr ] 18R472 ac-do-variable is scalar-int-variable 19C493 (R472) ac-do-variable shall be a named variable. 20C494 (R466) If type-spec is omitted, each ac-value expression in the array-constructor shall have the 21 same type and kind type parameters. 22C495 (R466) If type-spec specifies an intrinsic type, each ac-value expression in the array-constructor 67 J3/04-007 WORKING DRAFT MAY 2004 1 shall be of an intrinsic type that is in type conformance with a variable of type type-spec as 2 specified in Table 7.8. 3C496 (R466) If type-spec specifies a derived type, all ac-value expressions in the array-constructor 4 shall be of that derived type and shall have the same kind type parameter values as specified by 5 type-spec. 6C497 (R470) The ac-do-variable of an ac-implied-do that is in another ac-implied-do shall not appear 7 as the ac-do-variable of the containing ac-implied-do. 8If type-spec is omitted, each ac-value expression in the array constructor shall have the same length type 9parameters; in this case, the type and type parameters of the array constructor are those of the ac-value 10expressions. 11If type-spec appears, it specifies the type and type parameters of the array constructor. Each ac-value 12expression in the array-constructor shall be compatible with intrinsic assignment to a variable of this 13type and type parameters. Each value is converted to the type parameters of the array-constructor in 14accordance with the rules of intrinsic assignment (7.4.1.3). 15The character length of an ac-value in an ac-implied-do whose iteration count is zero shall not depend 16on the value of the ac-do-variable and shall not depend on the value of an expression that is not an 17initialization expression. 18If an ac-value is a scalar expression, its value specifies an element of the array constructor. If an ac- 19value is an array expression, the values of the elements of the expression, in array element order (6.2.2.2), 20specify the corresponding sequence of elements of the array constructor. If an ac-value is an ac-implied- 21do, it is expanded to form a sequence of elements under the control of the ac-do-variable, as in the DO 22construct (8.1.6.4). 23For an ac-implied-do, the loop initialization and execution is the same as for a DO construct. 24An empty sequence forms a zero-sized rank-one array. NOTE 4.67 A one-dimensional array may be reshaped into any allowable array shape using the RESHAPE intrinsic function (13.7.99). An example is: X = (/ 3.2, 4.01, 6.5 /) Y = RESHAPE (SOURCE = [ 2.0, [ 4.5, 4.5 ], X ], SHAPE = [ 3, 2 ]) This results in Y having the 3 × 2 array of values: 2.0 3.2 4.5 4.01 4.5 6.5 NOTE 4.68 Examples of array constructors containing an implied DO are: (/ (I, I = 1, 1075) /) and [ 3.6, (3.6 / I, I = 1, N) ] 68 MAY 2004 WORKING DRAFT J3/04-007 NOTE 4.69 Using the type definition for PERSON in Note 4.17, an example of the construction of a derived- type array value is: (/ PERSON (40, 'SMITH'), PERSON (20, 'JONES') /) NOTE 4.70 Using the type definition for LINE in Note 4.28, an example of the construction of a derived-type scalar value with a rank-2 array component is: LINE (RESHAPE ( (/ 0.0, 0.0, 1.0, 2.0 /), (/ 2, 2 /) ), 0.1, 1) The RESHAPE intrinsic function is used to construct a value that represents a solid line from (0, 0) to (1, 2) of width 0.1 centimeters. NOTE 4.71 Examples of zero-size array constructors are: (/ INTEGER :: /) (/ ( I, I = 1, 0) /) NOTE 4.72 An example of an array constructor that specifies a length type parameter: (/ CHARACTER(LEN=7) :: 'Takata', 'Tanaka', 'Hayashi' /) In this constructor, without the type specification, it would have been necessary to specify all of the constants with the same character length. 69 J3/04-007 WORKING DRAFT MAY 2004 70 MAY 2004 WORKING DRAFT J3/04-007 1Section 5: Data object declarations and specifications 2Every data object has a type and rank and may have type parameters and other attributes that determine 3the uses of the object. Collectively, these properties are the attributes of the object. The type of a 4named data object is either specified explicitly in a type declaration statement or determined implicitly 5by the first letter of its name (5.3). All of its attributes may be included in a type declaration statement 6or may be specified individually in separate specification statements. NOTE 5.1 For example: INTEGER :: INCOME, EXPENDITURE declares the two data objects named INCOME and EXPENDITURE to have the type integer. REAL, DIMENSION (-5:+5) :: X, Y, Z declares three data objects with names X, Y, and Z. These all have default real type and are explicit-shape rank-one arrays with a lower bound of -5, an upper bound of +5, and therefore a size of 11. 75.1 Type declaration statements 8R501 type-declaration-stmt is declaration-type-spec [ [ , attr-spec ] ... :: ] entity-decl-list 9R502 declaration-type-spec is intrinsic-type-spec 10 or TYPE ( derived-type-spec ) 11 or CLASS ( derived-type-spec ) 12 or CLASS ( * ) 13C501 (R502) In a declaration-type-spec, every type-param-value that is not a colon or an asterisk shall 14 be a specification-expr. 15C502 (R502) In a declaration-type-spec that uses the CLASS keyword, derived-type-spec shall specify 16 an extensible type. NOTE 5.2 A declaration-type-spec is used in a nonexecutable statement; a type-spec is used in an array constructor, a SELECT TYPE construct, or an ALLOCATE statement. 17C503 (R502) The TYPE(derived-type-spec) shall not specify an abstract type (4.5.6). 18R503 attr-spec is access-spec 19 or ALLOCATABLE 20 or ASYNCHRONOUS 21 or DIMENSION ( array-spec ) 22 or EXTERNAL 23 or INTENT ( intent-spec ) 24 or INTRINSIC 25 or language-binding-spec 71 J3/04-007 WORKING DRAFT MAY 2004 1 or OPTIONAL 2 or PARAMETER 3 or POINTER 4 or PROTECTED 5 or SAVE 6 or TARGET 7 or VALUE 8 or VOLATILE 9R504 entity-decl is object-name [( array-spec )] [ * char-length ] [ initialization ] 10 or function-name [ * char-length ] 11C504 (R504) If a type-param-value in a char-length in an entity-decl is not a colon or an asterisk, it 12 shall be a specification-expr. 13R505 object-name is name 14C505 (R505) The object-name shall be the name of a data object. 15R506 initialization is = initialization-expr 16 or => null-init 17R507 null-init is function-reference 18C506 (R507) The function-reference shall be a reference to the NULL intrinsic function with no 19 arguments. 20C507 (R501) The same attr-spec shall not appear more than once in a given type-declaration-stmt. 21C508 An entity shall not be explicitly given any attribute more than once in a scoping unit. 22C509 (R501) An entity declared with the CLASS keyword shall be a dummy argument or have the 23 ALLOCATABLE or POINTER attribute. 24C510 (R501) An array that has the POINTER or ALLOCATABLE attribute shall be specified with 25 an array-spec that is a deferred-shape-spec-list (5.1.2.5.3). 26C511 (R501) An array-spec for an object-name that is a function result that does not have the AL- 27 LOCATABLE or POINTER attribute shall be an explicit-shape-spec-list. 28C512 (R501) If the POINTER attribute is specified, the ALLOCATABLE, TARGET, EXTERNAL, 29 or INTRINSIC attribute shall not be specified. 30C513 (R501) If the TARGET attribute is specified, the POINTER, EXTERNAL, INTRINSIC, or 31 PARAMETER attribute shall not be specified. 32C514 (R501) The PARAMETER attribute shall not be specified for a dummy argument, a pointer, 33 an allocatable entity, a function, or an object in a common block. 34C515 (R501) The INTENT, VALUE, and OPTIONAL attributes may be specified only for dummy 35 arguments. 36C516 (R501) The INTENT attribute shall not be specified for a dummy procedure without the 37 POINTER attribute. 38C517 (R501) The SAVE attribute shall not be specified for an object that is in a common block, a 39 dummy argument, a procedure, a function result, an automatic data object, or an object with 72 MAY 2004 WORKING DRAFT J3/04-007 1 the PARAMETER attribute. 2C518 An entity shall not have both the EXTERNAL attribute and the INTRINSIC attribute. 3C519 (R501) An entity in an entity-decl-list shall not have the EXTERNAL or INTRINSIC attribute 4 specified unless it is a function. 5C520 (R504) The * char-length option is permitted only if the type specified is character. 6C521 (R504) The function-name shall be the name of an external function, an intrinsic function, a 7 function dummy procedure, or a statement function. 8C522 (R501) The initialization shall appear if the statement contains a PARAMETER attribute 9 (5.1.2.10). 10C523 (R501) If initialization appears, a double-colon separator shall appear before the entity-decl-list. 11C524 (R504)initialization shall not appear if object-name is a dummy argument, a function result, an 12 object in a named common block unless the type declaration is in a block data program unit, 13 an object in blank common, an allocatable variable, an external name, an intrinsic name, or an 14 automatic object. 15C525 (R504) If => appears in initialization, the object shall have the POINTER attribute. If = 16 appears in initialization, the object shall not have the POINTER attribute. 17C526 (R501) If the VOLATILE attribute is specified, the PARAMETER, INTRINSIC, EXTERNAL, 18 or INTENT(IN) attribute shall not be specified. 19C527 (R501) If the VALUE attribute is specified, the PARAMETER, EXTERNAL, POINTER, 20 ALLOCATABLE, DIMENSION, VOLATILE, INTENT(INOUT), or INTENT(OUT) attribute 21 shall not be specified. 22C528 (R501) If the VALUE attribute is specified, the length type parameter values shall be omitted 23 or specified by initialization expressions. 24C529 (R501) The VALUE attribute shall not be specified for a dummy procedure. 25C530 (R501) The ALLOCATABLE, POINTER, or OPTIONAL attribute shall not be specified for a 26 dummy argument of a procedure that has a proc-language-binding-spec. 27C531 (R503) A language-binding-spec shall appear only in the specification part of a module. 28C532 (R501) If a language-binding-spec is specified, the entity declared shall be an interoperable 29 variable (15.2). 30C533 (R501) If a language-binding-spec with a NAME= specifier appears, the entity-decl-list shall 31 consist of a single entity-decl. 32C534 (R503) The PROTECTED attribute is permitted only in the specification part of a module. 33C535 (R501) The PROTECTED attribute is permitted only for a procedure pointer or named variable 34 that is not in a common block. 35C536 (R501) If the PROTECTED attribute is specified, the EXTERNAL, INTRINSIC, or PARAM- 36 ETER attribute shall not be specified. 37C537 A nonpointer object that has the PROTECTED attribute and is accessed by use association 38 shall not appear in a variable definition context (16.5.7) or as the data-target or proc-target in 73 J3/04-007 WORKING DRAFT MAY 2004 1 a pointer-assignment-stmt. 2C538 A pointer object that has the PROTECTED attribute and is accessed by use association shall 3 not appear as 4 (1) A pointer-object in a nullify-stmt, 5 (2) A data-pointer-object or proc-pointer-object in a pointer-assignment-stmt, 6 (3) An allocate-object in an allocate-stmt or deallocate-stmt, or 7 (4) An actual argument in a reference to a procedure if the associated dummy argument is a 8 pointer with the INTENT(OUT) or INTENT(INOUT) attribute. 9A name that identifies a specific intrinsic function in a scoping unit has a type as specified in 13.6. An 10explicit type declaration statement is not required; however, it is permitted. Specifying a type for a 11generic intrinsic function name in a type declaration statement is not sufficient, by itself, to remove the 12generic properties from that function. 13A function result may be declared to have the POINTER or ALLOCATABLE attribute. 14A specification-expr in an array-spec, in a type-param-value in a declaration-type-spec corresponding to 15a length type parameter, or in a char-length in an entity-decl shall be an initialization expression unless 16it is in an interface body (12.3.2.1), the specification part of a subprogram, or the declaration-type-spec 17of a FUNCTION statement (12.5.2.1). If the data object being declared depends on the value of a 18specification-expr that is not an initialization expression, and it is not a dummy argument, such an 19object is called an automatic data object. NOTE 5.3 An automatic object shall neither appear in a SAVE or DATA statement nor be declared with a SAVE attribute nor be initially defined by an initialization. 20If a type parameter in a declaration-type-spec or in a char-length in an entity-decl is defined by an 21expression that is not an initialization expression, the type parameter value is established on entry to 22the procedure and is not affected by any redefinition or undefinition of the variables in the specification 23expression during execution of the procedure. 24If an entity-decl contains initialization and the object-name does not have the PARAMETER attribute, 25the entity is a variable with explicit initialization. Explicit initialization alternatively may be specified 26in a DATA statement unless the variable is of a derived type for which default initialization is specified. 27If initialization is =initialization-expr, the object-name is initially defined with the value specified by 28the initialization-expr; if necessary, the value is converted according to the rules of intrinsic assignment 29(7.4.1.3) to a value that agrees in type, type parameters, and shape with the object-name. A variable, 30or part of a variable, shall not be explicitly initialized more than once in a program. If the variable is an 31array, it shall have its shape specified in either the type declaration statement or a previous attribute 32specification statement in the same scoping unit. 33If initialization is =>null-init, object-name shall be a pointer, and its initial association status is disas- 34sociated. 35The presence of initialization implies that object-name is saved, except for an object-name in a named 36common block or an object-name with the PARAMETER attribute. The implied SAVE attribute may 37be reaffirmed by explicit use of the SAVE attribute in the type declaration statement, by inclusion of 38the object-name in a SAVE statement (5.2.12), or by the appearance of a SAVE statement without a 39saved-entity-list in the same scoping unit. 74 MAY 2004 WORKING DRAFT J3/04-007 NOTE 5.4 Examples of type declaration statements are: REAL A (10) LOGICAL, DIMENSION (5, 5) :: MASK1, MASK2 COMPLEX :: CUBE_ROOT = (-0.5, 0.866) INTEGER, PARAMETER :: SHORT = SELECTED_INT_KIND (4) INTEGER (SHORT) K ! Range at least -9999 to 9999. REAL (KIND (0.0D0)) A REAL (KIND = 2) B COMPLEX (KIND = KIND (0.0D0)) :: C CHARACTER (LEN = 10, KIND = 2) A CHARACTER B, C *20 TYPE (PERSON) :: CHAIRMAN TYPE(NODE), POINTER :: HEAD => NULL ( ) TYPE (humongous_matrix (k=8, d=1000)) :: mat (The last line above uses a type definition from Note 4.24.) 15.1.1 Declaration type specifiers 2The declaration-type-spec in a type declaration statement specifies the type of the entities in the entity 3declaration list. This explicit type declaration may override or confirm the implicit type that could 4otherwise be indicated by the first letter of an entity name (5.3). 5An intrinsic-type-spec in a type declaration statement is used to declare entities of intrinsic type. 65.1.1.1 TYPE 7A TYPE type specifier is used to declare entities of a derived type. 8Where a data entity is declared explicitly using the TYPE type specifier, the specified derived type shall 9have been defined previously in the scoping unit or be accessible there by use or host association. If 10the data entity is a function result, the derived type may be specified in the FUNCTION statement 11provided the derived type is defined within the body of the function or is accessible there by use or host 12association. If the derived type is specified in the FUNCTION statement and is defined within the body 13of the function, it is as if the function result variable was declared with that derived type immediately 14following the derived-type-def of the specified derived type. 15A scalar entity of derived type is a structure. If a derived type has the SEQUENCE property, a scalar 16entity of the type is a sequence structure. 175.1.1.2 CLASS 18A polymorphic entity is a data entity that is able to be of differing types during program execution. 19The type of a data entity at a particular point during execution of a program is its dynamic type. The 20declared type of a data entity is the type that it is declared to have, either explicitly or implicitly. 21A CLASS type specifier is used to declare polymorphic objects. The declared type of a polymorphic 22object is the specified type if the CLASS type specifier contains a type name. 23An object declared with the CLASS(*) specifier is an unlimited polymorphic object. An unlimited 24polymorphic entity is not declared to have a type. It is not considered to have the same declared type 25as any other entity, including another unlimited polymorphic entity. 75 J3/04-007 WORKING DRAFT MAY 2004 1A nonpolymorphic entity is type compatible only with entities of the same declared type. A poly- 2morphic entity that is not an unlimited polymorphic entity is type compatible with entities of the same 3declared type or any of its extensions. Even though an unlimited polymorphic entity is not considered 4to have a declared type, it is type compatible with all entities. An entity is said to be type compatible 5with a type if it is type compatible with entities of that type. 6Two entities are type incompatible if neither is type compatible with the other. 7An entity is type, kind, and rank compatible, or TKR compatible, with another entity if the first 8entity is type compatible with the second, the kind type parameters of the first entity have the same 9values as corresponding kind type parameters of the second, and both entities have the same rank. 10A polymorphic allocatable object may be allocated to be of any type with which it is type compatible. 11A polymorphic pointer or dummy argument may, during program execution, be associated with objects 12with which it is type compatible. 13The dynamic type of an allocated allocatable polymorphic object is the type with which it was allocated. 14The dynamic type of an associated polymorphic pointer is the dynamic type of its target. The dynamic 15type of a nonallocatable nonpointer polymorphic dummy argument is the dynamic type of its associated 16actual argument. The dynamic type of an unallocated allocatable or a disassociated pointer is the same 17as its declared type. The dynamic type of an entity identified by an associate name (8.1.4) is the dynamic 18type of the selector with which it is associated. The dynamic type of an object that is not polymorphic 19is its declared type. NOTE 5.5 Only components of the declared type of a polymorphic object may be designated by component selection (6.1.2). 205.1.2 Attributes 21The additional attributes that may appear in the attribute specification of a type declaration statement 22further specify the nature of the entities being declared or specify restrictions on their use in the program. 235.1.2.1 Accessibility attribute 24The accessibility attribute specifies the accessibility of an entity via a particular identifier. 25R508 access-spec is PUBLIC 26 or PRIVATE 27C539 (R508) An access-spec shall appear only in the specification-part of a module. 28Identifiers that are specified in a module or accessible in that module by use association have either 29the PUBLIC or PRIVATE attribute. Identifiers for which an access-spec is not explicitly specified in 30that module have the default accessibility attribute for that module. The default accessibility attribute 31for a module is PUBLIC unless it has been changed by a PRIVATE statement (5.2.1). Only identifiers 32that have the PUBLIC attribute in that module are available to be accessed from that module by use 33association. NOTE 5.6 In order for an identifier to be accessed by use association, it must have the PUBLIC attribute in the module from which it is accessed. It can nonetheless have the PRIVATE attribute in a module in which it is accessed by use association, and therefore not be available for use association from a module where it is PRIVATE. 76 MAY 2004 WORKING DRAFT J3/04-007 NOTE 5.7 An example of an accessibility specification is: REAL, PRIVATE :: X, Y, Z 15.1.2.2 ALLOCATABLE attribute 2An object with the ALLOCATABLE attribute is one for which space is allocated by an ALLOCATE 3statement (6.3.1) or by an intrinsic assignment statement (7.4.1.3). 45.1.2.3 ASYNCHRONOUS attribute 5The ASYNCHRONOUS attribute specifies that a variable may be subject to asynchronous in- 6put/output. 7The base object of a variable shall have the ASYNCHRONOUS attribute in a scoping unit if: 8 (1) the variable appears in an executable statement or specification expression in that scoping 9 unit and 10 (2) any statement of the scoping unit is executed while the variable is a pending I/O storage 11 sequence affector (9.5.1.4) 12The ASYNCHRONOUS attribute may be conferred implicitly by the use of a variable in an asynchronous 13input/output statement (9.5.1.4). 14An object may have the ASYNCHRONOUS attribute in a particular scoping unit without necessarily 15having it in other scoping units (11.2.1, 16.4.1.3). If an object has the ASYNCHRONOUS attribute, 16then all of its subobjects also have the ASYNCHRONOUS attribute. NOTE 5.8 The ASYNCHRONOUS attribute specifies the variables that might be associated with a pending input/output storage sequence (the actual memory locations on which asynchronous input/output is being performed) while the scoping unit is in execution. This information could be used by the compiler to disable certain code motion optimizations. The ASYNCHRONOUS attribute is similar to the VOLATILE attribute. It is intended to facilitate traditional code motion optimizations in the presence of asynchronous input/output. 175.1.2.4 BIND attribute for data entities 18The BIND attribute for a variable or common block specifies that it is capable of interoperating with a 19C variable that has external linkage (15.3). 20R509 language-binding-spec is BIND (C [, NAME = scalar-char-initialization-expr ]) 21C540 (R509) The scalar-char-initialization-expr shall be of default character kind. 22If the value of the scalar-char-initialization-expr after discarding leading and trailing blanks has nonzero 23length, it shall be valid as an identifier on the companion processor. NOTE 5.9 The C International Standard provides a facility for creating C identifiers whose characters are not restricted to the C basic character set. Such a C identifier is referred to as a universal character name (6.4.3 of the C International Standard). The name of such a C identifier may include characters that are not part of the representation method used by the processor for type default 77 J3/04-007 WORKING DRAFT MAY 2004 NOTE 5.9 (cont.) character. If so, the C entity cannot be referenced from Fortran. 1The BIND attribute implies the SAVE attribute, which may be confirmed by explicit specification. NOTE 5.10 Specifying the BIND attribute for an entity might have no discernable effect for a processor that is its own companion processor. 25.1.2.5 DIMENSION attribute 3The DIMENSION attribute specifies that an entity is an array. The rank or rank and shape is 4specified by the array-spec, if there is one, in the entity-decl, or by the array-spec in the DIMENSION 5attr-spec otherwise. To specify that an entity is an array in a type declaration statement, either the 6DIMENSION attr-spec shall appear, or an array-spec shall appear in the entity-decl. The appearance 7of an array-spec in an entity-decl specifies the DIMENSION attribute for the entity. The DIMENSION 8attribute alternatively may be specified in the specification statements DIMENSION, ALLOCATABLE, 9POINTER, TARGET, or COMMON. 10R510 array-spec is explicit-shape-spec-list 11 or assumed-shape-spec-list 12 or deferred-shape-spec-list 13 or assumed-size-spec 14C541 (R510)The maximum rank is seven. NOTE 5.11 Examples of DIMENSION attribute specifications are: SUBROUTINE EX (N, A, B) REAL, DIMENSION (N, 10) :: W ! Automatic explicit-shape array REAL A (:), B (0:) ! Assumed-shape arrays REAL, POINTER :: D (:, :) ! Array pointer REAL, DIMENSION (:), POINTER :: P ! Array pointer REAL, ALLOCATABLE, DIMENSION (:) :: E ! Allocatable array 155.1.2.5.1 Explicit-shape array 16An explicit-shape array is a named array that is declared with an explicit-shape-spec-list. This specifies 17explicit values for the bounds in each dimension of the array. 18R511 explicit-shape-spec is [ lower-bound : ] upper-bound 19R512 lower-bound is specification-expr 20R513 upper-bound is specification-expr 21C542 (R511) An explicit-shape array whose bounds are not initialization expressions shall be a dummy 22 argument, a function result, or an automatic array of a procedure. 23An automatic array is an explicit-shape array that is declared in a subprogram, is not a dummy 24argument, and has bounds that are not initialization expressions. 25If an explicit-shape array has bounds that are not initialization expressions, the bounds, and hence 26shape, are determined at entry to the procedure by evaluating the bounds expressions. The bounds of 78 MAY 2004 WORKING DRAFT J3/04-007 1such an array are unaffected by the redefinition or undefinition of any variable during execution of the 2procedure. 3The values of each lower-bound and upper-bound determine the bounds of the array along a particular 4dimension and hence the extent of the array in that dimension. The value of a lower bound or an upper 5bound may be positive, negative, or zero. The subscript range of the array in that dimension is the set 6of integer values between and including the lower and upper bounds, provided the upper bound is not 7less than the lower bound. If the upper bound is less than the lower bound, the range is empty, the 8extent in that dimension is zero, and the array is of zero size. If the lower-bound is omitted, the default 9value is 1. The number of sets of bounds specified is the rank. 105.1.2.5.2 Assumed-shape array 11An assumed-shape array is a nonpointer dummy argument array that takes its shape from the asso- 12ciated actual argument array. 13R514 assumed-shape-spec is [ lower-bound ] : 14The rank is equal to the number of colons in the assumed-shape-spec-list. 15The extent of a dimension of an assumed-shape array dummy argument is the extent of the corresponding 16dimension of the associated actual argument array. If the lower bound value is d and the extent of the 17corresponding dimension of the associated actual argument array is s, then the value of the upper bound 18is s + d - 1. The lower bound is lower-bound, if present, and 1 otherwise. 195.1.2.5.3 Deferred-shape array 20A deferred-shape array is an allocatable array or an array pointer. 21An allocatable array is an array that has the ALLOCATABLE attribute and a specified rank, but its 22bounds, and hence shape, are determined by allocation or argument association. 23An array with the ALLOCATABLE attribute shall be declared with a deferred-shape-spec-list. 24An array pointer is an array with the POINTER attribute and a specified rank. Its bounds, and hence 25shape, are determined when it is associated with a target. An array with the POINTER attribute shall 26be declared with a deferred-shape-spec-list. 27R515 deferred-shape-spec is : 28The rank is equal to the number of colons in the deferred-shape-spec-list. 29The size, bounds, and shape of an unallocated allocatable array or a disassociated array pointer are 30undefined. No part of such an array shall be referenced or defined; however, the array may appear as an 31argument to an intrinsic inquiry function as specified in 13.1. 32The bounds of each dimension of an allocatable array are those specified when the array is allocated. 33The bounds of each dimension of an array pointer may be specified in two ways: 34 (1) in an ALLOCATE statement (6.3.1) when the target is allocated, or 35 (2) by pointer assignment (7.4.2). 36The bounds of the array target or allocatable array are unaffected by any subsequent redefinition or 37undefinition of variables involved in the bounds' specification expressions. 79 J3/04-007 WORKING DRAFT MAY 2004 15.1.2.5.4 Assumed-size array 2An assumed-size array is a dummy argument array whose size is assumed from that of an associated 3actual argument. The rank and extents may differ for the actual and dummy arrays; only the size of the 4actual array is assumed by the dummy array. An assumed-size array is declared with an assumed-size- 5spec. 6R516 assumed-size-spec is [ explicit-shape-spec-list , ] [ lower-bound : ] * 7C543 An assumed-size-spec shall not appear except as the declaration of the array bounds of a dummy 8 data argument. 9C544 An assumed-size array with INTENT (OUT) shall not be of a type for which default initialization 10 is specified. 11The size of an assumed-size array is determined as follows: 12 (1) If the actual argument associated with the assumed-size dummy array is an array of any 13 type other than default character, the size is that of the actual array. 14 (2) If the actual argument associated with the assumed-size dummy array is an array element 15 of any type other than default character with a subscript order value of r (6.2.2.2) in an 16 array of size x, the size of the dummy array is x - r + 1. 17 (3) If the actual argument is a default character array, default character array element, or a 18 default character array element substring (6.1.1), and if it begins at character storage unit t 19 of an array with c character storage units, the size of the dummy array is MAX (INT ((c - 20 t + 1)/e), 0), where e is the length of an element in the dummy character array. 21 (4) If the actual argument is of type default character and is a scalar that is not an array element 22 or array element substring designator, the size of the dummy array is MAX (INT (l/e), 0), 23 where e is the length of an element in the dummy character array and l is the length of the 24 actual argument. 25The rank equals one plus the number of explicit-shape-specs. 26An assumed-size array has no upper bound in its last dimension and therefore has no extent in its last 27dimension and no shape. An assumed-size array name shall not be written as a whole array reference 28except as an actual argument in a procedure reference for which the shape is not required. 29The bounds of the first n - 1 dimensions are those specified by the explicit-shape-spec-list, if present, in 30the assumed-size-spec. The lower bound of the last dimension is lower-bound, if present, and 1 otherwise. 31An assumed-size array may be subscripted or sectioned (6.2.2.3). The upper bound shall not be omitted 32from a subscript triplet in the last dimension. 33If an assumed-size array has bounds that are not initialization expressions, the bounds are determined 34at entry to the procedure. The bounds of such an array are unaffected by the redefinition or undefinition 35of any variable during execution of the procedure. 365.1.2.6 EXTERNAL attribute 37The EXTERNAL attribute specifies that an entity is an external procedure, dummy procedure, 38procedure pointer, or block data subprogram. This attribute may also be specified by an EXTER- 39NAL statement (12.3.2.2), a procedure-declaration-stmt (12.3.2.3) or an interface body that is not in an 40abstract interface block (12.3.2.1). 41If an external procedure or dummy procedure is used as an actual argument or is the target of a procedure 42pointer assignment, it shall be declared to have the EXTERNAL attribute. 43A procedure that has both the EXTERNAL and POINTER attributes is a procedure pointer. 80 MAY 2004 WORKING DRAFT J3/04-007 15.1.2.7 INTENT attribute 2The INTENT attribute specifies the intended use of a dummy argument. 3R517 intent-spec is IN 4 or OUT 5 or INOUT 6C545 (R517) A nonpointer object with the INTENT (IN) attribute shall not appear in a variable 7 definition context (16.5.7). 8C546 (R517) A pointer object with the INTENT (IN) attribute shall not appear as 9 (1) A pointer-object in a nullify-stmt, 10 (2) A data-pointer-object or proc-pointer-object in a pointer-assignment-stmt, 11 (3) An allocate-object in an allocate-stmt or deallocate-stmt, or 12 (4) An actual argument in a reference to a procedure if the associated dummy argument is a 13 pointer with the INTENT (OUT) or INTENT (INOUT) attribute. 14The INTENT (IN) attribute for a nonpointer dummy argument specifies that it shall neither be de- 15fined nor become undefined during the execution of the procedure. The INTENT (IN) attribute for a 16pointer dummy argument specifies that during the execution of the procedure its association shall not 17be changed except that it may become undefined if the target is deallocated other than through the 18pointer (16.4.2.1.3). 19The INTENT (OUT) attribute for a nonpointer dummy argument specifies that it shall be defined 20before a reference to the dummy argument is made within the procedure and any actual argument that 21becomes associated with such a dummy argument shall be definable. On invocation of the procedure, 22such a dummy argument becomes undefined except for components of an object of derived type for 23which default initialization has been specified. The INTENT (OUT) attribute for a pointer dummy 24argument specifies that on invocation of the procedure the pointer association status of the dummy 25argument becomes undefined. Any actual argument associated with such a pointer dummy shall be a 26pointer variable. 27The INTENT (INOUT) attribute for a nonpointer dummy argument specifies that it is intended for use 28both to receive data from and to return data to the invoking scoping unit. Such a dummy argument may 29be referenced or defined. Any actual argument that becomes associated with such a dummy argument 30shall be definable. The INTENT (INOUT) attribute for a pointer dummy argument specifies that it is 31intended for use both to receive a pointer association from and to return a pointer association to the 32invoking scoping unit. Any actual argument associated with such a pointer dummy shall be a pointer 33variable. 34If no INTENT attribute is specified for a dummy argument, its use is subject to the limitations of the 35associated actual argument (12.4.1.2, 12.4.1.3, 12.4.1.4). NOTE 5.12 An example of INTENT specification is: SUBROUTINE MOVE (FROM, TO) USE PERSON_MODULE TYPE (PERSON), INTENT (IN) :: FROM TYPE (PERSON), INTENT (OUT) :: TO 36If an object has an INTENT attribute, then all of its subobjects have the same INTENT attribute. 81 J3/04-007 WORKING DRAFT MAY 2004 NOTE 5.13 If a dummy argument is a derived-type object with a pointer component, then the pointer as a pointer is a subobject of the dummy argument, but the target of the pointer is not. Therefore, the restrictions on subobjects of the dummy object apply to the pointer in contexts where it is used as a pointer, but not in contexts where it is dereferenced to indicate its target. For example, if X is a dummy argument of derived type with an integer pointer component P, and X has INTENT(IN), then the statement X%P => NEW_TARGET is prohibited, but X%P = 0 is allowed (provided that X%P is associated with a definable target). Similarly, the INTENT restrictions on pointer dummy arguments apply only to the association of the dummy argument; they do not restrict the operations allowed on its target. NOTE 5.14 Argument intent specifications serve several purposes in addition to documenting the intended use of dummy arguments. A processor can check whether an INTENT (IN) dummy argument is used in a way that could redefine it. A slightly more sophisticated processor could check to see whether an INTENT (OUT) dummy argument could possibly be referenced before it is defined. If the procedure's interface is explicit, the processor can also verify that actual arguments corresponding to INTENT (OUT) or INTENT (INOUT) dummy arguments are definable. A more sophisticated processor could use this information to optimize the translation of the referencing scoping unit by taking advantage of the fact that actual arguments corresponding to INTENT (IN) dummy arguments will not be changed and that any prior value of an actual argument corresponding to an INTENT (OUT) dummy argument will not be referenced and could thus be discarded. INTENT (OUT) means that the value of the argument after invoking the procedure is entirely the result of executing that procedure. If there is any possibility that an argument should retain its current value rather than being redefined, INTENT (INOUT) should be used rather than INTENT (OUT), even if there is no explicit reference to the value of the dummy argument. Because an INTENT(OUT) variable is considered undefined on entry to the procedure, any default initialization specified for its type will be applied. INTENT (INOUT) is not equivalent to omitting the INTENT attribute. The argument corre- sponding to an INTENT (INOUT) dummy argument always shall be definable, while an argument corresponding to a dummy argument without an INTENT attribute need be definable only if the dummy argument is actually redefined. 15.1.2.8 INTRINSIC attribute 2The INTRINSIC attribute confirms that a name is the specific name (13.6) or generic name (13.5) 3of an intrinsic procedure. The INTRINSIC attribute allows the specific name of an intrinsic procedure 4that is listed in 13.6 and not marked with a bullet (·) to be used as an actual argument (12.4). 5Declaring explicitly that a generic intrinsic procedure name has the INTRINSIC attribute does not cause 6that name to lose its generic property. 7If the specific name of an intrinsic procedure (13.6) is used as an actual argument, the name shall be 82 MAY 2004 WORKING DRAFT J3/04-007 1explicitly specified to have the INTRINSIC attribute. 2C547 (R503) (R1216) If the name of a generic intrinsic procedure is explicitly declared to have the 3 INTRINSIC attribute, and it is also the generic name in one or more generic interfaces (12.3.2.1) 4 accessible in the same scoping unit, the procedures in the interfaces and the specific intrinsic 5 procedures shall all be functions or all be subroutines, and the characteristics of the specific 6 intrinsic procedures and the procedures in the interfaces shall differ as specified in 16.2.3. 75.1.2.9 OPTIONAL attribute 8The OPTIONAL attribute specifies that the dummy argument need not be associated with an actual 9argument in a reference to the procedure (12.4.1.6). The PRESENT intrinsic function may be used 10to determine whether an actual argument has been associated with a dummy argument having the 11OPTIONAL attribute. 125.1.2.10 PARAMETER attribute 13The PARAMETER attribute specifies entities that are named constants. The object-name has the 14value specified by the initialization-expr that appears on the right of the equals; if necessary, the value 15is converted according to the rules of intrinsic assignment (7.4.1.3) to a value that agrees in type, type 16parameters, and shape with the object-name. 17A named constant shall not be referenced unless it has been defined previously in the same statement, 18defined in a prior statement, or made accessible by use or host association. NOTE 5.15 Examples of declarations with a PARAMETER attribute are: REAL, PARAMETER :: ONE = 1.0, Y = 4.1 / 3.0 INTEGER, DIMENSION (3), PARAMETER :: ORDER = (/ 1, 2, 3 /) TYPE(NODE), PARAMETER :: DEFAULT = NODE(0, NULL ( )) 195.1.2.11 POINTER attribute 20Entities with the POINTER attribute can be associated with different data objects or procedures 21during execution of a program. A pointer is either a data pointer or a procedure pointer. Procedure 22pointers are described in 12.3.2.3. 23A data pointer shall neither be referenced nor defined unless it is pointer associated with a target object 24that may be referenced or defined. 25If a data pointer is associated, the values of its deferred type parameters are the same as the values of 26the corresponding type parameters of its target. 27A procedure pointer shall not be referenced unless it is pointer associated with a target procedure. NOTE 5.16 Examples of POINTER attribute specifications are: TYPE (NODE), POINTER :: CURRENT, TAIL REAL, DIMENSION (:, :), POINTER :: IN, OUT, SWAP For a more elaborate example see C.2.1. 83 J3/04-007 WORKING DRAFT MAY 2004 15.1.2.12 PROTECTED attribute 2The PROTECTED attribute imposes limitations on the usage of module entities. 3Other than within the module in which an entity is given the PROTECTED attribute, 4 (1) if it is a nonpointer object, it is not definable, and 5 (2) if it is a pointer, its association status shall not be changed except that it may become 6 undefined if its target is deallocated other than through the pointer (16.4.2.1.3) or if its 7 target becomes undefined by execution of a RETURN or END statement. 8If an object has the PROTECTED attribute, all of its subobjects have the PROTECTED attribute. NOTE 5.17 An example of the PROTECTED attribute: MODULE temperature REAL, PROTECTED :: temp_c, temp_f CONTAINS SUBROUTINE set_temperature_c(c) REAL, INTENT(IN) :: c temp_c = c temp_f = temp_c*(9.0/5.0) + 32 END SUBROUTINE END MODULE The PROTECTED attribute ensures that the variables temp c and temp f cannot be modified other than via the set temperature c procedure, thus keeping them consistent with each other. 95.1.2.13 SAVE attribute 10An entity with the SAVE attribute, in the scoping unit of a subprogram, retains its association status, 11allocation status, definition status, and value after execution of a RETURN or END statement unless it 12is a pointer and its target becomes undefined (16.4.2.1.3(4)). It is shared by all instances (12.5.2.3) of 13the subprogram. 14An entity with the SAVE attribute, declared in the scoping unit of a module, retains its association 15status, allocation status, definition status, and value after a RETURN or END statement is executed in 16a procedure that accesses the module unless it is a pointer and its target becomes undefined. 17A saved entity is an entity that has the SAVE attribute. An unsaved entity is an entity that does not 18have the SAVE attribute. 19The SAVE attribute may appear in declarations in a main program and has no effect. 205.1.2.14 TARGET attribute 21An object with the TARGET attribute may have a pointer associated with it (7.4.2). An object 22without the TARGET attribute shall not have an accessible pointer associated with it. NOTE 5.18 In addition to variables explicitly declared to have the TARGET attribute, the objects created by allocation of pointers (6.3.1.2) have the TARGET attribute. 23If an object has the TARGET attribute, then all of its nonpointer subobjects also have the TARGET 84 MAY 2004 WORKING DRAFT J3/04-007 1attribute. NOTE 5.19 Examples of TARGET attribute specifications are: TYPE (NODE), TARGET :: HEAD REAL, DIMENSION (1000, 1000), TARGET :: A, B For a more elaborate example see C.2.2. NOTE 5.20 Every object designator that starts from a target object will have either the TARGET or POINTER attribute. If pointers are involved, the designator might not necessarily be a subobject of the original target object, but because pointers may point only to targets, there is no way to end up at a nonpointer that is not a target. 25.1.2.15 VALUE attribute 3The VALUE attribute specifies a type of argument association (12.4.1.2) for a dummy argument. 45.1.2.16 VOLATILE attribute 5The VOLATILE attribute specifies that an object may be referenced, defined, or become undefined, 6by means not specified by the program. 7An object may have the VOLATILE attribute in a particular scoping unit without necessarily having 8it in other scoping units (11.2.1, 16.4.1.3). If an object has the VOLATILE attribute, then all of its 9subobjects also have the VOLATILE attribute. NOTE 5.21 The Fortran processor should use the most recent definition of a volatile object when a value is required. Likewise, it should make the most recent Fortran definition available. It is the programmer's responsibility to manage the interactions with the non-Fortran processes. 10A pointer with the VOLATILE attribute may additionally have its association status and array bounds 11changed by means not specified by the program. NOTE 5.22 If the target of a pointer is referenced, defined, or becomes undefined, by means not specified by the program, while the pointer is associated with the target, then the pointer shall have the VOLATILE attribute. Usually a pointer should have the VOLATILE attribute if its target has the VOLATILE attribute. Similarly, all members of an EQUIVALENCE group should have the VOLATILE attribute if one member has the VOLATILE attribute. 12An allocatable object with the VOLATILE attribute may additionally have its allocation status, dynamic 13type and type parameters, and array bounds changed by means not specified by the program. 145.2 Attribute specification statements 15All attributes (other than type) may be specified for entities, independently of type, by separate at- 16tribute specification statements. The combination of attributes that may be specified for a particular 17entity is subject to the same restrictions as for type declaration statements regardless of the method of 85 J3/04-007 WORKING DRAFT MAY 2004 1specification. This also applies to PROCEDURE, EXTERNAL, and INTRINSIC statements. 25.2.1 Accessibility statements 3R518 access-stmt is access-spec [ [ :: ] access-id-list ] 4R519 access-id is use-name 5 or generic-spec 6C548 (R518) An access-stmt shall appear only in the specification-part of a module. Only one ac- 7 cessibility statement with an omitted access-id-list is permitted in the specification-part of a 8 module. 9C549 (R519) Each use-name shall be the name of a named variable, procedure, derived type, named 10 constant, or namelist group. 11An access-stmt with an access-id-list specifies the accessibility attribute (5.1.2.1), PUBLIC or PRIVATE, 12of each access-id in the list. An access-stmt without an access-id list specifies the default accessibility 13that applies to all potentially accessible identifiers in the specification-part of the module. The 14statement 15PUBLIC 16specifies a default of public accessibility. The statement 17PRIVATE 18specifies a default of private accessibility. If no such statement appears in a module, the default is public 19accessibility. NOTE 5.23 Examples of accessibility statements are: MODULE EX PRIVATE PUBLIC :: A, B, C, ASSIGNMENT (=), OPERATOR (+) 205.2.2 ALLOCATABLE statement 21R520 allocatable-stmt is ALLOCATABLE [ :: ] 22 object-name [ ( deferred-shape-spec-list ) ] 23 [ , object-name [ ( deferred-shape-spec-list ) ] ] ... 24This statement specifies the ALLOCATABLE attribute (5.1.2.2) for a list of objects. NOTE 5.24 An example of an ALLOCATABLE statement is: REAL A, B (:), SCALAR ALLOCATABLE :: A (:, :), B, SCALAR 255.2.3 ASYNCHRONOUS statement 26R521 asynchronous-stmt is ASYNCHRONOUS [ :: ] object-name-list 27The ASYNCHRONOUS statement specifies the ASYNCHRONOUS attribute (5.1.2.3) for a list of ob- 86 MAY 2004 WORKING DRAFT J3/04-007 1jects. 25.2.4 BIND statement 3R522 bind-stmt is language-binding-spec [ :: ] bind-entity-list 4R523 bind-entity is entity-name 5 or / common-block-name / 6C550 (R522) If any bind-entity in a bind-stmt is an entity-name, the bind-stmt shall appear in the 7 specification part of a module and the entity shall be an interoperable variable (15.2.4, 15.2.5). 8C551 (R522) If the language-binding-spec has a NAME= specifier, the bind-entity-list shall consist of 9 a single bind-entity. 10C552 (R522) If a bind-entity is a common block, each variable of the common block shall be interop- 11 erable (15.2.4, 15.2.5). 12The BIND statement specifies the BIND attribute (5.1.2.4) for a list of variables and common blocks. 135.2.5 DATA statement 14R524 data-stmt is DATA data-stmt-set [ [ , ] data-stmt-set ] ... 15This statement is used to specify explicit initialization (5.1). 16A variable, or part of a variable, shall not be explicitly initialized more than once in a program. If a 17nonpointer object has been specified with default initialization in a type definition, it shall not appear 18in a data-stmt-object-list. 19A variable that appears in a DATA statement and has not been typed previously may appear in a 20subsequent type declaration only if that declaration confirms the implicit typing. An array name, 21array section, or array element that appears in a DATA statement shall have had its array properties 22established by a previous specification statement. 23Except for variables in named common blocks, a named variable has the SAVE attribute if any part 24of it is initialized in a DATA statement, and this may be confirmed by a SAVE statement or a type 25declaration statement containing the SAVE attribute. 26R525 data-stmt-set is data-stmt-object-list / data-stmt-value-list / 27R526 data-stmt-object is variable 28 or data-implied-do 29R527 data-implied-do is ( data-i-do-object-list , data-i-do-variable = 30 scalar-int-expr , scalar-int-expr [ , scalar-int-expr ] ) 31R528 data-i-do-object is array-element 32 or scalar-structure-component 33 or data-implied-do 34R529 data-i-do-variable is scalar-int-variable 35C553 (R526) In a variable that is a data-stmt-object, any subscript, section subscript, substring start- 36 ing point, and substring ending point shall be an initialization expression. 37C554 (R526) A variable whose designator is included in a data-stmt-object-list or a data-i-do-object- 38 list shall not be: a dummy argument, made accessible by use association or host association, in 39 a named common block unless the DATA statement is in a block data program unit, in a blank 40 common block, a function name, a function result name, an automatic object, or an allocatable 87 J3/04-007 WORKING DRAFT MAY 2004 1 variable. 2C555 (R526) A data-i-do-object or a variable that appears as a data-stmt-object shall not be an object 3 designator in which a pointer appears other than as the entire rightmost part-ref . 4C556 (R529) The data-i-do-variable shall be a named variable. 5C557 (R527) A scalar-int-expr of a data-implied-do shall involve as primaries only constants, subob- 6 jects of constants, or DO variables of the containing data-implied-dos, and each operation shall 7 be intrinsic. 8C558 (R528) The array-element shall be a variable. 9C559 (R528) The scalar-structure-component shall be a variable. 10C560 (R528) The scalar-structure-component shall contain at least one part-ref that contains a sub- 11 script-list. 12C561 (R528) In an array-element or a scalar-structure-component that is a data-i-do-object, any sub- 13 script shall be an expression whose primaries are either constants, subobjects of constants, or 14 DO variables of this data-implied-do or the containing data-implied-dos, and each operation shall 15 be intrinsic. 16R530 data-stmt-value is [ data-stmt-repeat * ] data-stmt-constant 17R531 data-stmt-repeat is scalar-int-constant 18 or scalar-int-constant-subobject 19C562 (R531) The data-stmt-repeat shall be positive or zero. If the data-stmt-repeat is a named con- 20 stant, it shall have been declared previously in the scoping unit or made accessible by use 21 association or host association. 22R532 data-stmt-constant is scalar-constant 23 or scalar-constant-subobject 24 or signed-int-literal-constant 25 or signed-real-literal-constant 26 or null-init 27 or structure-constructor 28C563 (R532) If a DATA statement constant value is a named constant or a structure constructor, the 29 named constant or derived type shall have been declared previously in the scoping unit or made 30 accessible by use or host association. 31C564 (R532) If a data-stmt-constant is a structure-constructor, it shall be an initialization expression. 32R533 int-constant-subobject is constant-subobject 33C565 (R533) int-constant-subobject shall be of type integer. 34R534 constant-subobject is designator 35C566 (R534) constant-subobject shall be a subobject of a constant. 36C567 (R534) Any subscript, substring starting point, or substring ending point shall be an initializa- 37 tion expression. 38The data-stmt-object-list is expanded to form a sequence of pointers and scalar variables, referred to as 39"sequence of variables" in subsequent text. A nonpointer array whose unqualified name appears in a 40data-stmt-object-list is equivalent to a complete sequence of its array elements in array element order 88 MAY 2004 WORKING DRAFT J3/04-007 1(6.2.2.2). An array section is equivalent to the sequence of its array elements in array element order. A 2data-implied-do is expanded to form a sequence of array elements and structure components, under the 3control of the data-i-do-variable, as in the DO construct (8.1.6.4). 4The data-stmt-value-list is expanded to form a sequence of data-stmt-constants. A data-stmt-repeat 5indicates the number of times the following data-stmt-constant is to be included in the sequence; omission 6of a data-stmt-repeat has the effect of a repeat factor of 1. 7A zero-sized array or a data-implied-do with an iteration count of zero contributes no variables to the 8expanded sequence of variables, but a zero-length scalar character variable does contribute a variable 9to the expanded sequence. A data-stmt-constant with a repeat factor of zero contributes no data-stmt- 10constants to the expanded sequence of scalar data-stmt-constants. 11The expanded sequences of variables and data-stmt-constants are in one-to-one correspondence. Each 12data-stmt-constant specifies the initial value or null-init for the corresponding variable. The lengths of 13the two expanded sequences shall be the same. 14A data-stmt-constant shall be null-init if and only if the corresponding data-stmt-object has the POINT- 15ER attribute. The initial association status of a pointer data-stmt-object is disassociated. 16A data-stmt-constant other than null-init shall be compatible with its corresponding variable according 17to the rules of intrinsic assignment (7.4.1.2). The variable is initially defined with the value specified by 18the data-stmt-constant; if necessary, the value is converted according to the rules of intrinsic assignment 19(7.4.1.3) to a value that agrees in type, type parameters, and shape with the variable. 20If a data-stmt-constant is a boz-literal-constant, the corresponding variable shall be of type integer. The 21boz-literal-constant is treated as if it were an int-literal-constant with a kind-param that specifies the 22representation method with the largest decimal exponent range supported by the processor. NOTE 5.25 Examples of DATA statements are: CHARACTER (LEN = 10) NAME INTEGER, DIMENSION (0:9) :: MILES REAL, DIMENSION (100, 100) :: SKEW TYPE (NODE), POINTER :: HEAD_OF_LIST TYPE (PERSON) MYNAME, YOURNAME DATA NAME / 'JOHN DOE' /, MILES / 10 * 0 / DATA ((SKEW (K, J), J = 1, K), K = 1, 100) / 5050 * 0.0 / DATA ((SKEW (K, J), J = K + 1, 100), K = 1, 99) / 4950 * 1.0 / DATA HEAD_OF_LIST / NULL() / DATA MYNAME / PERSON (21, 'JOHN SMITH') / DATA YOURNAME % AGE, YOURNAME % NAME / 35, 'FRED BROWN' / The character variable NAME is initialized with the value JOHN DOE with padding on the right because the length of the constant is less than the length of the variable. All ten elements of the integer array MILES are initialized to zero. The two-dimensional array SKEW is initialized so that the lower triangle of SKEW is zero and the strict upper triangle is one. The structures MYNAME and YOURNAME are declared using the derived type PERSON from Note 4.17. The pointer HEAD OF LIST is declared using the derived type NODE from Note 4.36; it is initially disassociated. MYNAME is initialized by a structure constructor. YOURNAME is initialized by supplying a separate value for each component. 89 J3/04-007 WORKING DRAFT MAY 2004 15.2.6 DIMENSION statement 2R535 dimension-stmt is DIMENSION [ :: ] array-name ( array-spec ) 3 [ , array-name ( array-spec ) ] ... 4This statement specifies the DIMENSION attribute (5.1.2.5) and the array properties for each object 5named. NOTE 5.26 An example of a DIMENSION statement is: DIMENSION A (10), B (10, 70), C (:) 65.2.7 INTENT statement 7R536 intent-stmt is INTENT ( intent-spec ) [ :: ] dummy-arg-name-list 8This statement specifies the INTENT attribute (5.1.2.7) for the dummy arguments in the list. NOTE 5.27 An example of an INTENT statement is: SUBROUTINE EX (A, B) INTENT (INOUT) :: A, B 95.2.8 OPTIONAL statement 10R537 optional-stmt is OPTIONAL [ :: ] dummy-arg-name-list 11This statement specifies the OPTIONAL attribute (5.1.2.9) for the dummy arguments in the list. NOTE 5.28 An example of an OPTIONAL statement is: SUBROUTINE EX (A, B) OPTIONAL :: B 125.2.9 PARAMETER statement 13The PARAMETER statement specifies the PARAMETER attribute (5.1.2.10) and the values for 14the named constants in the list. 15R538 parameter-stmt is PARAMETER ( named-constant-def -list ) 16R539 named-constant-def is named-constant = initialization-expr 17The named constant shall have its type, type parameters, and shape specified in a prior specification of 18the specification-part or declared implicitly (5.3). If the named constant is typed by the implicit typing 19rules, its appearance in any subsequent specification of the specification-part shall confirm this implied 20type and the values of any implied type parameters. 21The value of each named constant is that specified by the corresponding initialization expression; if 22necessary, the value is converted according to the rules of intrinsic assignment (7.4.1.3) to a value that 23agrees in type, type parameters, and shape with the named constant. 90 MAY 2004 WORKING DRAFT J3/04-007 NOTE 5.29 An example of a PARAMETER statement is: PARAMETER (MODULUS = MOD (28, 3), NUMBER_OF_SENATORS = 100) 15.2.10 POINTER statement 2R540 pointer-stmt is POINTER [ :: ] pointer-decl-list 3R541 pointer-decl is object-name [ ( deferred-shape-spec-list ) ] 4 or proc-entity-name 5C568 (R541) A proc-entity-name shall also be declared in a procedure-declaration-stmt. 6This statement specifies the POINTER attribute (5.1.2.11) for a list of objects and procedure entities. NOTE 5.30 An example of a POINTER statement is: TYPE (NODE) :: CURRENT POINTER :: CURRENT, A (:, :) 75.2.11 PROTECTED statement 8R542 protected-stmt is PROTECTED [ :: ] entity-name-list 9The PROTECTED statement specifies the PROTECTED attribute (5.1.2.12) for a list of entities. 105.2.12 SAVE statement 11R543 save-stmt is SAVE [ [ :: ] saved-entity-list ] 12R544 saved-entity is object-name 13 or proc-pointer-name 14 or / common-block-name / 15R545 proc-pointer-name is name 16C569 (R545) A proc-pointer-name shall be the name of a procedure pointer. 17C570 (R543) If a SAVE statement with an omitted saved entity list occurs in a scoping unit, no other 18 explicit occurrence of the SAVE attribute or SAVE statement is permitted in the same scoping 19 unit. 20A SAVE statement with a saved entity list specifies the SAVE attribute (5.1.2.13) for all entities named 21in the list or included within a common block named in the list. A SAVE statement without a saved 22entity list is treated as though it contained the names of all allowed items in the same scoping unit. 23If a particular common block name is specified in a SAVE statement in any scoping unit of a program 24other than the main program, it shall be specified in a SAVE statement in every scoping unit in which 25that common block appears except in the scoping unit of the main program. For a common block 26declared in a SAVE statement, the values in the common block storage sequence (5.5.2.1) at the time a 27RETURN or END statement is executed are made available to the next scoping unit in the execution 28sequence of the program that specifies the common block name or accesses the common block. If a 29named common block is specified in the scoping unit of the main program, the current values of the 30common block storage sequence are made available to each scoping unit that specifies the named common 31block. The definition status of each object in the named common block storage sequence depends on 91 J3/04-007 WORKING DRAFT MAY 2004 1the association that has been established for the common block storage sequence. 2A SAVE statement may appear in the specification part of a main program and has no effect. NOTE 5.31 An example of a SAVE statement is: SAVE A, B, C, / BLOCKA /, D 35.2.13 TARGET statement 4R546 target-stmt is TARGET [ :: ] object-name [ ( array-spec ) ] 5 [ , object-name [ ( array-spec ) ] ] ... 6This statement specifies the TARGET attribute (5.1.2.14) for a list of objects. NOTE 5.32 An example of a TARGET statement is: TARGET :: A (1000, 1000), B 75.2.14 VALUE statement 8R547 value-stmt is VALUE [ :: ] dummy-arg-name-list 9The VALUE statement specifies the VALUE attribute (5.1.2.15) for a list of dummy arguments. 105.2.15 VOLATILE statement 11R548 volatile-stmt is VOLATILE [ :: ] object-name-list 12The VOLATILE statement specifies the VOLATILE attribute (5.1.2.16) for a list of objects. 135.3 IMPLICIT statement 14In a scoping unit, an IMPLICIT statement specifies a type, and possibly type parameters, for all 15implicitly typed data entities whose names begin with one of the letters specified in the statement. 16Alternatively, it may indicate that no implicit typing rules are to apply in a particular scoping unit. 17R549 implicit-stmt is IMPLICIT implicit-spec-list 18 or IMPLICIT NONE 19R550 implicit-spec is declaration-type-spec ( letter-spec-list ) 20R551 letter-spec is letter [ ­ letter ] 21C571 (R549) If IMPLICIT NONE is specified in a scoping unit, it shall precede any PARAMETER 22 statements that appear in the scoping unit and there shall be no other IMPLICIT statements 23 in the scoping unit. 24C572 (R551) If the minus and second letter appear, the second letter shall follow the first letter 25 alphabetically. 26A letter-spec consisting of two letters separated by a minus is equivalent to writing a list containing all 27of the letters in alphabetical order in the alphabetic sequence from the first letter through the second 28letter. For example, A­C is equivalent to A, B, C. The same letter shall not appear as a single letter, or 92 MAY 2004 WORKING DRAFT J3/04-007 1be included in a range of letters, more than once in all of the IMPLICIT statements in a scoping unit. 2In each scoping unit, there is a mapping, which may be null, between each of the letters A, B, ..., Z 3and a type (and type parameters). An IMPLICIT statement specifies the mapping for the letters in 4its letter-spec-list. IMPLICIT NONE specifies the null mapping for all the letters. If a mapping is not 5specified for a letter, the default for a program unit or an interface body is default integer if the letter 6is I, J, ..., or N and default real otherwise, and the default for an internal or module procedure is the 7mapping in the host scoping unit. 8Any data entity that is not explicitly declared by a type declaration statement, is not an intrinsic 9function, and is not made accessible by use association or host association is declared implicitly to be of 10the type (and type parameters) mapped from the first letter of its name, provided the mapping is not 11null. The mapping for the first letter of the data entity shall either have been established by a prior 12IMPLICIT statement or be the default mapping for the letter. The mapping may be to a derived type 13that is inaccessible in the local scope if the derived type is accessible to the host scope. The data entity 14is treated as if it were declared in an explicit type declaration in the outermost scoping unit in which it 15appears. An explicit type specification in a FUNCTION statement overrides an IMPLICIT statement 16for the name of the result variable of that function subprogram. NOTE 5.33 The following are examples of the use of IMPLICIT statements: MODULE EXAMPLE_MODULE IMPLICIT NONE ... INTERFACE FUNCTION FUN (I) ! Not all data entities need to INTEGER FUN ! be declared explicitly END FUNCTION FUN END INTERFACE CONTAINS FUNCTION JFUN (J) ! All data entities need to INTEGER JFUN, J ! be declared explicitly. ... END FUNCTION JFUN END MODULE EXAMPLE_MODULE SUBROUTINE SUB IMPLICIT COMPLEX (C) C = (3.0, 2.0) ! C is implicitly declared COMPLEX ... CONTAINS SUBROUTINE SUB1 IMPLICIT INTEGER (A, C) C = (0.0, 0.0) ! C is host associated and of ! type complex Z = 1.0 ! Z is implicitly declared REAL A = 2 ! A is implicitly declared INTEGER CC = 1 ! CC is implicitly declared INTEGER ... END SUBROUTINE SUB1 SUBROUTINE SUB2 Z = 2.0 ! Z is implicitly declared REAL and ! is different from the variable of ! the same name in SUB1 93 J3/04-007 WORKING DRAFT MAY 2004 NOTE 5.33 (cont.) ... END SUBROUTINE SUB2 SUBROUTINE SUB3 USE EXAMPLE_MODULE ! Accesses integer function FUN ! by use association Q = FUN (K) ! Q is implicitly declared REAL and ... ! K is implicitly declared INTEGER END SUBROUTINE SUB3 END SUBROUTINE SUB NOTE 5.34 An IMPLICIT statement may specify a declaration-type-spec of derived type. For example, given an IMPLICIT statement and a type defined as follows: IMPLICIT TYPE (POSN) (A-B, W-Z), INTEGER (C-V) TYPE POSN REAL X, Y INTEGER Z END TYPE POSN variables beginning with the letters A, B, W, X, Y, and Z are implicitly typed with the type POSN and the remaining variables are implicitly typed with type INTEGER. NOTE 5.35 The following is an example of a mapping to a derived type that is inaccessible in the local scope: PROGRAM MAIN IMPLICIT TYPE(BLOB) (A) TYPE BLOB INTEGER :: I END TYPE BLOB TYPE(BLOB) :: B CALL STEVE CONTAINS SUBROUTINE STEVE INTEGER :: BLOB .. AA = B .. END SUBROUTINE STEVE END PROGRAM MAIN In the subroutine STEVE, it is not possible to explicitly declare a variable to be of type BLOB because BLOB has been given a different meaning, but implicit mapping for the letter A still maps to type BLOB, so AA is of type BLOB. 94 MAY 2004 WORKING DRAFT J3/04-007 15.4 NAMELIST statement 2A NAMELIST statement specifies a group of named data objects, which may be referred to by a 3single name for the purpose of data transfer (9.5, 10.10). 4R552 namelist-stmt is NAMELIST 5 / namelist-group-name / namelist-group-object-list 6 [ [ , ] / namelist-group-name / 7 namelist-group-object-list ] ... 8C573 (R552) The namelist-group-name shall not be a name made accessible by use association. 9R553 namelist-group-object is variable-name 10C574 (R553) A namelist-group-object shall not be an assumed-size array. 11C575 (R552) A namelist-group-object shall not have the PRIVATE attribute if the namelist-group- 12 name has the PUBLIC attribute. 13The order in which the variables are specified in the NAMELIST statement determines the order in 14which the values appear on output. 15Any namelist-group-name may occur more than once in the NAMELIST statements in a scoping unit. 16The namelist-group-object-list following each successive appearance of the same namelist-group-name in 17a scoping unit is treated as a continuation of the list for that namelist-group-name. 18A namelist group object may be a member of more than one namelist group. 19A namelist group object shall either be accessed by use or host association or shall have its type, type 20parameters, and shape specified by previous specification statements or the procedure heading in the 21same scoping unit or by the implicit typing rules in effect for the scoping unit. If a namelist group object 22is typed by the implicit typing rules, its appearance in any subsequent type declaration statement shall 23confirm the implied type and type parameters. NOTE 5.36 An example of a NAMELIST statement is: NAMELIST /NLIST/ A, B, C 245.5 Storage association of data objects 25In general, the physical storage units or storage order for data objects is not specifiable. However, 26the EQUIVALENCE, COMMON, and SEQUENCE statements and the BIND(C) type-attr-spec provide 27for control of the order and layout of storage units. The general mechanism of storage association is 28described in 16.4.3. 295.5.1 EQUIVALENCE statement 30An EQUIVALENCE statement is used to specify the sharing of storage units by two or more objects 31in a scoping unit. This causes storage association of the objects that share the storage units. 32If the equivalenced objects have differing type or type parameters, the EQUIVALENCE statement does 33not cause type conversion or imply mathematical equivalence. If a scalar and an array are equivalenced, 34the scalar does not have array properties and the array does not have the properties of a scalar. 95 J3/04-007 WORKING DRAFT MAY 2004 1R554 equivalence-stmt is EQUIVALENCE equivalence-set-list 2R555 equivalence-set is ( equivalence-object , equivalence-object-list ) 3R556 equivalence-object is variable-name 4 or array-element 5 or substring 6C576 (R556) An equivalence-object shall not be a designator with a base object that is a dummy 7 argument, a pointer, an allocatable variable, a derived-type object that has an allocatable ulti- 8 mate component, an object of a nonsequence derived type, an object of a derived type that has 9 a pointer at any level of component selection, an automatic object, a function name, an entry 10 name, a result name, a variable with the BIND attribute, a variable in a common block that 11 has the BIND attribute, or a named constant. 12C577 (R556) An equivalence-object shall not be a designator that has more than one part-ref . 13C578 (R556) An equivalence-object shall not have the TARGET attribute. 14C579 (R556) Each subscript or substring range expression in an equivalence-object shall be an integer 15 initialization expression (7.1.7). 16C580 (R555) If an equivalence-object is of type default integer, default real, double precision real, 17 default complex, default logical, or numeric sequence type, all of the objects in the equivalence 18 set shall be of these types. 19C581 (R555) If an equivalence-object is of type default character or character sequence type, all of the 20 objects in the equivalence set shall be of these types. 21C582 (R555) If an equivalence-object is of a sequence derived type that is not a numeric sequence or 22 character sequence type, all of the objects in the equivalence set shall be of the same type with 23 the same type parameter values. 24C583 (R555) If an equivalence-object is of an intrinsic type other than default integer, default real, 25 double precision real, default complex, default logical, or default character, all of the objects in 26 the equivalence set shall be of the same type with the same kind type parameter value. 27C584 (R556) If an equivalence-object has the PROTECTED attribute, all of the objects in the equiv- 28 alence set shall have the PROTECTED attribute. 29C585 (R556) The name of an equivalence-object shall not be a name made accessible by use association. 30C586 (R556) A substring shall not have length zero. NOTE 5.37 The EQUIVALENCE statement allows the equivalencing of sequence structures and the equiv- alencing of objects of intrinsic type with nondefault type parameters, but there are strict rules regarding the appearance of these objects in an EQUIVALENCE statement. A structure that appears in an EQUIVALENCE statement shall be a sequence structure. If a sequence structure is not of numeric sequence type or of character sequence type, it shall be equivalenced only to objects of the same type with the same type parameter values. A structure of a numeric sequence type may be equivalenced to another structure of a numeric sequence type, an object of default integer type, default real type, double precision real type, default complex type, or default logical type such that components of the structure ultimately become associated only with objects of these types. A structure of a character sequence type may be equivalenced to an object of default character 96 MAY 2004 WORKING DRAFT J3/04-007 NOTE 5.37 (cont.) type or another structure of a character sequence type. An object of intrinsic type with nondefault kind type parameters may be equivalenced only to objects of the same type and kind type parameters. Further rules on the interaction of EQUIVALENCE statements and default initialization are given in 16.4.3.3. 15.5.1.1 Equivalence association 2An EQUIVALENCE statement specifies that the storage sequences (16.4.3.1) of the data objects specified 3in an equivalence-set are storage associated. All of the nonzero-sized sequences in the equivalence-set, if 4any, have the same first storage unit, and all of the zero-sized sequences in the equivalence-set, if any, 5are storage associated with one another and with the first storage unit of any nonzero-sized sequences. 6This causes the storage association of the data objects in the equivalence-set and may cause storage 7association of other data objects. 85.5.1.2 Equivalence of default character objects 9A data object of type default character may be equivalenced only with other objects of type default 10character. The lengths of the equivalenced objects need not be the same. 11An EQUIVALENCE statement specifies that the storage sequences of all the default character data 12objects specified in an equivalence-set are storage associated. All of the nonzero-sized sequences in the 13equivalence-set, if any, have the same first character storage unit, and all of the zero-sized sequences in 14the equivalence-set, if any, are storage associated with one another and with the first character storage 15unit of any nonzero-sized sequences. This causes the storage association of the data objects in the 16equivalence-set and may cause storage association of other data objects. NOTE 5.38 For example, using the declarations: CHARACTER (LEN = 4) :: A, B CHARACTER (LEN = 3) :: C (2) EQUIVALENCE (A, C (1)), (B, C (2)) the association of A, B, and C can be illustrated graphically as: 1 2 3 4 5 6 7 |--- --- A --- ---| |--- --- B --- ---| |--- C(1) ---| |--- C(2) ---| 175.5.1.3 Array names and array element designators 18For a nonzero-sized array, the use of the array name unqualified by a subscript list in an EQUIVALENCE 19statement has the same effect as using an array element designator that identifies the first element of 20the array. 97 J3/04-007 WORKING DRAFT MAY 2004 15.5.1.4 Restrictions on EQUIVALENCE statements 2An EQUIVALENCE statement shall not specify that the same storage unit is to occur more than once 3in a storage sequence. NOTE 5.39 For example: REAL, DIMENSION (2) :: A REAL :: B EQUIVALENCE (A (1), B), (A (2), B) ! Not standard conforming is prohibited, because it would specify the same storage unit for A (1) and A (2). 4An EQUIVALENCE statement shall not specify that consecutive storage units are to be nonconsecutive. 5 NOTE 5.40 For example, the following is prohibited: REAL A (2) DOUBLE PRECISION D (2) EQUIVALENCE (A (1), D (1)), (A (2), D (2)) ! Not standard conforming 65.5.2 COMMON statement 7The COMMON statement specifies blocks of physical storage, called common blocks, that may be 8accessed by any of the scoping units in a program. Thus, the COMMON statement provides a global 9data facility based on storage association (16.4.3). 10The common blocks specified by the COMMON statement may be named and are called named com- 11mon blocks, or may be unnamed and are called blank common. 12R557 common-stmt is COMMON 13 [ / [ common-block-name ] / ] common-block-object-list 14 [ [ , ] / [ common-block-name ] / 15 common-block-object-list ] ... 16R558 common-block-object is variable-name [ ( explicit-shape-spec-list ) ] 17 or proc-pointer-name 18C587 (R558) Only one appearance of a given variable-name or proc-pointer-name is permitted in all 19 common-block-object-lists within a scoping unit. 20C588 (R558) A common-block-object shall not be a dummy argument, an allocatable variable, a 21 derived-type object with an ultimate component that is allocatable, an automatic object, a 22 function name, an entry name, a variable with the BIND attribute, or a result name. 23C589 (R558) If a common-block-object is of a derived type, it shall be a sequence type (4.5.1) or a 24 type with the BIND attribute and it shall have no default initialization. 25C590 (R558) A variable-name or proc-pointer-name shall not be a name made accessible by use 26 association. 27In each COMMON statement, the data objects whose names appear in a common block object list 28following a common block name are declared to be in that common block. If the first common block 98 MAY 2004 WORKING DRAFT J3/04-007 1name is omitted, all data objects whose names appear in the first common block object list are specified to 2be in blank common. Alternatively, the appearance of two slashes with no common block name between 3them declares the data objects whose names appear in the common block object list that follows to be 4in blank common. 5Any common block name or an omitted common block name for blank common may occur more than 6once in one or more COMMON statements in a scoping unit. The common block list following each 7successive appearance of the same common block name in a scoping unit is treated as a continuation of 8the list for that common block name. Similarly, each blank common block object list in a scoping unit 9is treated as a continuation of blank common. 10The form variable-name (explicit-shape-spec-list) declares variable-name to have the DIMENSION at- 11tribute and specifies the array properties that apply. If derived-type objects of numeric sequence type 12(4.5.1) or character sequence type (4.5.1) appear in common, it is as if the individual components were 13enumerated directly in the common list. NOTE 5.41 Examples of COMMON statements are: COMMON /BLOCKA/ A, B, D (10, 30) COMMON I, J, K 145.5.2.1 Common block storage sequence 15For each common block in a scoping unit, a common block storage sequence is formed as follows: 16 (1) A storage sequence is formed consisting of the sequence of storage units in the storage 17 sequences (16.4.3.1) of all data objects in the common block object lists for the common 18 block. The order of the storage sequences is the same as the order of the appearance of the 19 common block object lists in the scoping unit. 20 (2) The storage sequence formed in (1) is extended to include all storage units of any storage 21 sequence associated with it by equivalence association. The sequence may be extended only 22 by adding storage units beyond the last storage unit. Data objects associated with an entity 23 in a common block are considered to be in that common block. 24Only COMMON statements and EQUIVALENCE statements appearing in the scoping unit contribute 25to common block storage sequences formed in that unit. 265.5.2.2 Size of a common block 27The size of a common block is the size of its common block storage sequence, including any extensions 28of the sequence resulting from equivalence association. 295.5.2.3 Common association 30Within a program, the common block storage sequences of all nonzero-sized common blocks with the 31same name have the same first storage unit, and the common block storage sequences of all zero-sized 32common blocks with the same name are storage associated with one another. Within a program, the 33common block storage sequences of all nonzero-sized blank common blocks have the same first storage 34unit and the storage sequences of all zero-sized blank common blocks are associated with one another and 35with the first storage unit of any nonzero-sized blank common blocks. This results in the association of 36objects in different scoping units. Use association or host association may cause these associated objects 37to be accessible in the same scoping unit. 38A nonpointer object of default integer type, default real type, double precision real type, default complex 99 J3/04-007 WORKING DRAFT MAY 2004 1type, default logical type, or numeric sequence type shall be associated only with nonpointer objects of 2these types. 3A nonpointer object of type default character or character sequence type shall be associated only with 4nonpointer objects of these types. 5A nonpointer object of a derived type that is not a numeric sequence or character sequence type shall 6be associated only with nonpointer objects of the same type with the same type parameter values. 7A nonpointer object of intrinsic type other than default integer, default real, double precision real, 8default complex, default logical, or default character shall be associated only with nonpointer objects of 9the same type and type parameters. 10A data pointer shall be storage associated only with data pointers of the same type and rank. Data 11pointers that are storage associated shall have deferred the same type parameters; corresponding non- 12deferred type parameters shall have the same value. A procedure pointer shall be storage associated 13only with another procedure pointer; either both interfaces shall be explicit or both interfaces shall be 14implicit. If the interfaces are explicit, the characteristics shall be the same. If the interfaces are implicit, 15either both shall be subroutines or both shall be functions with the same type and type parameters. 16An object with the TARGET attribute may be storage associated only with another object that has the 17TARGET attribute and the same type and type parameters. NOTE 5.42 A common block is permitted to contain sequences of different storage units, provided each scoping unit that accesses the common block specifies an identical sequence of storage units for the common block. For example, this allows a single common block to contain both numeric and character storage units. Association in different scoping units between objects of default type, objects of double precision real type, and sequence structures is permitted according to the rules for equivalence objects (5.5.1). 185.5.2.4 Differences between named common and blank common 19A blank common block has the same properties as a named common block, except for the following: 20 (1) Execution of a RETURN or END statement may cause data objects in a named common 21 block to become undefined unless the common block name has been declared in a SAVE 22 statement, but never causes data objects in blank common to become undefined (16.5.6). 23 (2) Named common blocks of the same name shall be of the same size in all scoping units of a 24 program in which they appear, but blank common blocks may be of different sizes. 25 (3) A data object in a named common block may be initially defined by means of a DATA 26 statement or type declaration statement in a block data program unit (11.3), but objects in 27 blank common shall not be initially defined. 285.5.2.5 Restrictions on common and equivalence 29An EQUIVALENCE statement shall not cause the storage sequences of two different common blocks to 30be associated. 31Equivalence association shall not cause a common block storage sequence to be extended by adding 32storage units preceding the first storage unit of the first object specified in a COMMON statement for 33the common block. 100 MAY 2004 WORKING DRAFT J3/04-007 NOTE 5.43 For example, the following is not permitted: COMMON /X/ A REAL B (2) EQUIVALENCE (A, B (2)) ! Not standard conforming 1Equivalence association shall not cause a derived-type object with default initialization to be associated 2with an object in a common block. 101 J3/04-007 WORKING DRAFT MAY 2004 102 MAY 2004 WORKING DRAFT J3/04-007 1Section 6: Use of data objects 2The appearance of a data object designator in a context that requires its value is termed a reference. A 3reference is permitted only if the data object is defined. A reference to a pointer is permitted only if the 4pointer is associated with a target object that is defined. A data object becomes defined with a value 5when events described in 16.5.5 occur. 6R601 variable is designator 7C601 (R601) designator shall not be a constant or a subobject of a constant. 8R602 variable-name is name 9C602 (R602) A variable-name shall be the name of a variable. 10R603 designator is object-name 11 or array-element 12 or array-section 13 or structure-component 14 or substring 15R604 logical-variable is variable 16C603 (R604) logical-variable shall be of type logical. 17R605 default-logical-variable is variable 18C604 (R605) default-logical-variable shall be of type default logical. 19R606 char-variable is variable 20C605 (R606) char-variable shall be of type character. 21R607 default-char-variable is variable 22C606 (R607) default-char-variable shall be of type default character. 23R608 int-variable is variable 24C607 (R608) int-variable shall be of type integer. NOTE 6.1 For example, given the declarations: CHARACTER (10) A, B (10) TYPE (PERSON) P ! See Note 4.17 then A, B, B (1), B (1:5), P % AGE, and A (1:1) are all variables. 25A constant (3.2.2) is a literal constant or a named constant. A literal constant is a scalar denoted by a 26syntactic form, which indicates its type, type parameters, and value. A named constant is a constant 27that has a name; the name has the PARAMETER attribute (5.1.2.10, 5.2.9). A reference to a constant 28is always permitted; redefinition of a constant is never permitted. 103 J3/04-007 WORKING DRAFT MAY 2004 16.1 Scalars 2A scalar (2.4.4) is a data entity that can be represented by a single value of the type and that is not an 3array (6.2). Its value, if defined, is a single element from the set of values that characterize its type. NOTE 6.2 A scalar object of derived type has a single value that consists of the values of its components (4.5.7). 4A scalar has rank zero. 56.1.1 Substrings 6A substring is a contiguous portion of a character string (4.4.4). The following rules define the forms 7of a substring: 8R609 substring is parent-string ( substring-range ) 9R610 parent-string is scalar-variable-name 10 or array-element 11 or scalar-structure-component 12 or scalar-constant 13R611 substring-range is [ scalar-int-expr ] : [ scalar-int-expr ] 14C608 (R610) parent-string shall be of type character. 15The value of the first scalar-int-expr in substring-range is called the starting point and the value of 16the second one is called the ending point. The length of a substring is the number of characters in the 17substring and is MAX (l - f + 1, 0), where f and l are the starting and ending points, respectively. 18Let the characters in the parent string be numbered 1, 2, 3, ..., n, where n is the length of the parent 19string. Then the characters in the substring are those from the parent string from the starting point and 20proceeding in sequence up to and including the ending point. Both the starting point and the ending 21point shall be within the range 1, 2, ..., n unless the starting point exceeds the ending point, in which 22case the substring has length zero. If the starting point is not specified, the default value is 1. If the 23ending point is not specified, the default value is n. 24If the parent is a variable, the substring is also a variable. NOTE 6.3 Examples of character substrings are: B(1)(1:5) array element as parent string P%NAME(1:1) structure component as parent string ID(4:9) scalar variable name as parent string '0123456789'(N:N) character constant as parent string 256.1.2 Structure components 26A structure component is part of an object of derived type; it may be referenced by an object 27designator. A structure component may be a scalar or an array. 104 MAY 2004 WORKING DRAFT J3/04-007 1R612 data-ref is part-ref [ % part-ref ] ... 2R613 part-ref is part-name [ ( section-subscript-list ) ] 3C609 (R612) Each part-name except the rightmost shall be of derived type. 4C610 (R612) Each part-name except the leftmost shall be the name of a component of the declared 5 type of the preceding part-name. 6C611 (R612) If the rightmost part-name is of abstract type, data-ref shall be polymorphic. 7C612 (R612) The leftmost part-name shall be the name of a data object. 8C613 (R613) If a section-subscript-list appears, the number of section-subscripts shall equal the rank 9 of part-name. 10The rank of a part-ref of the form part-name is the rank of part-name. The rank of a part-ref that has 11a section subscript list is the number of subscript triplets and vector subscripts in the list. 12C614 (R612) There shall not be more than one part-ref with nonzero rank. A part-name to the right 13 of a part-ref with nonzero rank shall not have the ALLOCATABLE or POINTER attribute. 14The rank of a data-ref is the rank of the part-ref with nonzero rank, if any; otherwise, the rank is zero. 15The base object of a data-ref is the data object whose name is the leftmost part name. 16The type and type parameters, if any, of a data-ref are those of the rightmost part name. 17A data-ref with more than one part-ref is a subobject of its base object if none of the part-names, 18except for possibly the rightmost, are pointers. If the rightmost part-name is the only pointer, then the 19data-ref is a subobject of its base object in contexts that pertain to its pointer association status but 20not in any other contexts. NOTE 6.4 If X is an object of derived type with a pointer component P, then the pointer X%P is a subobject of X when considered as a pointer ­ that is in contexts where it is not dereferenced. However the target of X%P is not a subobject of X. Thus, in contexts where X%P is dereferenced to refer to the target, it is not a subobject of X. 21R614 structure-component is data-ref 22C615 (R614) There shall be more than one part-ref and the rightmost part-ref shall be of the form 23 part-name. 24A structure component shall be neither referenced nor defined before the declaration of the base object. 25A structure component is a pointer only if the rightmost part name is defined to have the POINTER 26attribute. NOTE 6.5 Examples of structure components are: SCALAR_PARENT%SCALAR_FIELD scalar component of scalar parent ARRAY_PARENT(J)%SCALAR_FIELD component of array element parent ARRAY_PARENT(1:N)%SCALAR_FIELD component of array section parent For a more elaborate example see C.3.1. 105 J3/04-007 WORKING DRAFT MAY 2004 NOTE 6.6 The syntax rules are structured such that a data-ref that ends in a component name without a following subscript list is a structure component, even when other component names in the data- ref are followed by a subscript list. A data-ref that ends in a component name with a following subscript list is either an array element or an array section. A data-ref of nonzero rank that ends with a substring-range is an array section. A data-ref of zero rank that ends with a substring-range is a substring. 1A subcomponent of an object of derived type is a component of that object or of a subobject of that 2object. 36.1.3 Type parameter inquiry 4A type parameter inquiry is used to inquire about a type parameter of a data object. It applies to 5both intrinsic and derived types. 6R615 type-param-inquiry is designator % type-param-name 7C616 (R615) The type-param-name shall be the name of a type parameter of the declared type of the 8 object designated by the designator. 9A deferred type parameter of a pointer that is not associated or of an unallocated allocatable variable 10shall not be inquired about. NOTE 6.7 A type-param-inquiry has a syntax like that of a structure component reference, but it does not have the same semantics. It is not a variable and thus can never be assigned to. It may be used only as a primary in an expression. It is scalar even if designator is an array. The intrinsic type parameters can also be inquired about by using the intrinsic functions KIND and LEN. NOTE 6.8 The following are examples of type parameter inquiries: a%kind !-- A is real. Same value as KIND(a). s%len !-- S is character. Same value as LEN(s). b(10)%kind !-- Inquiry about an array element. p%dim !-- P is of the derived type general_point. See Note 4.24 for the definition of the general point type used in the last example above. 116.2 Arrays 12An array is a set of scalar data, all of the same type and type parameters, whose individual elements 13are arranged in a rectangular pattern. The scalar data that make up an array are the array elements. 14No order of reference to the elements of an array is indicated by the appearance of the array designator, 15except where array element ordering (6.2.2.2) is specified. 106 MAY 2004 WORKING DRAFT J3/04-007 16.2.1 Whole arrays 2A whole array is a named array, which may be either a named constant (5.1.2.10, 5.2.9) or a variable; 3no subscript list is appended to the name. 4The appearance of a whole array variable in an executable construct specifies all the elements of the 5array (2.4.5). An assumed-size array is permitted to appear as a whole array in an executable construct 6only as an actual argument in a procedure reference that does not require the shape. 7The appearance of a whole array name in a nonexecutable statement specifies the entire array except 8for the appearance of a whole array name in an equivalence set (5.5.1.3). 96.2.2 Array elements and array sections 10R616 array-element is data-ref 11C617 (R616) Every part-ref shall have rank zero and the last part-ref shall contain a subscript-list. 12R617 array-section is data-ref [ ( substring-range ) ] 13C618 (R617) Exactly one part-ref shall have nonzero rank, and either the final part-ref shall have a 14 section-subscript-list with nonzero rank or another part-ref shall have nonzero rank. 15C619 (R617) If a substring-range appears, the rightmost part-name shall be of type character. 16R618 subscript is scalar-int-expr 17R619 section-subscript is subscript 18 or subscript-triplet 19 or vector-subscript 20R620 subscript-triplet is [ subscript ] : [ subscript ] [ : stride ] 21R621 stride is scalar-int-expr 22R622 vector-subscript is int-expr 23C620 (R622) A vector-subscript shall be an integer array expression of rank one. 24C621 (R620) The second subscript shall not be omitted from a subscript-triplet in the last dimension 25 of an assumed-size array. 26An array element is a scalar. An array section is an array. If a substring-range is present in an array- 27section, each element is the designated substring of the corresponding element of the array section. NOTE 6.9 For example, with the declarations: REAL A (10, 10) CHARACTER (LEN = 10) B (5, 5, 5) A (1, 2) is an array element, A (1:N:2, M) is a rank-one array section, and B (:, :, :) (2:3) is an array of shape (5, 5, 5) whose elements are substrings of length 2 of the corresponding elements of B. NOTE 6.10 Unless otherwise specified, an array element or array section does not have an attribute of the whole array. In particular, an array element or an array section does not have the POINTER or ALLOCATABLE attribute. 107 J3/04-007 WORKING DRAFT MAY 2004 NOTE 6.11 Examples of array elements and array sections are: ARRAY_A(1:N:2)%ARRAY_B(I, J)%STRING(K)(:) array section SCALAR_PARENT%ARRAY_FIELD(J) array element SCALAR_PARENT%ARRAY_FIELD(1:N) array section SCALAR_PARENT%ARRAY_FIELD(1:N)%SCALAR_FIELD array section 16.2.2.1 Array elements 2The value of a subscript in an array element shall be within the bounds for that dimension. 36.2.2.2 Array element order 4The elements of an array form a sequence known as the array element order. The position of an array 5element in this sequence is determined by the subscript order value of the subscript list designating the 6element. The subscript order value is computed from the formulas in Table 6.1. Table 6.1: Subscript order value Rank Subscript bounds Subscript list Subscript order value 1 j1:k1 s1 1 + (s1 - j1) 1 + (s1 - j1) 2 j1:k1,j2:k2 s1, s2 + (s2 - j2) × d1 1 + (s1 - j1) 3 j1:k1, j2:k2, j3:k3 s1, s2, s3 + (s2 - j2) × d1 + (s3 - j3) × d2 × d1 · · · · · · · · · · · · 1 + (s1 - j1) + (s2 - j2) × d1 + (s3 - j3) × d2 × d1 7 j1:k1, . . . , j7:k7 s1, . . . , s7 + ... + (s7 - j7) × d6 × d5 × ... × d1 Notes for Table 6.1: 1) di = max (ki -ji +1, 0) is the size of the ith dimension. 2) If the size of the array is nonzero, ji si ki for all i = 1, 2, ..., 7. 76.2.2.3 Array sections 8An array section is an array subobject optionally followed by a substring range. 9In an array-section having a section-subscript-list, each subscript-triplet and vector-subscript in the 10section subscript list indicates a sequence of subscripts, which may be empty. Each subscript in such a 11sequence shall be within the bounds for its dimension unless the sequence is empty. The array section is 12the set of elements from the array determined by all possible subscript lists obtainable from the single 13subscripts or sequences of subscripts specified by each section subscript. 14In an array-section with no section-subscript-list, the rank and shape of the array is the rank and shape 15of the part-ref with nonzero rank; otherwise, the rank of the array section is the number of subscript 16triplets and vector subscripts in the section subscript list. The shape is the rank-one array whose ith 108 MAY 2004 WORKING DRAFT J3/04-007 1element is the number of integer values in the sequence indicated by the ith subscript triplet or vector 2subscript. If any of these sequences is empty, the array section has size zero. The subscript order of the 3elements of an array section is that of the array data object that the array section represents. 46.2.2.3.1 Subscript triplet 5A subscript triplet designates a regular sequence of subscripts consisting of zero or more subscript values. 6The third expression in the subscript triplet is the increment between the subscript values and is called 7the stride. The subscripts and stride of a subscript triplet are optional. An omitted first subscript in a 8subscript triplet is equivalent to a subscript whose value is the lower bound for the array and an omitted 9second subscript is equivalent to the upper bound. An omitted stride is equivalent to a stride of 1. 10The stride shall not be zero. 11When the stride is positive, the subscripts specified by a triplet form a regularly spaced sequence of 12integers beginning with the first subscript and proceeding in increments of the stride to the largest such 13integer not greater than the second subscript; the sequence is empty if the first subscript is greater than 14the second. NOTE 6.12 For example, suppose an array is declared as A (5, 4, 3). The section A (3 : 5, 2, 1 : 2) is the array of shape (3, 2): A (3, 2, 1) A (3, 2, 2) A (4, 2, 1) A (4, 2, 2) A (5, 2, 1) A (5, 2, 2) 15When the stride is negative, the sequence begins with the first subscript and proceeds in increments of 16the stride down to the smallest such integer equal to or greater than the second subscript; the sequence 17is empty if the second subscript is greater than the first. NOTE 6.13 For example, if an array is declared B (10), the section B (9 : 1 : ­2) is the array of shape (5) whose elements are B (9), B (7), B (5), B (3), and B (1), in that order. NOTE 6.14 A subscript in a subscript triplet need not be within the declared bounds for that dimension if all values used in selecting the array elements are within the declared bounds. For example, if an array is declared as B (10), the array section B (3 : 11 : 7) is the array of shape (2) consisting of the elements B (3) and B (10), in that order. 186.2.2.3.2 Vector subscript 19A vector subscript designates a sequence of subscripts corresponding to the values of the elements 20of the expression. Each element of the expression shall be defined. A many-one array section is an 21array section with a vector subscript having two or more elements with the same value. A many-one 22array section shall appear neither on the left of the equals in an assignment statement nor as an input 23item in a READ statement. 24An array section with a vector subscript shall not be argument associated with a dummy array that 25is defined or redefined. An array section with a vector subscript shall not be the target in a pointer 109 J3/04-007 WORKING DRAFT MAY 2004 1assignment statement. An array section with a vector subscript shall not be an internal file. NOTE 6.15 For example, suppose Z is a two-dimensional array of shape (5, 7) and U and V are one-dimensional arrays of shape (3) and (4), respectively. Assume the values of U and V are: U = (/ 1, 3, 2 /) V = (/ 2, 1, 1, 3 /) Then Z (3, V) consists of elements from the third row of Z in the order: Z (3, 2) Z (3, 1) Z (3, 1) Z (3, 3) and Z (U, 2) consists of the column elements: Z (1, 2) Z (3, 2) Z (2, 2) and Z (U, V) consists of the elements: Z (1, 2) Z (1, 1) Z (1, 1) Z (1, 3) Z (3, 2) Z (3, 1) Z (3, 1) Z (3, 3) Z (2, 2) Z (2, 1) Z (2, 1) Z (2, 3) Because Z (3, V) and Z (U, V) contain duplicate elements from Z, the sections Z (3, V) and Z (U, V) shall not be redefined as sections. 26.3 Dynamic association 3Dynamic control over the allocation, association, and deallocation of pointer targets is provided by 4the ALLOCATE, NULLIFY, and DEALLOCATE statements and pointer assignment. ALLOCATE 5(6.3.1) creates targets for pointers; pointer assignment (7.4.2) associates pointers with existing targets; 6NULLIFY (6.3.2) disassociates pointers from targets, and DEALLOCATE (6.3.3) deallocates targets. 7Dynamic association applies to scalars and arrays of any type. 8The ALLOCATE and DEALLOCATE statements also are used to create and deallocate variables with 9the ALLOCATABLE attribute. NOTE 6.16 Detailed remarks regarding pointers and dynamic association are in C.3.3. 106.3.1 ALLOCATE statement 11The ALLOCATE statement dynamically creates pointer targets and allocatable variables. 12R623 allocate-stmt is ALLOCATE ( [ type-spec :: ] allocation-list 13 [, alloc-opt-list ] ) 14R624 alloc-opt is STAT = stat-variable 15 or ERRMSG = errmsg-variable 16 or SOURCE = source-expr 17R625 stat-variable is scalar-int-variable 18R626 errmsg-variable is scalar-default-char-variable 19R627 source-expr is expr 20R628 allocation is allocate-object [ ( allocate-shape-spec-list ) ] 110 MAY 2004 WORKING DRAFT J3/04-007 1R629 allocate-object is variable-name 2 or structure-component 3R630 allocate-shape-spec is [ lower-bound-expr : ] upper-bound-expr 4R631 lower-bound-expr is scalar-int-expr 5R632 upper-bound-expr is scalar-int-expr 6C622 (R629) Each allocate-object shall be a nonprocedure pointer or an allocatable variable. 7C623 (R623) If any allocate-object in the statement has a deferred type parameter, either type-spec or 8 SOURCE= shall appear. 9C624 (R623) If a type-spec appears, it shall specify a type with which each allocate-object is type 10 compatible. 11C625 (R623) If any allocate-object is unlimited polymorphic, either type-spec or SOURCE= shall 12 appear. 13C626 (R623) A type-param-value in a type-spec shall be an asterisk if and only if each allocate-object 14 is a dummy argument for which the corresponding type parameter is assumed. 15C627 (R623) If a type-spec appears, the kind type parameter values of each allocate-object shall be 16 the same as the corresponding type parameter values of the type-spec. 17C628 (R628) An allocate-shape-spec-list shall appear if and only if the allocate-object is an array. 18C629 (R628) The number of allocate-shape-specs in an allocate-shape-spec-list shall be the same as 19 the rank of the allocate-object. 20C630 (R624) No alloc-opt shall appear more than once in a given alloc-opt-list. 21C631 (R623) If SOURCE= appears, type-spec shall not appear and allocation-list shall contain only 22 one allocate-object, which shall be type compatible (5.1.1.2) with source-expr. 23C632 (R623) The source-expr shall be a scalar or have the same rank as allocate-object. 24C633 (R623) Corresponding kind type parameters of allocate-object and source-expr shall have the 25 same values. 26An allocate-object or a bound or type parameter of an allocate-object shall not depend on the value of 27stat-variable, the value of errmsg-variable, or on the value, bounds, length type parameters, allocation 28status, or association status of any allocate-object in the same ALLOCATE statement. 29Neither stat-variable, source-expr, nor errmsg-variable shall be allocated within the ALLOCATE state- 30ment in which it appears; nor shall they depend on the value, bounds, length type parameters, allocation 31status, or association status of any allocate-object in the same ALLOCATE statement. 32The optional type-spec specifies the dynamic type and type parameters of the objects to be allocated. If 33a type-spec is specified, allocation of a polymorphic object allocates an object with the specified dynamic 34type; if a source-expr is specified, the allocation allocates an object whose dynamic type and type 35parameters are the same as those of the source-expr; otherwise it allocates an object with a dynamic 36type the same as its declared type. 37When an ALLOCATE statement having a type-spec is executed, any type-param-values in the type-spec 38specify the type parameters. If the value specified for a type parameter differs from a corresponding 39nondeferred value specified in the declaration of any of the allocate-objects then an error condition occurs. 40If a type-param-value in a type-spec in an ALLOCATE statement is an asterisk, it denotes the current 41value of that assumed type parameter. If it is an expression, subsequent redefinition or undefinition of 111 J3/04-007 WORKING DRAFT MAY 2004 1any entity in the expression does not affect the type parameter value. NOTE 6.17 An example of an ALLOCATE statement is: ALLOCATE (X (N), B (-3 : M, 0:9), STAT = IERR_ALLOC) 2When an ALLOCATE statement is executed for an array, the values of the lower bound and upper 3bound expressions determine the bounds of the array. Subsequent redefinition or undefinition of any 4entities in the bound expressions do not affect the array bounds. If the lower bound is omitted, the 5default value is 1. If the upper bound is less than the lower bound, the extent in that dimension is zero 6and the array has zero size. NOTE 6.18 An allocate-object may be of type character with zero character length. 7If SOURCE= appears, source-expr shall be conformable (2.4.5) with allocation. If the value of a non- 8deferred length type parameter of allocate-object is different from the value of the corresponding type 9parameter of source-expr, an error condition occurs. If the allocation is successful, the value of allocate- 10object becomes that of source-expr. NOTE 6.19 An example of an ALLOCATE statement in which the value and dynamic type are determined by reference to another object is: CLASS(*), ALLOCATABLE :: NEW CLASS(*), POINTER :: OLD ! ... ALLOCATE (NEW, SOURCE=OLD) ! Allocate NEW with the value and dynamic type of OLD A more extensive example is given in C.3.2. 11If the STAT= specifier appears, successful execution of the ALLOCATE statement causes the stat- 12variable to become defined with a value of zero. If an error condition occurs during the execution 13of the ALLOCATE statement, the stat-variable becomes defined with a processor-dependent positive 14integer value and each allocate-object will have a processor-dependent status; each allocate-object that 15was successfully allocated shall have an allocation status of allocated or a pointer association status of 16associated; each allocate-object that was not successfully allocated shall retain its previous allocation 17status or pointer association status. 18If an error condition occurs during execution of an ALLOCATE statement that does not contain the 19STAT= specifier, execution of the program is terminated. 20The ERRMSG= specifier is described in 6.3.1.3. 216.3.1.1 Allocation of allocatable variables 22The allocation status of an allocatable entity is one of the following at any time during the execution of 23a program: 24 (1) The status of an allocatable variable becomes allocated if it is allocated by an ALLOCATE 25 statement, if it is allocated during assignment, or if it is given that status by the allocation 26 transfer procedure (13.5.16). An allocatable variable with this status may be referenced, 27 defined, or deallocated; allocating it causes an error condition in the ALLOCATE statement. 112 MAY 2004 WORKING DRAFT J3/04-007 1 The intrinsic function ALLOCATED (13.7.9) returns true for such a variable. 2 (2) An allocatable variable has a status of unallocated if it is not allocated. The status of 3 an allocatable variable becomes unallocated if it is deallocated (6.3.3) or if it is given that 4 status by the allocation transfer procedure. An allocatable variable with this status shall 5 not be referenced or defined. It shall not be supplied as an actual argument corresponding 6 to a nonallocatable dummy argument, except to certain intrinsic inquiry functions. It may 7 be allocated with the ALLOCATE statement. Deallocating it causes an error condition in 8 the DEALLOCATE statement. The intrinsic function ALLOCATED (13.7.9) returns false 9 for such a variable. 10At the beginning of execution of a program, allocatable variables are unallocated. 11A saved allocatable object has an initial status of unallocated. The status may change during the 12execution of the program. 13When the allocation status of an allocatable variable changes, the allocation status of any associated 14allocatable variable changes accordingly. Allocation of an allocatable variable establishes values for the 15deferred type parameters of all associated allocatable variables. 16An unsaved allocatable object that is a local variable of a procedure has a status of unallocated at the 17beginning of each invocation of the procedure. The status may change during execution of the procedure. 18An unsaved allocatable object that is a local variable of a module or a subobject thereof has an initial 19status of unallocated. The status may change during execution of the program. 20When an object of derived type is created by an ALLOCATE statement, any allocatable ultimate 21components have an allocation status of unallocated. 226.3.1.2 Allocation of pointer targets 23Allocation of a pointer creates an object that implicitly has the TARGET attribute. Following successful 24execution of an ALLOCATE statement for a pointer, the pointer is associated with the target and may 25be used to reference or define the target. Additional pointers may become associated with the pointer 26target or a part of the pointer target by pointer assignment. It is not an error to allocate a pointer 27that is already associated with a target. In this case, a new pointer target is created as required by the 28attributes of the pointer and any array bounds, type, and type parameters specified by the ALLOCATE 29statement. The pointer is then associated with this new target. Any previous association of the pointer 30with a target is broken. If the previous target had been created by allocation, it becomes inaccessible 31unless other pointers are associated with it. The ASSOCIATED intrinsic function (13.7.13) may be used 32to determine whether a pointer that does not have undefined association status is associated. 33At the beginning of execution of a function whose result is a pointer, the association status of the result 34pointer is undefined. Before such a function returns, it shall either associate a target with this pointer 35or cause the association status of this pointer to become defined as disassociated. 366.3.1.3 ERRMSG= specifier 37If an error condition occurs during execution of an ALLOCATE or DEALLOCATE statement, the 38processor shall assign an explanatory message to errmsg-variable. If no such condition occurs, the 39processor shall not change the value of errmsg-variable. 406.3.2 NULLIFY statement 41The NULLIFY statement causes pointers to be disassociated. 42R633 nullify-stmt is NULLIFY ( pointer-object-list ) 43R634 pointer-object is variable-name 113 J3/04-007 WORKING DRAFT MAY 2004 1 or structure-component 2 or proc-pointer-name 3C634 (R634) Each pointer-object shall have the POINTER attribute. 4A pointer-object shall not depend on the value, bounds, or association status of another pointer-object 5in the same NULLIFY statement. NOTE 6.20 When a NULLIFY statement is applied to a polymorphic pointer (5.1.1.2), its dynamic type becomes the declared type. 66.3.3 DEALLOCATE statement 7The DEALLOCATE statement causes allocatable variables to be deallocated; it causes pointer tar- 8gets to be deallocated and the pointers to be disassociated. 9R635 deallocate-stmt is DEALLOCATE ( allocate-object-list [ , dealloc-opt-list ] ) 10C635 (R635) Each allocate-object shall be a nonprocedure pointer or an allocatable variable. 11R636 dealloc-opt is STAT = stat-variable 12 or ERRMSG = errmsg-variable 13C636 (R636) No dealloc-opt shall appear more than once in a given dealloc-opt-list. 14An allocate-object shall not depend on the value, bounds, allocation status, or association status of 15another allocate-object in the same DEALLOCATE statement; it also shall not depend on the value of 16the stat-variable or errmsg-variable in the same DEALLOCATE statement. 17Neither stat-variable nor errmsg-variable shall be deallocated within the same DEALLOCATE state- 18ment; they also shall not depend on the value, bounds, allocation status, or association status of any 19allocate-object in the same DEALLOCATE statement. 20If the STAT= specifier appears, successful execution of the DEALLOCATE statement causes the stat- 21variable to become defined with a value of zero. If an error condition occurs during the execution of 22the DEALLOCATE statement, the stat-variable becomes defined with a processor-dependent positive 23integer value and each allocate-object that was successfully deallocated shall have an allocation status of 24unallocated or a pointer association status of disassociated. Each allocate-object that was not successfully 25deallocated shall retain its previous allocation status or pointer association status. NOTE 6.21 The status of objects that were not successfully deallocated can be individually checked with the ALLOCATED or ASSOCIATED intrinsic functions. 26If an error condition occurs during execution of a DEALLOCATE statement that does not contain the 27STAT= specifier, execution of the program is terminated. 28The ERRMSG= specifier is described in 6.3.1.3. NOTE 6.22 An example of a DEALLOCATE statement is: DEALLOCATE (X, B) 114 MAY 2004 WORKING DRAFT J3/04-007 16.3.3.1 Deallocation of allocatable variables 2Deallocating an unallocated allocatable variable causes an error condition in the DEALLOCATE state- 3ment. Deallocating an allocatable variable with the TARGET attribute causes the pointer association 4status of any pointer associated with it to become undefined. 5When the execution of a procedure is terminated by execution of a RETURN or END statement, an 6allocatable variable that is a named local variable of the procedure retains its allocation and definition 7status if it has the SAVE attribute or is a function result variable or a subobject thereof; otherwise, it 8is deallocated. NOTE 6.23 The ALLOCATED intrinsic function may be used to determine whether a variable is allocated or unallocated. 9If an unsaved allocatable object is a local variable of a module, and it is allocated when execution 10of a RETURN or END statement results in no active scoping unit having access to the module, it is 11processor-dependent whether the object retains its allocation status or is deallocated. NOTE 6.24 The following example illustrates the effects of SAVE on allocation status. MODULE MOD1 TYPE INITIALIZED_TYPE INTEGER :: I = 1 ! Default initialization END TYPE INITIALIZED_TYPE SAVE :: SAVED1, SAVED2 INTEGER :: SAVED1, UNSAVED1 TYPE(INITIALIZED_TYPE) :: SAVED2, UNSAVED2 ALLOCATABLE :: SAVED1(:), SAVED2(:), UNSAVED1(:), UNSAVED2(:) END MODULE MOD1 PROGRAM MAIN CALL SUB1 ! The values returned by the ALLOCATED intrinsic calls ! in the PRINT statement are: ! .FALSE., .FALSE., .FALSE., and .FALSE. ! Module MOD1 is used, and its variables are allocated. ! After return from the subroutine, whether the variables ! which were not specified with the SAVE attribute ! retain their allocation status is processor dependent. CALL SUB1 ! The values returned by the first two ALLOCATED intrinsic ! calls in the PRINT statement are: ! .TRUE., .TRUE. ! The values returned by the second two ALLOCATED ! intrinsic calls in the PRINT statement are ! processor dependent and each could be either ! .TRUE. or .FALSE. CONTAINS SUBROUTINE SUB1 USE MOD1 ! Brings in saved and unsaved variables. PRINT *, ALLOCATED(SAVED1), ALLOCATED(SAVED2), & ALLOCATED(UNSAVED1), ALLOCATED(UNSAVED2) IF (.NOT. ALLOCATED(SAVED1)) ALLOCATE(SAVED1(10)) IF (.NOT. ALLOCATED(SAVED2)) ALLOCATE(SAVED2(10)) IF (.NOT. ALLOCATED(UNSAVED1)) ALLOCATE(UNSAVED1(10)) 115 J3/04-007 WORKING DRAFT MAY 2004 NOTE 6.24 (cont.) IF (.NOT. ALLOCATED(UNSAVED2)) ALLOCATE(UNSAVED2(10)) END SUBROUTINE SUB1 END PROGRAM MAIN 1If an executable construct references a function whose result is either allocatable or a structure with 2a subobject that is allocatable, and the function reference is executed, an allocatable result and any 3subobject that is an allocated allocatable entity in the result returned by the function is deallocated 4after execution of the innermost executable construct containing the reference. 5If a specification expression in a scoping unit references a function whose result is either allocatable or 6a structure with a subobject that is allocatable, and the function reference is executed, an allocatable 7result and any subobject that is an allocated allocatable entity in the result returned by the function is 8deallocated before execution of the first executable statement in the scoping unit. 9When a procedure is invoked, any allocated allocatable object that is an actual argument associated with 10an INTENT(OUT) allocatable dummy argument is deallocated; any allocated allocatable object that is 11a subobject of an actual argument associated with an INTENT(OUT) dummy argument is deallocated. 12When an intrinsic assignment statement (7.4.1.3) is executed, any allocated allocatable subobject of the 13variable is deallocated before the assignment takes place. 14When a variable of derived type is deallocated, any allocated allocatable subobject is deallocated. 15If an allocatable component is a subobject of a finalizable object, that object is finalized before the 16component is automatically deallocated. 17The effect of automatic deallocation is the same as that of a DEALLOCATE statement without a 18dealloc-opt-list. NOTE 6.25 In the following example: SUBROUTINE PROCESS REAL, ALLOCATABLE :: TEMP(:) REAL, ALLOCATABLE, SAVE :: X(:) ... END SUBROUTINE PROCESS on return from subroutine PROCESS, the allocation status of X is preserved because X has the SAVE attribute. TEMP does not have the SAVE attribute, so it will be deallocated. On the next invocation of PROCESS, TEMP will have an allocation status of unallocated. 196.3.3.2 Deallocation of pointer targets 20If a pointer appears in a DEALLOCATE statement, its association status shall be defined. Deallocating 21a pointer that is disassociated or whose target was not created by an ALLOCATE statement causes an 22error condition in the DEALLOCATE statement. If a pointer is associated with an allocatable entity, 23the pointer shall not be deallocated. 24If a pointer appears in a DEALLOCATE statement, it shall be associated with the whole of an object 25that was created by allocation. Deallocating a pointer target causes the pointer association status of 26any other pointer that is associated with the target or a portion of the target to become undefined. 116 MAY 2004 WORKING DRAFT J3/04-007 1Section 7: Expressions and assignment 2This section describes the formation, interpretation, and evaluation rules for expressions, intrinsic and 3defined assignment, pointer assignment, masked array assignment (WHERE), and FORALL. 47.1 Expressions 5An expression represents either a data reference or a computation, and its value is either a scalar or 6an array. An expression is formed from operands, operators, and parentheses. 7An operand is either a scalar or an array. An operation is either intrinsic or defined (7.2). More 8complicated expressions can be formed using operands which are themselves expressions. 9Evaluation of an expression produces a value, which has a type, type parameters (if appropriate), and a 10shape (7.1.4). 117.1.1 Form of an expression 12An expression is defined in terms of several categories: primary, level-1 expression, level-2 expression, 13level-3 expression, level-4 expression, and level-5 expression. 14These categories are related to the different operator precedence levels and, in general, are defined in 15terms of other categories. The simplest form of each expression category is a primary. The rules given 16below specify the syntax of an expression. The semantics are specified in 7.2. 177.1.1.1 Primary 18R701 primary is constant 19 or designator 20 or array-constructor 21 or structure-constructor 22 or function-reference 23 or type-param-inquiry 24 or type-param-name 25 or ( expr ) 26C701 (R701) The type-param-name shall be the name of a type parameter. 27C702 (R701) The designator shall not be a whole assumed-size array. NOTE 7.1 Examples of a primary are: Example Syntactic class 1.0 constant 'ABCDEFGHIJKLMNOPQRSTUVWXYZ' (I:I) constant-subobject A variable (/ 1.0, 2.0 /) array-constructor PERSON (12, 'Jones') structure-constructor F (X, Y) function-reference 117 J3/04-007 WORKING DRAFT MAY 2004 NOTE 7.1 (cont.) (S + T) (expr) 17.1.1.2 Level-1 expressions 2Defined unary operators have the highest operator precedence (Table 7.7). Level-1 expressions are 3primaries optionally operated on by defined unary operators: 4R702 level-1-expr is [ defined-unary-op ] primary 5R703 defined-unary-op is . letter [ letter ] ... . 6C703 (R703) A defined-unary-op shall not contain more than 63 letters and shall not be the same as 7 any intrinsic-operator or logical-literal-constant. NOTE 7.2 Simple examples of a level-1 expression are: Example Syntactic class A primary (R701) .INVERSE. B level-1-expr (R702) A more complicated example of a level-1 expression is: .INVERSE. (A + B) 87.1.1.3 Level-2 expressions 9Level-2 expressions are level-1 expressions optionally involving the numeric operators power-op, mult-op, 10and add-op. 11R704 mult-operand is level-1-expr [ power-op mult-operand ] 12R705 add-operand is [ add-operand mult-op ] mult-operand 13R706 level-2-expr is [ [ level-2-expr ] add-op ] add-operand 14R707 power-op is ** 15R708 mult-op is * 16 or / 17R709 add-op is + 18 or ­ NOTE 7.3 Simple examples of a level-2 expression are: Example Syntactic class Remarks A level-1-expr A is a primary. (R702) B ** C mult-operand B is a level-1-expr, ** is a power-op, and C is a mult-operand. (R704) D * E add-operand D is an add-operand, * is a mult-op, and E is a mult-operand. (R705) +1 level-2-expr + is an add-op and 1 is an add-operand. (R706) F - I level-2-expr F is a level-2-expr, ­ is an add-op, and I is an add-operand. (R706) A more complicated example of a level-2 expression is: 118 MAY 2004 WORKING DRAFT J3/04-007 NOTE 7.3 (cont.) - A + D * E + B ** C 17.1.1.4 Level-3 expressions 2Level-3 expressions are level-2 expressions optionally involving the character operator concat-op. 3R710 level-3-expr is [ level-3-expr concat-op ] level-2-expr 4R711 concat-op is // NOTE 7.4 Simple examples of a level-3 expression are: Example Syntactic class A level-2-expr (R706) B // C level-3-expr (R710) A more complicated example of a level-3 expression is: X // Y // 'ABCD' 57.1.1.5 Level-4 expressions 6Level-4 expressions are level-3 expressions optionally involving the relational operators rel-op. 7R712 level-4-expr is [ level-3-expr rel-op ] level-3-expr 8R713 rel-op is .EQ. 9 or .NE. 10 or .LT. 11 or .LE. 12 or .GT. 13 or .GE. 14 or == 15 or /= 16 or < 17 or <= 18 or > 19 or >= NOTE 7.5 Simple examples of a level-4 expression are: Example Syntactic class A level-3-expr (R710) B == C level-4-expr (R712) D < E level-4-expr (R712) A more complicated example of a level-4 expression is: (A + B) /= C 119 J3/04-007 WORKING DRAFT MAY 2004 17.1.1.6 Level-5 expressions 2Level-5 expressions are level-4 expressions optionally involving the logical operators not-op, and-op, 3or-op, and equiv-op. 4R714 and-operand is [ not-op ] level-4-expr 5R715 or-operand is [ or-operand and-op ] and-operand 6R716 equiv-operand is [ equiv-operand or-op ] or-operand 7R717 level-5-expr is [ level-5-expr equiv-op ] equiv-operand 8R718 not-op is .NOT. 9R719 and-op is .AND. 10R720 or-op is .OR. 11R721 equiv-op is .EQV. 12 or .NEQV. NOTE 7.6 Simple examples of a level-5 expression are: Example Syntactic class A level-4-expr (R712) .NOT. B and-operand (R714) C .AND. D or-operand (R715) E .OR. F equiv-operand (R716) G .EQV. H level-5-expr (R717) S .NEQV. T level-5-expr (R717) A more complicated example of a level-5 expression is: A .AND. B .EQV. .NOT. C 137.1.1.7 General form of an expression 14Expressions are level-5 expressions optionally involving defined binary operators. Defined binary oper- 15ators have the lowest operator precedence (Table 7.7). 16R722 expr is [ expr defined-binary-op ] level-5-expr 17R723 defined-binary-op is . letter [ letter ] ... . 18C704 (R723) A defined-binary-op shall not contain more than 63 letters and shall not be the same as 19 any intrinsic-operator or logical-literal-constant. NOTE 7.7 Simple examples of an expression are: Example Syntactic class A level-5-expr (R717) B.UNION.C expr (R722) More complicated examples of an expression are: (B .INTERSECT. C) .UNION. (X - Y) A + B == C * D .INVERSE. (A + B) A + B .AND. C * D E // G == H (1:10) 120 MAY 2004 WORKING DRAFT J3/04-007 17.1.2 Intrinsic operations 2An intrinsic operation is either an intrinsic unary operation or an intrinsic binary operation. An 3intrinsic unary operation is an operation of the form intrinsic-operator x2 where x2 is of an intrinsic 4type (4.4) listed in Table 7.1 for the unary intrinsic operator. 5An intrinsic binary operation is an operation of the form x1 intrinsic-operator x2 where x1 and 6x2 are of the intrinsic types (4.4) listed in Table 7.1 for the binary intrinsic operator and are in shape 7conformance (7.1.5). Table 7.1: Type of operands and results for intrinsic operators Intrinsic operator Type of Type of Type of op x1 x2 [x1] op x2 Unary +, ­ I, R, Z I, R, Z I I, R, Z I, R, Z Binary +, ­, *, /, ** R I, R, Z R, R, Z Z I, R, Z Z, Z, Z // C C C I I, R, Z L, L, L .EQ., .NE., R I, R, Z L, L, L ==, /= Z I, R, Z L, L, L C C L I I, R L, L .GT., .GE., .LT., .LE. R I, R L, L >, >=, <, <= C C L .NOT. L L .AND., .OR., .EQV., .NEQV. L L L Note: The symbols I, R, Z, C, and L stand for the types integer, real, complex, character, and logical, respectively. Where more than one type for x2 is given, the type of the result of the operation is given in the same relative position in the next column. For the intrinsic operators with operands of type character, the kind type parameters of the operands shall be the same. 8A numeric intrinsic operation is an intrinsic operation for which the intrinsic-operator is a numeric 9operator (+, ­, *, /, or **). A numeric intrinsic operator is the operator in a numeric intrinsic 10operation. 11For numeric intrinsic binary operations, the two operands may be of different numeric types or different 12kind type parameters. Except for a value raised to an integer power, if the operands have different types 13or kind type parameters, the effect is as if each operand that differs in type or kind type parameter from 14those of the result is converted to the type and kind type parameter of the result before the operation 15is performed. When a value of type real or complex is raised to an integer power, the integer operand 16need not be converted. 17A character intrinsic operation, relational intrinsic operation, and logical intrinsic operation 18are similarly defined in terms of a character intrinsic operator (//), relational intrinsic operator 19(.EQ., .NE., .GT., .GE., .LT., .LE., ==, /=, >, >=, <, and <=), and logical intrinsic operator 20(.AND., .OR., .NOT., .EQV., and .NEQV.), respectively. For the character intrinsic operator //, the 21kind type parameters shall be the same. For the relational intrinsic operators with character operands, 22the kind type parameters shall be the same. 23A numeric relational intrinsic operation is a relational intrinsic operation where the operands are 24of numeric type. A character relational intrinsic operation is a relational intrinsic operation where 25the operands are of type character. 121 J3/04-007 WORKING DRAFT MAY 2004 17.1.3 Defined operations 2A defined operation is either a defined unary operation or a defined binary operation. A defined 3unary operation is an operation that has the form defined-unary-op x2 or intrinsic-operator x2 and 4that is defined by a function and a generic interface (4.5.1, 12.3.2.1). 5A function defines the unary operation op x2 if 6 (1) The function is specified with a FUNCTION (12.5.2.1) or ENTRY (12.5.2.4) statement that 7 specifies one dummy argument d2, 8 (2) Either 9 (a) A generic interface (12.3.2.1) provides the function with a generic-spec of OPERA- 10 TOR (op), or 11 (b) There is a generic binding (4.5.1) in the declared type of x2 with a generic-spec of 12 OPERATOR (op) and there is a corresponding binding to the function in the dynamic 13 type of x2, 14 (3) The type of d2 is compatible with the dynamic type of x2, 15 (4) The type parameters, if any, of d2 match the corresponding type parameters of x2, and 16 (5) Either 17 (a) The rank of x2 matches that of d2 or 18 (b) The function is elemental and there is no other function that defines the operation. 19If d2 is an array, the shape of x2 shall match the shape of d2. 20A defined binary operation is an operation that has the form x1 defined-binary-op x2 or x1 intrinsic- 21operator x2 and that is defined by a function and a generic interface. 22A function defines the binary operation x1 op x2 if 23 (1) The function is specified with a FUNCTION (12.5.2.1) or ENTRY (12.5.2.4) statement that 24 specifies two dummy arguments, d1 and d2, 25 (2) Either 26 (a) A generic interface (12.3.2.1) provides the function with a generic-spec of OPERA- 27 TOR (op), or 28 (b) There is a generic binding (4.5.1) in the declared type of x1 or x2 with a generic- 29 spec of OPERATOR (op) and there is a corresponding binding to the function in the 30 dynamic type of x1 or x2, respectively, 31 (3) The types of d1 and d2 are compatible with the dynamic types of x1 and x2, respectively, 32 (4) The type parameters, if any, of d1 and d2 match the corresponding type parameters of x1 33 and x2, respectively, and 34 (5) Either 35 (a) The ranks of x1 and x2 match those of d1 and d2 or 36 (b) The function is elemental, x1 and x2 are conformable, and there is no other function 37 that defines the operation. 38If d1 or d2 is an array, the shapes of x1 and x2 shall match the shapes of d1 and d2, respectively. NOTE 7.8 An intrinsic operator may be used as the operator in a defined operation. In such a case, the generic properties of the operator are extended. 122 MAY 2004 WORKING DRAFT J3/04-007 1An extension operation is a defined operation in which the operator is of the form defined-unary-op 2or defined-binary-op. Such an operator is called an extension operator. The operator used in an 3extension operation may be such that a generic interface for the operator may specify more than one 4function. 5A defined elemental operation is a defined operation for which the function is elemental (12.7). 67.1.4 Type, type parameters, and shape of an expression 7The type, type parameters, and shape of an expression depend on the operators and on the types, type 8parameters, and shapes of the primaries used in the expression, and are determined recursively from 9the syntactic form of the expression. The type of an expression is one of the intrinsic types (4.4) or a 10derived type (4.5). 11If an expression is a polymorphic primary or defined operation, the type parameters and the declared and 12dynamic types of the expression are the same as those of the primary or defined operation. Otherwise 13the type parameters and dynamic type of the expression are the same as its declared type and type 14parameters; they are referred to simply as the type and type parameters of the expression. 15R724 logical-expr is expr 16C705 (R724) logical-expr shall be of type logical. 17R725 char-expr is expr 18C706 (R725) char-expr shall be of type character. 19R726 default-char-expr is expr 20C707 (R726) default-char-expr shall be of type default character. 21R727 int-expr is expr 22C708 (R727) int-expr shall be of type integer. 23R728 numeric-expr is expr 24C709 (R728) numeric-expr shall be of type integer, real, or complex. 257.1.4.1 Type, type parameters, and shape of a primary 26The type, type parameters, and shape of a primary are determined according to whether the primary is a 27constant, variable, array constructor, structure constructor, function reference, type parameter inquiry, 28type parameter name, or parenthesized expression. If a primary is a constant, its type, type parameters, 29and shape are those of the constant. If it is a structure constructor, it is scalar and its type and type 30parameters are as described in 4.5.9. If it is an array constructor, its type, type parameters, and shape 31are as described in 4.7. If it is a variable or function reference, its type, type parameters, and shape are 32those of the variable (5.1.1, 5.1.2) or the function reference (12.4.2), respectively. If the function reference 33is generic (12.3.2.1, 13.5) then its type, type parameters, and shape are those of the specific function 34referenced, which is determined by the types, type parameters, and ranks of its actual arguments as 35specified in 12.4.4.1. If it is a type parameter inquiry or type parameter name, it is a scalar integer with 36the kind of the type parameter. 37If a primary is a parenthesized expression, its type, type parameters, and shape are those of the expres- 38sion. 39If a pointer appears as one of the following, the associated target object is referenced: 123 J3/04-007 WORKING DRAFT MAY 2004 1 (1) A primary in an intrinsic or defined operation, 2 (2) The expr of a parenthesized primary, or 3 (3) The only primary on the right-hand side of an intrinsic assignment statement. 4The type, type parameters, and shape of the primary are those of the current target. If the pointer is 5not associated with a target, it may appear as a primary only as an actual argument in a reference to 6a procedure whose corresponding dummy argument is declared to be a pointer, or as the target in a 7pointer assignment statement. 8A disassociated array pointer or an unallocated allocatable array has no shape but does have rank. The 9type, type parameters, and rank of the result of the NULL intrinsic function depend on context (13.7.88). 107.1.4.2 Type, type parameters, and shape of the result of an operation 11The type of the result of an intrinsic operation [x1] op x2 is specified by Table 7.1. The shape of the 12result of an intrinsic operation is the shape of x2 if op is unary or if x1 is scalar, and is the shape of x1 13otherwise. 14The type, type parameters, and shape of the result of a defined operation [x1] op x2 are specified by the 15function defining the operation (7.2). 16An expression of an intrinsic type has a kind type parameter. An expression of type character also has 17a character length parameter. 18The type parameters of the result of an intrinsic operation are as follows: 19 (1) For an expression x1 // x2 where // is the character intrinsic operator and x1 and x2 are 20 of type character, the character length parameter is the sum of the lengths of the operands 21 and the kind type parameter is the kind type parameter of x1, which shall be the same as 22 the kind type parameter of x2. 23 (2) For an expression op x2 where op is an intrinsic unary operator and x2 is of type integer, 24 real, complex, or logical, the kind type parameter of the expression is that of the operand. 25 (3) For an expression x1 op x2 where op is a numeric intrinsic binary operator with one operand 26 of type integer and the other of type real or complex, the kind type parameter of the 27 expression is that of the real or complex operand. 28 (4) For an expression x1 op x2 where op is a numeric intrinsic binary operator with both 29 operands of the same type and kind type parameters, or with one real and one complex 30 with the same kind type parameters, the kind type parameter of the expression is identical 31 to that of each operand. In the case where both operands are integer with different kind type 32 parameters, the kind type parameter of the expression is that of the operand with the greater 33 decimal exponent range if the decimal exponent ranges are different; if the decimal exponent 34 ranges are the same, the kind type parameter of the expression is processor dependent, but 35 it is the same as that of one of the operands. In the case where both operands are any 36 of type real or complex with different kind type parameters, the kind type parameter of 37 the expression is that of the operand with the greater decimal precision if the decimal 38 precisions are different; if the decimal precisions are the same, the kind type parameter of 39 the expression is processor dependent, but it is the same as that of one of the operands. 40 (5) For an expression x1 op x2 where op is a logical intrinsic binary operator with both operands 41 of the same kind type parameter, the kind type parameter of the expression is identical to 42 that of each operand. In the case where both operands are of type logical with different 43 kind type parameters, the kind type parameter of the expression is processor dependent, 44 but it is the same as that of one of the operands. 45 (6) For an expression x1 op x2 where op is a relational intrinsic operator, the expression has 46 the default logical kind type parameter. 124 MAY 2004 WORKING DRAFT J3/04-007 17.1.5 Conformability rules for elemental operations 2An elemental operation is an intrinsic operation or a defined elemental operation. Two entities are 3in shape conformance if both are arrays of the same shape, or one or both are scalars. 4For all elemental binary operations, the two operands shall be in shape conformance. In the case where 5one is a scalar and the other an array, the scalar is treated as if it were an array of the same shape as 6the array operand with every element, if any, of the array equal to the value of the scalar. 77.1.6 Specification expression 8A specification expression is an expression with limitations that make it suitable for use in specifi- 9cations such as length type parameters (C501) and array bounds (R512, R513). 10R729 specification-expr is scalar-int-expr 11C710 (R729) The scalar-int-expr shall be a restricted expression. 12A restricted expression is an expression in which each operation is intrinsic and each primary is 13 (1) A constant or subobject of a constant, 14 (2) An object designator with a base object that is a dummy argument that has neither the 15 OPTIONAL nor the INTENT (OUT) attribute, 16 (3) An object designator with a base object that is in a common block, 17 (4) An object designator with a base object that is made accessible by use association or host 18 association, 19 (5) An array constructor where each element and each scalar-int-expr of each ac-implied-do- 20 control is a restricted expression, 21 (6) A structure constructor where each component is a restricted expression, 22 (7) A specification inquiry where each designator or function argument is 23 (a) a restricted expression or 24 (b) a variable whose properties inquired about are not 25 (i) dependent on the upper bound of the last dimension of an assumed-size array, 26 (ii) deferred, or 27 (iii) defined by an expression that is not a restricted expression, 28 (8) A reference to any other standard intrinsic function where each argument is a restricted 29 expression, 30 (9) A reference to a specification function where each argument is a restricted expression, 31 (10) A type parameter of the derived type being defined, 32 (11) An ac-do-variable within an array constructor where each scalar-int-expr of the correspond- 33 ing ac-implied-do-control is a restricted expression, or 34 (12) A restricted expression enclosed in parentheses, 35where each subscript, section subscript, substring starting point, substring ending point, and type pa- 36rameter value is a restricted expression, and where any final subroutine that is invoked is pure. 37A specification inquiry is a reference to 38 (1) an array inquiry function (13.5.7), 39 (2) the bit inquiry function BIT SIZE, 40 (3) the character inquiry function LEN, 41 (4) the kind inquiry function KIND, 125 J3/04-007 WORKING DRAFT MAY 2004 1 (5) the character inquiry function NEW LINE, 2 (6) a numeric inquiry function (13.5.6), 3 (7) a type parameter inquiry (6.1.3), or 4 (8) an IEEE inquiry function (14.9.1), 5A function is a specification function if it is a pure function, is not a standard intrinsic function, is 6not an internal function, is not a statement function, and does not have a dummy procedure argument. 7Evaluation of a specification expression shall not directly or indirectly cause a procedure defined by the 8subprogram in which it appears to be invoked. NOTE 7.9 Specification functions are nonintrinsic functions that may be used in specification expressions to determine the attributes of data objects. The requirement that they be pure ensures that they cannot have side effects that could affect other objects being declared in the same specification-part. The requirement that they not be internal ensures that they cannot inquire, via host association, about other objects being declared in the same specification-part. The prohibition against recursion avoids the creation of a new instance of a procedure while construction of one is in progress. 9A variable in a specification expression shall have its type and type parameters, if any, specified by a 10previous declaration in the same scoping unit, by the implicit typing rules in effect for the scoping unit, 11or by host or use association. If a variable in a specification expression is typed by the implicit typing 12rules, its appearance in any subsequent type declaration statement shall confirm the implied type and 13type parameters. 14If a specification expression includes a specification inquiry that depends on a type parameter or an 15array bound of an entity specified in the same specification-part, the type parameter or array bound 16shall be specified in a prior specification of the specification-part. The prior specification may be to the 17left of the specification inquiry in the same statement, but shall not be within the same entity-decl. If a 18specification expression includes a reference to the value of an element of an array specified in the same 19specification-part, the array shall be completely specified in prior declarations. NOTE 7.10 The following are examples of specification expressions: LBOUND (B, 1) + 5 ! B is an assumed-shape dummy array M + LEN (C) ! M and C are dummy arguments 2 * PRECISION (A) ! A is a real variable made accessible ! by a USE statement 207.1.7 Initialization expression 21An initialization expression is an expression with limitations that make it suitable for use as a kind 22type parameter, initializer, or named constant. It is an expression in which each operation is intrinsic, 23and each primary is 24 (1) A constant or subobject of a constant, 25 (2) An array constructor where each element and each scalar-int-expr of each ac-implied-do- 26 control is an initialization expression, 27 (3) A structure constructor where each component-spec corresponding to an allocatable com- 28 ponent is a reference to the transformational intrinsic function NULL, and each other 29 component-spec is an initialization expression, 30 (4) A reference to an elemental standard intrinsic function, where each argument is an initial- 126 MAY 2004 WORKING DRAFT J3/04-007 1 ization expression, 2 (5) A reference to a transformational standard intrinsic function other than NULL, where each 3 argument is an initialization expression, 4 (6) A reference to the transformational intrinsic function NULL that does not have an argu- 5 ment with a type parameter that is assumed or is defined by an expression that is not an 6 initialization expression, 7 (7) A reference to the transformational function IEEE SELECTED REAL KIND from the in- 8 trinsic module IEEE ARITHMETIC (14), where each argument is an initialization expres- 9 sion. 10 (8) A specification inquiry where each designator or function argument is 11 (a) an initialization expression or 12 (b) a variable whose properties inquired about are not 13 (i) assumed, 14 (ii) deferred, or 15 (iii) defined by an expression that is not an initialization expression, 16 (9) A kind type parameter of the derived type being defined, 17 (10) An ac-do-variable within an array constructor where each scalar-int-expr of the correspond- 18 ing ac-implied-do-control is an initialization expression, or 19 (11) An initialization expression enclosed in parentheses, 20and where each subscript, section subscript, substring starting point, substring ending point, and type 21parameter value is an initialization expression. 22R730 initialization-expr is expr 23C711 (R730) initialization-expr shall be an initialization expression. 24R731 char-initialization-expr is char-expr 25C712 (R731) char-initialization-expr shall be an initialization expression. 26R732 int-initialization-expr is int-expr 27C713 (R732) int-initialization-expr shall be an initialization expression. 28R733 logical-initialization-expr is logical-expr 29C714 (R733) logical-initialization-expr shall be an initialization expression. 30If an initialization expression includes a specification inquiry that depends on a type parameter or an 31array bound of an entity specified in the same specification-part, the type parameter or array bound 32shall be specified in a prior specification of the specification-part. The prior specification may be to the 33left of the specification inquiry in the same statement, but shall not be within the same entity-decl. NOTE 7.11 The following are examples of initialization expressions: 3 -3 + 4 'AB' 'AB' // 'CD' ('AB' // 'CD') // 'EF' SIZE (A) DIGITS (X) + 4 127 J3/04-007 WORKING DRAFT MAY 2004 NOTE 7.11 (cont.) 4.0 * atan(1.0) ceiling(number_of_decimal_digits / log10(radix(0.0))) where A is an explicit-shaped array with constant bounds and X is of type default real. 17.1.8 Evaluation of operations 2An intrinsic operation requires the values of its operands. 3The execution of any numeric operation whose result is not defined by the arithmetic used by the 4processor is prohibited. Raising a negative-valued primary of type real to a real power is prohibited. 5The evaluation of a function reference shall neither affect nor be affected by the evaluation of any other 6entity within the statement. If a function reference causes definition or undefinition of an actual argument 7of the function, that argument or any associated entities shall not appear elsewhere in the same statement. 8However, execution of a function reference in the logical expression in an IF statement (8.1.2.4), the mask 9expression in a WHERE statement (7.4.3.1), or the subscripts and strides in a FORALL statement (7.4.4) 10is permitted to define variables in the statement that is conditionally executed. NOTE 7.12 For example, the statements A (I) = F (I) Y = G (X) + X are prohibited if the reference to F defines or undefines I or the reference to G defines or undefines X. However, in the statements IF (F (X)) A = X WHERE (G (X)) B = X F or G may define X. 11The declared type of an expression in which a function reference appears does not affect, and is not 12affected by, the evaluation of the actual arguments of the function. 13Execution of an array element reference requires the evaluation of its subscripts. The type of an expres- 14sion in which the array element reference appears does not affect, and is not affected by, the evaluation 15of its subscripts. Execution of an array section reference requires the evaluation of its section subscripts. 16The type of an expression in which an array section appears does not affect, and is not affected by, the 17evaluation of the array section subscripts. Execution of a substring reference requires the evaluation of 18its substring expressions. The type of an expression in which a substring appears does not affect, and 19is not affected by, the evaluation of the substring expressions. It is not necessary for a processor to 20evaluate any subscript expressions or substring expressions for an array of zero size or a character entity 21of zero length. 22The appearance of an array constructor requires the evaluation of each scalar-int-expr of the ac-implied- 23do-control in any ac-implied-do it may contain. The type of an expression in which an array constructor 24appears does not affect, and is not affected by, the evaluation of such bounds and stride expressions. 25When an elemental binary operation is applied to a scalar and an array or to two arrays of the same 128 MAY 2004 WORKING DRAFT J3/04-007 1shape, the operation is performed element-by-element on corresponding array elements of the array 2operands. The processor may perform the element-by-element operations in any order. NOTE 7.13 For example, the array expression A + B produces an array of the same shape as A and B. The individual array elements of the result have the values of the first element of A added to the first element of B, the second element of A added to the second element of B, etc. 3When an elemental unary operator operates on an array operand, the operation is performed element- 4by-element, in any order, and the result is the same shape as the operand. 57.1.8.1 Evaluation of operands 6It is not necessary for a processor to evaluate all of the operands of an expression, or to evaluate entirely 7each operand, if the value of the expression can be determined otherwise. NOTE 7.14 This principle is most often applicable to logical expressions, zero-sized arrays, and zero-length strings, but it applies to all expressions. For example, in evaluating the expression X > Y .OR. L (Z) where X, Y, and Z are real and L is a function of type logical, the function reference L (Z) need not be evaluated if X is greater than Y. Similarly, in the array expression W (Z) + A where A is of size zero and W is a function, the function reference W (Z) need not be evaluated. 8If a statement contains a function reference in a part of an expression that need not be evaluated, all 9entities that would have become defined in the execution of that reference become undefined at the 10completion of evaluation of the expression containing the function reference. NOTE 7.15 In the examples in Note 7.14, if L or W defines its argument, evaluation of the expressions under the specified conditions causes Z to become undefined, no matter whether or not L(Z) or W(Z) is evaluated. 117.1.8.2 Integrity of parentheses 12The sections that follow state certain conditions under which a processor may evaluate an expression that 13is different from the one specified by applying the rules given in 7.1.1 and 7.2. However, any expression 14in parentheses shall be treated as a data entity. NOTE 7.16 For example, in evaluating the expression A + (B ­ C) where A, B, and C are of numeric types, the difference of B and C shall be evaluated before the addition operation is performed; the processor 129 J3/04-007 WORKING DRAFT MAY 2004 NOTE 7.16 (cont.) shall not evaluate the mathematically equivalent expression (A + B) ­ C. 17.1.8.3 Evaluation of numeric intrinsic operations 2The rules given in 7.2.1 specify the interpretation of a numeric intrinsic operation. Once the interpreta- 3tion has been established in accordance with those rules, the processor may evaluate any mathematically 4equivalent expression, provided that the integrity of parentheses is not violated. 5Two expressions of a numeric type are mathematically equivalent if, for all possible values of their 6primaries, their mathematical values are equal. However, mathematically equivalent expressions of 7numeric type may produce different computational results. NOTE 7.17 Any difference between the values of the expressions (1./3.)*3. and 1. is a computational difference, not a mathematical difference. The difference between the values of the expressions 5/2 and 5./2. is a mathematical difference, not a computational difference. The mathematical definition of integer division is given in 7.2.1.1. NOTE 7.18 The following are examples of expressions with allowable alternative forms that may be used by the processor in the evaluation of those expressions. A, B, and C represent arbitrary real or complex operands; I and J represent arbitrary integer operands; and X, Y, and Z represent arbitrary operands of numeric type. Expression Allowable alternative form X + Y Y + X X * Y Y * X -X + Y Y - X X + Y + Z X + (Y + Z) X - Y + Z X - (Y - Z) X * A / Z X * (A / Z) X * Y - X * Z X * (Y - Z) A / B / C A / (B * C) A / 5.0 0.2 * A The following are examples of expressions with forbidden alternative forms that shall not be used by a processor in the evaluation of those expressions. Expression Forbidden alternative form I / 2 0.5 * I X * I / J X * (I / J) I / J / A I / (J * A) (X + Y) + Z X + (Y + Z) (X * Y) - (X * Z) X * (Y - Z) X * (Y - Z) X * Y - X * Z 8In addition to the parentheses required to establish the desired interpretation, parentheses may be 9included to restrict the alternative forms that may be used by the processor in the actual evaluation 10of the expression. This is useful for controlling the magnitude and accuracy of intermediate values 11developed during the evaluation of an expression. 130 MAY 2004 WORKING DRAFT J3/04-007 NOTE 7.19 For example, in the expression A + (B - C) the parenthesized expression (B ­ C) shall be evaluated and then added to A. The inclusion of parentheses may change the mathematical value of an expression. For example, the two expressions A * I / J A * (I / J) may have different mathematical values if I and J are of type integer. 1Each operand in a numeric intrinsic operation has a type that may depend on the order of evaluation 2used by the processor. NOTE 7.20 For example, in the evaluation of the expression Z + R + I where Z, R, and I represent data objects of complex, real, and integer type, respectively, the type of the operand that is added to I may be either complex or real, depending on which pair of operands (Z and R, R and I, or Z and I) is added first. 37.1.8.4 Evaluation of the character intrinsic operation 4The rules given in 7.2.2 specify the interpretation of the character intrinsic operation. A processor is 5only required to evaluate as much of the character intrinsic operation as is required by the context in 6which the expression appears. NOTE 7.21 For example, the statements CHARACTER (LEN = 2) C1, C2, C3, CF C1 = C2 // CF (C3) do not require the function CF to be evaluated, because only the value of C2 is needed to determine the value of C1 because C1 and C2 both have a length of 2. 77.1.8.5 Evaluation of relational intrinsic operations 8The rules given in 7.2.3 specify the interpretation of relational intrinsic operations. Once the interpre- 9tation of an expression has been established in accordance with those rules, the processor may evaluate 10any other expression that is relationally equivalent, provided that the integrity of parentheses in any 11expression is not violated. NOTE 7.22 For example, the processor may choose to evaluate the expression 131 J3/04-007 WORKING DRAFT MAY 2004 NOTE 7.22 (cont.) I > J where I and J are integer variables, as J - I < 0 1Two relational intrinsic operations are relationally equivalent if their logical values are equal for all 2possible values of their primaries. 37.1.8.6 Evaluation of logical intrinsic operations 4The rules given in 7.2.4 specify the interpretation of logical intrinsic operations. Once the interpretation 5of an expression has been established in accordance with those rules, the processor may evaluate any 6other expression that is logically equivalent, provided that the integrity of parentheses in any expression 7is not violated. NOTE 7.23 For example, for the variables L1, L2, and L3 of type logical, the processor may choose to evaluate the expression L1 .AND. L2 .AND. L3 as L1 .AND. (L2 .AND. L3) 8Two expressions of type logical are logically equivalent if their values are equal for all possible values of 9their primaries. 107.1.8.7 Evaluation of a defined operation 11The rules given in 7.2 specify the interpretation of a defined operation. Once the interpretation of an 12expression has been established in accordance with those rules, the processor may evaluate any other 13expression that is equivalent, provided that the integrity of parentheses is not violated. 14Two expressions of derived type are equivalent if their values are equal for all possible values of their 15primaries. 167.2 Interpretation of operations 17The intrinsic operations are those defined in 7.1.2. These operations are divided into the following 18categories: numeric, character, relational, and logical. The interpretations defined in the following 19sections apply to both scalars and arrays; the interpretation for arrays is obtained by applying the 20interpretation for scalars element by element. 21The interpretation of a defined operation is provided by the function that defines the operation. The type, 22type parameters and interpretation of an expression that consists of an intrinsic or defined operation are 23independent of the type and type parameters of the context or any larger expression in which it appears. 132 MAY 2004 WORKING DRAFT J3/04-007 NOTE 7.24 For example, if X is of type real, J is of type integer, and INT is the real-to-integer intrinsic conversion function, the expression INT (X + J) is an integer expression and X + J is a real expression. 1The operators <, <=, >, >=, ==, and /= always have the same interpretations as the operators .LT., 2.LE., .GT., .GE., .EQ., and .NE., respectively. 37.2.1 Numeric intrinsic operations 4A numeric operation is used to express a numeric computation. Evaluation of a numeric operation 5produces a numeric value. The permitted data types for operands of the numeric intrinsic operations 6are specified in 7.1.2. 7The numeric operators and their interpretation in an expression are given in Table 7.2, where x1 denotes 8the operand to the left of the operator and x2 denotes the operand to the right of the operator. Table 7.2: Interpretation of the numeric intrinsic operators Operator Representing Use of operator Interpretation ** Exponentiation x1 ** x2 Raise x1 to the power x2 / Division x1 / x2 Divide x1 by x2 * Multiplication x1 * x2 Multiply x1 by x2 - Subtraction x1 - x2 Subtract x2 from x1 - Negation - x2 Negate x2 + Addition x1 + x2 Add x1 and x2 + Identity + x2 Same as x2 9The interpretation of a division operation depends on the types of the operands (7.2.1.1). 10If x1 and x2 are of type integer and x2 has a negative value, the interpretation of x1 ** x2 is the same 11as the interpretation of 1/(x1 ** ABS (x2)), which is subject to the rules of integer division (7.2.1.1). NOTE 7.25 For example, 2 ** (­3) has the value of 1/(2 ** 3), which is zero. 127.2.1.1 Integer division 13One operand of type integer may be divided by another operand of type integer. Although the math- 14ematical quotient of two integers is not necessarily an integer, Table 7.1 specifies that an expression 15involving the division operator with two operands of type integer is interpreted as an expression of type 16integer. The result of such an operation is the integer closest to the mathematical quotient and between 17zero and the mathematical quotient inclusively. NOTE 7.26 For example, the expression (­8) / 3 has the value (­2). 187.2.1.2 Complex exponentiation 19In the case of a complex value raised to a complex power, the value of the operation x1 ** x2 is the 20principal value of xx1 . 2 133 J3/04-007 WORKING DRAFT MAY 2004 17.2.2 Character intrinsic operation 2The character intrinsic operator // is used to concatenate two operands of type character with the same 3kind type parameter. Evaluation of the character intrinsic operation produces a result of type character. 4The interpretation of the character intrinsic operator // when used to form an expression is given in 5Table 7.3, where x1 denotes the operand to the left of the operator and x2 denotes the operand to the 6right of the operator. Table 7.3: Interpretation of the character intrinsic operator // Operator Representing Use of operator Interpretation // Concatenation x1 // x2 Concatenate x1 with x2 7The result of the character intrinsic operation // is a character string whose value is the value of x1 8concatenated on the right with the value of x2 and whose length is the sum of the lengths of x1 and x2. 9Parentheses used to specify the order of evaluation have no effect on the value of a character expression. NOTE 7.27 For example, the value of ('AB' // 'CDE') // 'F' is the string 'ABCDEF'. Also, the value of 'AB' // ('CDE' // 'F') is the string 'ABCDEF'. 107.2.3 Relational intrinsic operations 11A relational intrinsic operation is used to compare values of two operands using the relational intrinsic 12operators .LT., .LE., .GT., .GE., .EQ., .NE., <, <=, >, >=, ==, and /=. The permitted types for 13operands of the relational intrinsic operators are specified in 7.1.2. NOTE 7.28 As shown in Table 7.1, a relational intrinsic operator cannot be used to compare the value of an expression of a numeric type with one of type character or logical. Also, two operands of type logical cannot be compared, a complex operand may be compared with another numeric operand only when the operator is .EQ., .NE., ==, or /=, and two character operands cannot be compared unless they have the same kind type parameter value. 14Evaluation of a relational intrinsic operation produces a result of type default logical. 15The interpretation of the relational intrinsic operators is given in Table 7.4, where x1 denotes the operand 16to the left of the operator and x2 denotes the operand to the right of the operator. Table 7.4: Interpretation of the relational intrinsic operators Operator Representing Use of operator Interpretation .LT. Less than x1 .LT. x2 x1 less than x2 < Less than x1 < x2 x1 less than x2 .LE. Less than or equal to x1 .LE. x2 x1 less than or equal to x2 <= Less than or equal to x1 <= x2 x1 less than or equal to x2 .GT. Greater than x1 .GT. x2 x1 greater than x2 > Greater than x1 > x2 x1 greater than x2 .GE. Greater than or equal to x1 .GE. x2 x1 greater than or equal to x2 >= Greater than or equal to x1 >= x2 x1 greater than or equal to x2 .EQ. Equal to x1 .EQ. x2 x1 equal to x2 == Equal to x1 == x2 x1 equal to x2 .NE. Not equal to x1 .NE. x2 x1 not equal to x2 134 MAY 2004 WORKING DRAFT J3/04-007 Interpretation of the relational intrinsic operators (cont.) Operator Representing Use of operator Interpretation /= Not equal to x1 /= x2 x1 not equal to x2 1A numeric relational intrinsic operation is interpreted as having the logical value true if the values of 2the operands satisfy the relation specified by the operator. A numeric relational intrinsic operation is 3interpreted as having the logical value false if the values of the operands do not satisfy the relation 4specified by the operator. 5In the numeric relational operation 6 x1 rel-op x2 7if the types or kind type parameters of x1 and x2 differ, their values are converted to the type and kind 8type parameter of the expression x1 + x2 before evaluation. 9A character relational intrinsic operation is interpreted as having the logical value true if the values of 10the operands satisfy the relation specified by the operator. A character relational intrinsic operation 11is interpreted as having the logical value false if the values of the operands do not satisfy the relation 12specified by the operator. 13For a character relational intrinsic operation, the operands are compared one character at a time in 14order, beginning with the first character of each character operand. If the operands are of unequal 15length, the shorter operand is treated as if it were extended on the right with blanks to the length of 16the longer operand. If both x1 and x2 are of zero length, x1 is equal to x2; if every character of x1 is 17the same as the character in the corresponding position in x2, x1 is equal to x2. Otherwise, at the first 18position where the character operands differ, the character operand x1 is considered to be less than x2 19if the character value of x1 at this position precedes the value of x2 in the collating sequence (4.4.4.3); 20x1 is greater than x2 if the character value of x1 at this position follows the value of x2 in the collating 21sequence. NOTE 7.29 The collating sequence depends partially on the processor; however, the result of the use of the operators .EQ., .NE., ==, and /= does not depend on the collating sequence. For nondefault character types, the blank padding character is processor dependent. 227.2.4 Logical intrinsic operations 23A logical operation is used to express a logical computation. Evaluation of a logical operation produces 24a result of type logical. The permitted types for operands of the logical intrinsic operations are specified 25in 7.1.2. 26The logical operators and their interpretation when used to form an expression are given in Table 7.5, 27where x1 denotes the operand to the left of the operator and x2 denotes the operand to the right of the 28operator. Table 7.5: Interpretation of the logical intrinsic operators Operator Representing Use of operator Interpretation .NOT. Logical negation .NOT. x2 True if x2 is false .AND. Logical conjunction x1 .AND. x2 True if x1 and x2 are both true .OR. Logical inclusive disjunction x1 .OR. x2 True if x1 and/or x2 is true True if either x1 or x2 is true, but .NEQV. Logical nonequivalence x1 .NEQV. x2 not both 135 J3/04-007 WORKING DRAFT MAY 2004 Interpretation of the logical intrinsic operators (cont.) Operator Representing Use of operator Interpretation True if both x1 and x2 are true or .EQV. Logical equivalence x1 .EQV. x2 both are false 1The values of the logical intrinsic operations are shown in Table 7.6. Table 7.6: The values of operations involving logical intrinsic operators x1 x2 .NOT. x2 x1 .AND. x2 x1 .OR. x2 x1 .EQV. x2 x1 .NEQV. x2 true true false true true true false true false true false true false true false true false false true false true false false true false false true false 27.3 Precedence of operators 3There is a precedence among the intrinsic and extension operations corresponding to the form of expres- 4sions specified in 7.1.1, which determines the order in which the operands are combined unless the order 5is changed by the use of parentheses. This precedence order is summarized in Table 7.7. Table 7.7: Categories of operations and relative precedence Category of operation Operators Precedence Extension defined-unary-op Highest Numeric ** . Numeric * or / . Numeric unary + or ­ . Numeric binary + or ­ . Character // . Relational .EQ., .NE., .LT., .LE., .GT., .GE., ==, /=, <, <=, >, >= . Logical .NOT. . Logical .AND. . Logical .OR. . Logical .EQV. or .NEQV. . Extension defined-binary-op Lowest 6The precedence of a defined operation is that of its operator. NOTE 7.30 For example, in the expression -A ** 2 the exponentiation operator (**) has precedence over the negation operator (­); therefore, the operands of the exponentiation operator are combined to form an expression that is used as the operand of the negation operator. The interpretation of the above expression is the same as the interpretation of the expression - (A ** 2) 136 MAY 2004 WORKING DRAFT J3/04-007 1The general form of an expression (7.1.1) also establishes a precedence among operators in the same 2syntactic class. This precedence determines the order in which the operands are to be combined in 3determining the interpretation of the expression unless the order is changed by the use of parentheses. NOTE 7.31 In interpreting a level-2-expr containing two or more binary operators + or ­, each operand (add- operand) is combined from left to right. Similarly, the same left-to-right interpretation for a mult- operand in add-operand, as well as for other kinds of expressions, is a consequence of the general form. However, for interpreting a mult-operand expression when two or more exponentiation operators ** combine level-1-expr operands, each level-1-expr is combined from right to left. For example, the expressions 2.1 + 3.4 + 4.9 2.1 * 3.4 * 4.9 2.1 / 3.4 / 4.9 2 ** 3 ** 4 'AB' // 'CD' // 'EF' have the same interpretations as the expressions (2.1 + 3.4) + 4.9 (2.1 * 3.4) * 4.9 (2.1 / 3.4) / 4.9 2 ** (3 ** 4) ('AB' // 'CD') // 'EF' As a consequence of the general form (7.1.1), only the first add-operand of a level-2-expr may be preceded by the identity (+) or negation (­) operator. These formation rules do not permit expressions containing two consecutive numeric operators, such as A ** ­B or A + ­B. However, expressions such as A ** (­B) and A + (­B) are permitted. The rules do allow a binary operator or an intrinsic unary operator to be followed by a defined unary operator, such as: A * .INVERSE. B - .INVERSE. (B) As another example, in the expression A .OR. B .AND. C the general form implies a higher precedence for the .AND. operator than for the .OR. opera- tor; therefore, the interpretation of the above expression is the same as the interpretation of the expression A .OR. (B .AND. C) NOTE 7.32 An expression may contain more than one category of operator. The logical expression L .OR. A + B >= C where A, B, and C are of type real, and L is of type logical, contains a numeric operator, a relational operator, and a logical operator. This expression would be interpreted the same as the expression 137 J3/04-007 WORKING DRAFT MAY 2004 NOTE 7.32 (cont.) L .OR. ((A + B) >= C) NOTE 7.33 If (1) The operator ** is extended to type logical, (2) The operator .STARSTAR. is defined to duplicate the function of ** on type real, (3) .MINUS. is defined to duplicate the unary operator ­, and (4) L1 and L2 are type logical and X and Y are type real, then in precedence: L1 ** L2 is higher than X * Y; X * Y is higher than X .STARSTAR. Y; and .MINUS. X is higher than ­X. 17.4 Assignment 2Execution of an assignment statement causes a variable to become defined or redefined. Execution of a 3pointer assignment statement causes a pointer to become associated with a target or causes its pointer 4association status to become disassociated or undefined. Execution of a WHERE statement or WHERE 5construct masks the evaluation of expressions and assignment of values in array assignment statements 6according to the value of a logical array expression. Execution of a FORALL statement or FORALL 7construct controls the assignment to elements of arrays by using a set of index variables and a mask 8expression. 97.4.1 Assignment statement 10A variable may be defined or redefined by execution of an assignment statement. 117.4.1.1 General form 12R734 assignment-stmt is variable = expr 13C715 (R734) The variable in an assignment-stmt shall not be a whole assumed-size array. NOTE 7.34 Examples of an assignment statement are: A = 3.5 + X * Y I = INT (A) 14An assignment-stmt shall meet the requirements of either a defined assignment statement or an intrinsic 15assignment statement. 167.4.1.2 Intrinsic assignment statement 17An intrinsic assignment statement is an assignment statement that is not a defined assignment 18statement (7.4.1.4). In an intrinsic assignment statement, variable shall not be polymorphic, and 19 (1) If expr is an array then variable shall also be an array, 20 (2) Either variable shall be an allocatable array of the same rank as expr or the shapes of 21 variable and expr shall conform, and 138 MAY 2004 WORKING DRAFT J3/04-007 1 (3) The declared types of variable and expr shall conform as specified in Table 7.8. 2 Table 7.8: Type conformance for the intrinsic assignment statement Type of variable Type of expr integer integer, real, complex real integer, real, complex complex integer, real, complex ISO 10646, ASCII, or default character ISO 10646, ASCII, or default character other character character of the same kind type parameter as variable logical logical derived type same derived type and kind type parameters as variable; each length type parameter value shall be the same unless variable is allocatable and its corresponding type parame- ter is deferred 3A numeric intrinsic assignment statement is an intrinsic assignment statement for which variable 4and expr are of numeric type. A character intrinsic assignment statement is an intrinsic assign- 5ment statement for which variable and expr are of type character. A logical intrinsic assignment 6statement is an intrinsic assignment statement for which variable and expr are of type logical. A 7derived-type intrinsic assignment statement is an intrinsic assignment statement for which vari- 8able and expr are of derived type. 9An array intrinsic assignment statement is an intrinsic assignment statement for which variable is 10an array. The variable shall not be a many-one array section (6.2.2.3.2). 11If variable is a pointer, it shall be associated with a definable target such that the type, type parameters, 12and shape of the target and expr conform. 137.4.1.3 Interpretation of intrinsic assignments 14Execution of an intrinsic assignment causes, in effect, the evaluation of the expression expr and all 15expressions within variable (7.1.8), the possible conversion of expr to the type and type parameters 16of variable (Table 7.9), and the definition of variable with the resulting value. The execution of the 17assignment shall have the same effect as if the evaluation of all operations in expr and variable occurred 18before any portion of variable is defined by the assignment. The evaluation of expressions within variable 19shall neither affect nor be affected by the evaluation of expr. No value is assigned to variable if variable 20is of type character and zero length, or is an array of size zero. 21If variable is a pointer, the value of expr is assigned to the target of variable. 22If variable is an allocated allocatable variable, it is deallocated if expr is an array of different shape 23or any of the corresponding length type parameter values of variable and expr differ. If variable is or 24becomes an unallocated allocatable variable, then it is allocated with each deferred type parameter equal 25to the corresponding type parameters of expr, with the shape of expr, and with each lower bound equal 26to the corresponding element of LBOUND(expr). NOTE 7.35 For example, given the declaration CHARACTER(:),ALLOCATABLE :: NAME then after the assignment statement NAME = 'Dr. '//FIRST_NAME//' '//SURNAME 139 J3/04-007 WORKING DRAFT MAY 2004 NOTE 7.35 (cont.) NAME will have the length LEN(FIRST NAME)+LEN(SURNAME)+5, even if it had previously been unallocated, or allocated with a different length. However, for the assignment statement NAME(:) = 'Dr. '//FIRST_NAME//' '//SURNAME NAME must already be allocated at the time of the assignment; the assigned value is truncated or blank padded to the previously allocated length of NAME. 1Both variable and expr may contain references to any portion of variable. NOTE 7.36 For example, in the character intrinsic assignment statement: STRING (2:5) = STRING (1:4) the assignment of the first character of STRING to the second character does not affect the evaluation of STRING (1:4). If the value of STRING prior to the assignment was 'ABCDEF', the value following the assignment is 'AABCDF'. 2If expr is a scalar and variable is an array, the expr is treated as if it were an array of the same shape 3as variable with every element of the array equal to the scalar value of expr. 4If variable is an array, the assignment is performed element-by-element on corresponding array elements 5of variable and expr. NOTE 7.37 For example, if A and B are arrays of the same shape, the array intrinsic assignment A = B assigns the corresponding elements of B to those of A; that is, the first element of B is assigned to the first element of A, the second element of B is assigned to the second element of A, etc. If C is an allocatable array of rank 1, then C = PACK(ARRAY,ARRAY>0) will cause C to contain all the positive elements of ARRAY in array element order; if C is not allocated or is allocated with the wrong size, it will be re-allocated to be of the correct size to hold the result of PACK. 6The processor may perform the element-by-element assignment in any order. NOTE 7.38 For example, the following program segment results in the values of the elements of array X being reversed: REAL X (10) ... X (1:10) = X (10:1:-1) 140 MAY 2004 WORKING DRAFT J3/04-007 1For a numeric intrinsic assignment statement, variable and expr may have different numeric types or 2different kind type parameters, in which case the value of expr is converted to the type and kind type 3parameter of variable according to the rules of Table 7.9. Table 7.9: Numeric conversion and the assignment statement Type of variable Value Assigned integer INT (expr, KIND = KIND (variable)) real REAL (expr, KIND = KIND (variable)) complex CMPLX (expr, KIND = KIND (variable)) Note: The functions INT, REAL, CMPLX, and KIND are the generic functions defined in 13.7. 4For a logical intrinsic assignment statement, variable and expr may have different kind type parameters, 5in which case the value of expr is converted to the kind type parameter of variable. 6For a character intrinsic assignment statement, variable and expr may have different character length 7parameters in which case the conversion of expr to the length of variable is as follows: 8 (1) If the length of variable is less than that of expr, the value of expr is truncated from the 9 right until it is the same length as variable. 10 (2) If the length of variable is greater than that of expr, the value of expr is extended on the 11 right with blanks until it is the same length as variable. 12If variable and expr have different kind type parameters, each character c in expr is converted to the 13kind type parameter of variable by ACHAR(IACHAR(c),KIND(variable)). NOTE 7.39 For nondefault character types, the blank padding character is processor dependent. When assign- ing a character expression to a variable of a different kind, each character of the expression that is not representable in the kind of the variable is replaced by a processor-dependent character. 14A derived-type intrinsic assignment is performed as if each component of variable were assigned from 15the corresponding component of expr using pointer assignment (7.4.2) for each pointer component, 16defined assignment for each nonpointer nonallocatable component of a type that has a type-bound 17defined assignment consistent with the component, and intrinsic assignment for each other nonpointer 18nonallocatable component. For an allocatable component the following sequence of operations is applied: 19 (1) If the component of variable is allocated, it is deallocated. 20 (2) If the component of expr is allocated, the corresponding component of variable is allocated 21 with the same dynamic type and type parameters as the component of expr. If it is an array, 22 it is allocated with the same bounds. The value of the component of expr is then assigned 23 to the corresponding component of variable using defined assignment if the declared type 24 of the component has a type-bound defined assignment consistent with the component, and 25 intrinsic assignment for the dynamic type of that component otherwise. 26The processor may perform the component-by-component assignment in any order or by any means that 27has the same effect. NOTE 7.40 For an example of a derived-type intrinsic assignment statement, if C and D are of the same derived type with a pointer component P and nonpointer components S, T, U, and V of type integer, logical, character, and another derived type, respectively, the intrinsic C = D 141 J3/04-007 WORKING DRAFT MAY 2004 NOTE 7.40 (cont.) pointer assigns D % P to C % P. It assigns D % S to C % S, D % T to C % T, and D % U to C % U using intrinsic assignment. It assigns D % V to C % V using defined assignment if objects of that type have a compatible type-bound defined assignment, and intrinsic assignment otherwise. NOTE 7.41 If an allocatable component of expr is unallocated, the corresponding component of variable has an allocation status of unallocated after execution of the assignment. 1When variable is a subobject, the assignment does not affect the definition status or value of other parts 2of the object. For example, if variable is an array section, the assignment does not affect the definition 3status or value of the elements of the array not specified by the array section. 47.4.1.4 Defined assignment statement 5A defined assignment statement is an assignment statement that is defined by a subroutine and a 6generic interface (4.5.1, 12.3.2.1.2) that specifies ASSIGNMENT (=). A defined elemental assign- 7ment statement is a defined assignment statement for which the subroutine is elemental (12.7). 8A subroutine defines the defined assignment x1 = x2 if 9 (1) The subroutine is specified with a SUBROUTINE (12.5.2.2) or ENTRY (12.5.2.4) statement 10 that specifies two dummy arguments, d1 and d2, 11 (2) Either 12 (a) A generic interface (12.3.2.1) provides the subroutine with a generic-spec of ASSIGN- 13 MENT (=), or 14 (b) There is a generic binding (4.5.1) in the declared type of x1 or x2 with a generic-spec 15 of ASSIGNMENT (=) and there is a corresponding binding to the subroutine in the 16 dynamic type of x1 or x2, respectively, 17 (3) The types of d1 and d2 are compatible with the dynamic types of x1 and x2, respectively, 18 (4) The type parameters, if any, of d1 and d2 match the corresponding type parameters of x1 19 and x2, respectively, and 20 (5) Either 21 (a) The ranks of x1 and x2 match those of d1 and d2 or 22 (b) The subroutine is elemental, x1 and x2 are conformable, and there is no other sub- 23 routine that defines the operation. 24If d1 or d2 is an array, the shapes of x1 and x2 shall match the shapes of d1 and d2, respectively. 257.4.1.5 Interpretation of defined assignment statements 26The interpretation of a defined assignment is provided by the subroutine that defines it. 27If the defined assignment is an elemental assignment and the variable in the assignment is an array, the 28defined assignment is performed element-by-element, in any order, on corresponding elements of variable 29and expr. If expr is a scalar, it is treated as if it were an array of the same shape as variable with every 30element of the array equal to the scalar value of expr. NOTE 7.42 The rules of defined assignment (12.3.2.1.2), procedure references (12.4), subroutine references (12.4.3), and elemental subroutine arguments (12.7.3) ensure that the defined assignment has the 142 MAY 2004 WORKING DRAFT J3/04-007 NOTE 7.42 (cont.) same effect as if the evaluation of all operations in x2 and x1 occurs before any portion of x1 is defined. 17.4.2 Pointer assignment 2Pointer assignment causes a pointer to become associated with a target or causes its pointer association 3status to become disassociated or undefined. Any previous association between the pointer and a target 4is broken. 5Pointer assignment for a pointer component of a structure may also take place by execution of a derived- 6type intrinsic assignment statement (7.4.1.3). 7A pointer may also become associated with a target by allocation of the pointer. 8R735 pointer-assignment-stmt is data-pointer-object [ (bounds-spec-list) ] => data-target 9 or data-pointer-object (bounds-remapping-list ) => data-target 10 or proc-pointer-object => proc-target 11R736 data-pointer-object is variable-name 12 or variable % data-pointer-component-name 13C716 (R735) If data-target is not unlimited polymorphic, data-pointer-object shall be type compatible 14 (5.1.1.2) with it, and the corresponding kind type parameters shall be equal. 15C717 (R735) If data-target is unlimited polymorphic, data-pointer-object shall be unlimited polymor- 16 phic, of a sequence derived type, or of a type with the BIND attribute. 17C718 (R735) If bounds-spec-list is specified, the number of bounds-specs shall equal the rank of data- 18 pointer-object. 19C719 (R735) If bounds-remapping-list is specified, the number of bounds-remappings shall equal the 20 rank of data-pointer-object. 21C720 (R735) If bounds-remapping-list is specified, data-target shall have rank one; otherwise, the 22 ranks of data-pointer-object and data-target shall be the same. 23C721 (R736) A variable-name shall have the POINTER attribute. 24C722 (R736) A data-pointer-component-name shall be the name of a component of variable that is a 25 data pointer. 26R737 bounds-spec is lower-bound-expr : 27R738 bounds-remapping is lower-bound-expr : upper-bound-expr 28R739 data-target is variable 29 or expr 30C723 (R739) A variable shall have either the TARGET or POINTER attribute, and shall not be an 31 array section with a vector subscript. 32C724 (R739) An expr shall be a reference to a function whose result is a data pointer. 33R740 proc-pointer-object is proc-pointer-name 34 or proc-component-ref 35R741 proc-component-ref is variable % procedure-component-name 36C725 (R741) the procedure-component-name shall be the name of a procedure pointer component of 37 the declared type of variable. 143 J3/04-007 WORKING DRAFT MAY 2004 1R742 proc-target is expr 2 or procedure-name 3 or proc-component-ref 4C726 (R742) An expr shall be a reference to a function whose result is a procedure pointer. 5C727 (R742) A procedure-name shall be the name of an external, module, or dummy procedure, a 6 specific intrinsic function listed in 13.6 and not marked with a bullet (·), or a procedure pointer. 7C728 (R742) The proc-target shall not be a nonintrinsic elemental procedure. 87.4.2.1 Data pointer assignment 9If data-pointer-object is not polymorphic and data-target is polymorphic with dynamic type that differs 10from its declared type, the assignment target is the ancestor component of data-target that has the type 11of data-pointer-object. Otherwise, the assignment target is data-target. 12If data-target is not a pointer, data-pointer-object becomes pointer associated with the assignment target. 13Otherwise, the pointer association status of data-pointer-object becomes that of data-target; if data-target 14is associated with an object, data-pointer-object becomes associated with the assignment target. If data- 15target is allocatable, it shall be allocated. 16If data-pointer-object is polymorphic (5.1.1.2), it assumes the dynamic type of data-target. If data- 17pointer-object is of sequence derived type or a type with the BIND attribute, the dynamic type of 18data-target shall be that derived type. 19If data-target is a disassociated pointer, all nondeferred type parameters of the declared type of data- 20pointer-object that correspond to nondeferred type parameters of data-target shall have the same values 21as the corresponding type parameters of data-target. Otherwise, all nondeferred type parameters of the 22declared type of data-pointer-object shall have the same values as the corresponding type parameters of 23data-target. 24If data-pointer-object has nondeferred type parameters that correspond to deferred type parameters of 25data-target, data-target shall not be a pointer with undefined association status. 26If bounds-remapping-list is specified, data-target shall not be a disassociated or undefined pointer, and 27the size of data-target shall not be less than the size of data-pointer-object. The elements of the target 28of data-pointer-object, in array element order (6.2.2.2), are the first SIZE(data-pointer-object) elements 29of data-target. 30If no bounds-remapping-list is specified, the extent of a dimension of data-pointer-object is the extent of 31the corresponding dimension of data-target. If bounds-spec-list appears, it specifies the lower bounds; 32otherwise, the lower bound of each dimension is the result of the intrinsic function LBOUND (13.7.60) 33applied to the corresponding dimension of data-target. The upper bound of each dimension is one less 34than the sum of the lower bound and the extent. 357.4.2.2 Procedure pointer assignment 36If the proc-target is not a pointer, proc-pointer-object becomes pointer associated with proc-target. Other- 37wise, the pointer association status of proc-pointer-object becomes that of proc-target; if proc-target is 38associated with a procedure, proc-pointer-object becomes associated with the same procedure. 39If proc-pointer-object has an explicit interface, its characteristics shall be the same as proc-target except 40that proc-target may be pure even if proc-pointer-object is not pure and proc-target may be an elemental 41intrinsic procedure even if proc-pointer-object is not elemental. 42If the characteristics of proc-pointer-object or proc-target are such that an explicit interface is required, 144 MAY 2004 WORKING DRAFT J3/04-007 1both proc-pointer-object and proc-target shall have an explicit interface. 2If proc-pointer-object has an implicit interface and is explicitly typed or referenced as a function, proc- 3target shall be a function. If proc-pointer-object has an implicit interface and is referenced as a subroutine, 4proc-target shall be a subroutine. 5If proc-target and proc-pointer-object are functions, they shall have the same type; corresponding type 6parameters shall either both be deferred or both have the same value. 7If procedure-name is a specific procedure name that is also a generic name, only the specific procedure 8is associated with pointer-object. 97.4.2.3 Examples NOTE 7.43 The following are examples of pointer assignment statements. (See Note 12.14 for declarations of P and BESSEL.) NEW_NODE % LEFT => CURRENT_NODE SIMPLE_NAME => TARGET_STRUCTURE % SUBSTRUCT % COMPONENT PTR => NULL ( ) ROW => MAT2D (N, :) WINDOW => MAT2D (I-1:I+1, J-1:J+1) POINTER_OBJECT => POINTER_FUNCTION (ARG_1, ARG_2) EVERY_OTHER => VECTOR (1:N:2) WINDOW2 (0:, 0:) => MAT2D (ML:MU, NL:NU) ! P is a procedure pointer and BESSEL is a procedure with a ! compatible interface. P => BESSEL ! Likewise for a structure component. STRUCT % COMPONENT => BESSEL NOTE 7.44 It is possible to obtain high-rank views of (parts of) rank-one objects by specifying upper bounds in pointer assignment statements. Consider the following example, in which a matrix is under consideration. The matrix is stored as a rank-one object in MYDATA because its diagonal is needed for some reason ­ the diagonal cannot be gotten as a single object from a rank-two representation. The matrix is represented as a rank-two view of MYDATA. real, target :: MYDATA ( NR*NC ) ! An automatic array real, pointer :: MATRIX ( :, : ) ! A rank-two view of MYDATA real, pointer :: VIEW_DIAG ( : ) MATRIX( 1:NR, 1:NC ) => MYDATA ! The MATRIX view of the data VIEW_DIAG => MYDATA( 1::NR+1 ) ! The diagonal of MATRIX Rows, columns, or blocks of the matrix can be accessed as sections of MATRIX. 107.4.3 Masked array assignment ­ WHERE 11The masked array assignment is used to mask the evaluation of expressions and assignment of values in 12array assignment statements, according to the value of a logical array expression. 145 J3/04-007 WORKING DRAFT MAY 2004 17.4.3.1 General form of the masked array assignment 2A masked array assignment is either a WHERE statement or a WHERE construct. 3R743 where-stmt is WHERE ( mask-expr ) where-assignment-stmt 4R744 where-construct is where-construct-stmt 5 [ where-body-construct ] ... 6 [ masked-elsewhere-stmt 7 [ where-body-construct ] ... ] ... 8 [ elsewhere-stmt 9 [ where-body-construct ] ... ] 10 end-where-stmt 11R745 where-construct-stmt is [where-construct-name:] WHERE ( mask-expr ) 12R746 where-body-construct is where-assignment-stmt 13 or where-stmt 14 or where-construct 15R747 where-assignment-stmt is assignment-stmt 16R748 mask-expr is logical-expr 17R749 masked-elsewhere-stmt is ELSEWHERE (mask-expr) [where-construct-name] 18R750 elsewhere-stmt is ELSEWHERE [where-construct-name] 19R751 end-where-stmt is END WHERE [where-construct-name] 20C729 (R747) A where-assignment-stmt that is a defined assignment shall be elemental. 21C730 (R744) If the where-construct-stmt is identified by a where-construct-name, the corresponding 22 end-where-stmt shall specify the same where-construct-name. If the where-construct-stmt is 23 not identified by a where-construct-name, the corresponding end-where-stmt shall not specify 24 a where-construct-name. If an elsewhere-stmt or a masked-elsewhere-stmt is identified by a 25 where-construct-name, the corresponding where-construct-stmt shall specify the same where- 26 construct-name. 27C731 (R746) A statement that is part of a where-body-construct shall not be a branch target statement. 28If a where-construct contains a where-stmt, a masked-elsewhere-stmt, or another where-construct then 29each mask-expr within the where-construct shall have the same shape. In each where-assignment-stmt, 30the mask-expr and the variable being defined shall be arrays of the same shape. NOTE 7.45 Examples of a masked array assignment are: WHERE (TEMP > 100.0) TEMP = TEMP - REDUCE_TEMP WHERE (PRESSURE <= 1.0) PRESSURE = PRESSURE + INC_PRESSURE TEMP = TEMP - 5.0 ELSEWHERE RAINING = .TRUE. END WHERE 317.4.3.2 Interpretation of masked array assignments 32When a WHERE statement or a where-construct-stmt is executed, a control mask is established. In 33addition, when a WHERE construct statement is executed, a pending control mask is established. If 34the statement does not appear as part of a where-body-construct, the mask-expr of the statement is 35evaluated, and the control mask is established to be the value of mask-expr. The pending control mask 36is established to have the value .NOT. mask-expr upon execution of a WHERE construct statement that 146 MAY 2004 WORKING DRAFT J3/04-007 1does not appear as part of a where-body-construct. The mask-expr is evaluated only once. 2Each statement in a WHERE construct is executed in sequence. 3Upon execution of a masked-elsewhere-stmt, the following actions take place in sequence: 4 (1) The control mask mc is established to have the value of the pending control mask. 5 (2) The pending control mask is established to have the value mc .AND. (.NOT. mask-expr). 6 (3) The control mask mc is established to have the value mc .AND. mask-expr. 7The mask-expr is evaluated at most once. 8Upon execution of an ELSEWHERE statement, the control mask is established to have the value of the 9pending control mask. No new pending control mask value is established. 10Upon execution of an ENDWHERE statement, the control mask and pending control mask are es- 11tablished to have the values they had prior to the execution of the corresponding WHERE construct 12statement. Following the execution of a WHERE statement that appears as a where-body-construct, the 13control mask is established to have the value it had prior to the execution of the WHERE statement. NOTE 7.46 The establishment of control masks and the pending control mask is illustrated with the following example: WHERE(cond1) ! Statement 1 . . . ELSEWHERE(cond2) ! Statement 2 . . . ELSEWHERE ! Statement 3 . . . END WHERE Following execution of statement 1, the control mask has the value cond1 and the pending control mask has the value .NOT. cond1. Following execution of statement 2, the control mask has the value (.NOT. cond1) .AND. cond2 and the pending control mask has the value (.NOT. cond1) .AND. (.NOT. cond2). Following execution of statement 3, the control mask has the value (.NOT. cond1) .AND. (.NOT. cond2). The false condition values are propagated through the execution of the masked ELSEWHERE statement. 14Upon execution of a WHERE construct statement that is part of a where-body-construct, the pending 15control mask is established to have the value mc .AND. (.NOT. mask-expr). The control mask is then 16established to have the value mc .AND. mask-expr. The mask-expr is evaluated at most once. 17Upon execution of a WHERE statement that is part of a where-body-construct, the control mask is 18established to have the value mc .AND. mask-expr. The pending mask is not altered. 19If a nonelemental function reference occurs in the expr or variable of a where-assignment-stmt or in a 20mask-expr, the function is evaluated without any masked control; that is, all of its argument expressions 21are fully evaluated and the function is fully evaluated. If the result is an array and the reference is not 22within the argument list of a nonelemental function, elements corresponding to true values in the control 23mask are selected for use in evaluating the expr, variable or mask-expr. 24If an elemental operation or function reference occurs in the expr or variable of a where-assignment-stmt 25or in a mask-expr, and is not within the argument list of a nonelemental function reference, the operation 26is performed or the function is evaluated only for the elements corresponding to true values of the control 27mask. 147 J3/04-007 WORKING DRAFT MAY 2004 1If an array constructor appears in a where-assignment-stmt or in a mask-expr, the array constructor is 2evaluated without any masked control and then the where-assignment-stmt is executed or the mask-expr 3is evaluated. 4When a where-assignment-stmt is executed, the values of expr that correspond to true values of the 5control mask are assigned to the corresponding elements of variable. 6The value of the control mask is established by the execution of a WHERE statement, a WHERE con- 7struct statement, an ELSEWHERE statement, a masked ELSEWHERE statement, or an ENDWHERE 8statement. Subsequent changes to the value of entities in a mask-expr have no effect on the value of the 9control mask. The execution of a function reference in the mask expression of a WHERE statement is 10permitted to affect entities in the assignment statement. NOTE 7.47 Examples of function references in masked array assignments are: WHERE (A > 0.0) A = LOG (A) ! LOG is invoked only for positive elements. A = A / SUM (LOG (A)) ! LOG is invoked for all elements ! because SUM is transformational. END WHERE 117.4.4 FORALL 12FORALL constructs and statements are used to control the execution of assignment and pointer assign- 13ment statements with selection by sets of index values and an optional mask expression. 147.4.4.1 The FORALL Construct 15The FORALL construct allows multiple assignments, masked array (WHERE) assignments, and nested 16FORALL constructs and statements to be controlled by a single forall-triplet-spec-list and scalar-mask- 17expr. 18R752 forall-construct is forall-construct-stmt 19 [forall-body-construct ] ... 20 end-forall-stmt 21R753 forall-construct-stmt is [forall-construct-name :] FORALL forall-header 22R754 forall-header is (forall-triplet-spec-list [, scalar-mask-expr] ) 23R755 forall-triplet-spec is index-name = subscript : subscript [ : stride] 24R618 subscript is scalar-int-expr 25R621 stride is scalar-int-expr 26R756 forall-body-construct is forall-assignment-stmt 27 or where-stmt 28 or where-construct 29 or forall-construct 30 or forall-stmt 31R757 forall-assignment-stmt is assignment-stmt 32 or pointer-assignment-stmt 33R758 end-forall-stmt is END FORALL [forall-construct-name ] 34C732 (R758) If the forall-construct-stmt has a forall-construct-name, the end-forall-stmt shall have 35 the same forall-construct-name. If the end-forall-stmt has a forall-construct-name, the forall- 148 MAY 2004 WORKING DRAFT J3/04-007 1 construct-stmt shall have the same forall-construct-name. 2C733 (R754) The scalar-mask-expr shall be scalar and of type logical. 3C734 (R754) Any procedure referenced in the scalar-mask-expr, including one referenced by a defined 4 operation, shall be a pure procedure (12.6). 5C735 (R755) The index-name shall be a named scalar variable of type integer. 6C736 (R755) A subscript or stride in a forall-triplet-spec shall not contain a reference to any index- 7 name in the forall-triplet-spec-list in which it appears. 8C737 (R756) A statement in a forall-body-construct shall not define an index-name of the forall- 9 construct. 10C738 (R756) Any procedure referenced in a forall-body-construct, including one referenced by a defined 11 operation, assignment, or finalization, shall be a pure procedure. 12C739 (R756) A forall-body-construct shall not be a branch target. NOTE 7.48 An example of a FORALL construct is: REAL :: A(10, 10), B(10, 10) = 1.0 . . . FORALL (I = 1:10, J = 1:10, B(I, J) /= 0.0) A(I, J) = REAL (I + J - 2) B(I, J) = A(I, J) + B(I, J) * REAL (I * J) END FORALL NOTE 7.49 An assignment statement that is a FORALL body construct may be a scalar or array assignment statement, or a defined assignment statement. The variable being defined will normally use each index name in the forall-triplet-spec-list. For example FORALL (I = 1:N, J = 1:N) A(:, I, :, J) = 1.0 / REAL(I + J - 1) END FORALL broadcasts scalar values to rank-two subarrays of A. NOTE 7.50 An example of a FORALL construct containing a pointer assignment statement is: TYPE ELEMENT REAL ELEMENT_WT CHARACTER (32), POINTER :: NAME END TYPE ELEMENT TYPE(ELEMENT) CHART(200) REAL WEIGHTS (1000) CHARACTER (32), TARGET :: NAMES (1000) . . . FORALL (I = 1:200, WEIGHTS (I + N - 1) > .5) CHART(I) % ELEMENT_WT = WEIGHTS (I + N - 1) 149 J3/04-007 WORKING DRAFT MAY 2004 NOTE 7.50 (cont.) CHART(I) % NAME => NAMES (I + N - 1) END FORALL The results of this FORALL construct cannot be achieved with a WHERE construct because a pointer assignment statement is not permitted in a WHERE construct. 1An index-name in a forall-construct has a scope of the construct (16.3). It is a scalar variable that has 2the type and type parameters that it would have if it were the name of a variable in the scoping unit 3that includes the FORALL, and this type shall be integer type; it has no other attributes. NOTE 7.51 The use of index-name variables in a FORALL construct does not affect variables of the same name, for example: INTEGER :: X = -1 REAL A(5, 4) J = 100 . . . FORALL (X = 1:5, J = 1:4) A (X, J) = J END FORALL After execution of the FORALL, the variables X and J have the values -1 and 100 and A has the value 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 47.4.4.2 Execution of the FORALL construct 5There are three stages in the execution of a FORALL construct: 6 (1) Determination of the values for index-name variables, 7 (2) Evaluation of the scalar-mask-expr, and 8 (3) Execution of the FORALL body constructs. 97.4.4.2.1 Determination of the values for index variables 10The subscript and stride expressions in the forall-triplet-spec-list are evaluated. These expressions may 11be evaluated in any order. The set of values that a particular index-name variable assumes is determined 12as follows: 13 (1) The lower bound m1, the upper bound m2, and the stride m3 are of type integer with the 14 same kind type parameter as the index-name. Their values are established by evaluating 15 the first subscript, the second subscript, and the stride expressions, respectively, including, 16 if necessary, conversion to the kind type parameter of the index-name according to the rules 17 for numeric conversion (Table 7.9). If a stride does not appear, m3 has the value 1. The 18 value m3 shall not be zero. 19 (2) Let the value of max be (m2-m1+m3)/m3. If max 0 for some index-name, the execution 150 MAY 2004 WORKING DRAFT J3/04-007 1 of the construct is complete. Otherwise, the set of values for the index-name is 2 m1 + (k - 1) × m3 where k = 1, 2, ..., max. 3The set of combinations of index-name values is the Cartesian product of the sets defined by each triplet 4specification. An index-name becomes defined when this set is evaluated. NOTE 7.52 The stride may be positive or negative; the FORALL body constructs are executed as long as max > 0. For the forall-triplet-spec I = 10:1:-1 max has the value 10 57.4.4.2.2 Evaluation of the mask expression 6The scalar-mask-expr, if any, is evaluated for each combination of index-name values. If the scalar- 7mask-expr is not present, it is as if it were present with the value true. The index-name variables may 8be primaries in the scalar-mask-expr. 9The active combination of index-name values is defined to be the subset of all possible combinations 10(7.4.4.2.1) for which the scalar-mask-expr has the value true. NOTE 7.53 The index-name variables may appear in the mask, for example FORALL (I=1:10, J=1:10, A(I) > 0.0 .AND. B(J) < 1.0) . . . 117.4.4.2.3 Execution of the FORALL body constructs 12The forall-body-constructs are executed in the order in which they appear. Each construct is executed 13for all active combinations of the index-name values with the following interpretation: 14Execution of a forall-assignment-stmt that is an assignment-stmt causes the evaluation of expr and all 15expressions within variable for all active combinations of index-name values. These evaluations may be 16done in any order. After all these evaluations have been performed, each expr value is assigned to the 17corresponding variable. The assignments may occur in any order. 18Execution of a forall-assignment-stmt that is a pointer-assignment-stmt causes the evaluation of all 19expressions within data-target and data-pointer-object or proc-target and proc-pointer-object, the de- 20termination of any pointers within data-pointer-object or proc-pointer-object, and the determination of 21the target for all active combinations of index-name values. These evaluations may be done in any 22order. After all these evaluations have been performed, each data-pointer-object or proc-pointer-object 23is associated with the corresponding target. These associations may occur in any order. 24In a forall-assignment-stmt, a defined assignment subroutine shall not reference any variable that be- 25comes defined by the statement. NOTE 7.54 The following FORALL construct contains two assignment statements. The assignment to array B uses the values of array A computed in the previous statement, not the values A had prior to execution of the FORALL. 151 J3/04-007 WORKING DRAFT MAY 2004 NOTE 7.54 (cont.) FORALL (I = 2:N-1, J = 2:N-1 ) A (I, J) = A(I, J-1) + A(I, J+1) + A(I-1, J) + A(I+1, J) B (I, J) = 1.0 / A(I, J) END FORALL Computations that would otherwise cause error conditions can be avoided by using an appropriate scalar-mask-expr that limits the active combinations of the index-name values. For example: FORALL (I = 1:N, Y(I) /= 0.0) X(I) = 1.0 / Y(I) END FORALL 1Each statement in a where-construct (7.4.3) within a forall-construct is executed in sequence. When 2a where-stmt, where-construct-stmt or masked-elsewhere-stmt is executed, the statement's mask-expr is 3evaluated for all active combinations of index-name values as determined by the outer forall-constructs, 4masked by any control mask corresponding to outer where-constructs. Any where-assignment-stmt is 5executed for all active combinations of index-name values, masked by the control mask in effect for the 6where-assignment-stmt. NOTE 7.55 This FORALL construct contains a WHERE statement and an assignment statement. INTEGER A(5,4), B(5,4) FORALL ( I = 1:5 ) WHERE ( A(I,:) == 0 ) A(I,:) = I B (I,:) = I / A(I,:) END FORALL When executed with the input array 0 0 0 0 1 1 1 0 A = 2 2 0 2 1 0 2 3 0 0 0 0 the results will be 1 1 1 1 1 1 1 1 1 1 1 2 2 2 2 1 A = 2 2 3 2 B = 1 1 1 1 1 4 2 3 4 1 2 1 5 5 5 5 1 1 1 1 For an example of a FORALL construct containing a WHERE construct with an ELSEWHERE statement, see C.4.5. 7Execution of a forall-stmt or forall-construct causes the evaluation of the subscript and stride expressions 8in the forall-triplet-spec-list for all active combinations of the index-name values of the outer FORALL 9construct. The set of combinations of index-name values for the inner FORALL is the union of the sets 10defined by these bounds and strides for each active combination of the outer index-name values; it also 152 MAY 2004 WORKING DRAFT J3/04-007 1includes the outer index-name values. The scalar-mask-expr is then evaluated for all combinations of the 2index-name values of the inner construct to produce a set of active combinations for the inner construct. 3If there is no scalar-mask-expr, it is as if it were present with the value .TRUE.. Each statement in the 4inner FORALL is then executed for each active combination of the index-name values. NOTE 7.56 This FORALL construct contains a nested FORALL construct. It assigns the transpose of the strict lower triangle of array A (the section below the main diagonal) to the strict upper triangle of A. INTEGER A (3, 3) FORALL (I = 1:N-1 ) FORALL ( J=I+1:N ) A(I,J) = A(J,I) END FORALL END FORALL If prior to execution N = 3 and 0 3 6 A = 1 4 7 2 5 8 then after execution 0 1 2 A = 1 4 5 2 5 8 57.4.4.3 The FORALL statement 6The FORALL statement allows a single assignment statement or pointer assignment to be controlled by 7a set of index values and an optional mask expression. 8R759 forall-stmt is FORALL forall-header forall-assignment-stmt 9A FORALL statement is equivalent to a FORALL construct containing a single forall-body-construct 10that is a forall-assignment-stmt. 11The scope of an index-name in a forall-stmt is the statement itself (16.3). NOTE 7.57 Examples of FORALL statements are: FORALL (I=1:N) A(I,I) = X(I) This statement assigns the elements of vector X to the elements of the main diagonal of matrix A. FORALL (I = 1:N, J = 1:N) X(I,J) = 1.0 / REAL (I+J-1) Array element X(I,J) is assigned the value (1.0 / REAL (I+J-1)) for values of I and J between 1 and N, inclusive. 153 J3/04-007 WORKING DRAFT MAY 2004 NOTE 7.57 (cont.) FORALL (I=1:N, J=1:N, Y(I,J) /= 0 .AND. I /= J) X(I,J) = 1.0 / Y(I,J) This statement takes the reciprocal of each nonzero off-diagonal element of array Y(1:N, 1:N) and assigns it to the corresponding element of array X. Elements of Y that are zero or on the diagonal do not participate, and no assignments are made to the corresponding elements of X. The results from the execution of the example in Note 7.56 could be obtained with a single FORALL statement: FORALL ( I = 1:N-1, J=1:N, J > I ) A(I,J) = A(J,I) For more examples of FORALL statements, see C.4.6. 17.4.4.4 Restrictions on FORALL constructs and statements 2A many-to-one assignment is more than one assignment to the same object, or association of more 3than one target with the same pointer, whether the object is referenced directly or indirectly through a 4pointer. A many-to-one assignment shall not occur within a single statement in a FORALL construct or 5statement. It is possible to assign or pointer assign to the same object in different assignment statements 6in a FORALL construct. NOTE 7.58 The appearance of each index-name in the identification of the left-hand side of an assignment statement is helpful in eliminating many-to-one assignments, but it is not sufficient to guarantee there will be none. For example, the following is allowed FORALL (I = 1:10) A (INDEX (I)) = B(I) END FORALL if and only if INDEX(1:10) contains no repeated values. 7Within the scope of a FORALL construct, a nested FORALL statement or FORALL construct shall 8not have the same index-name. The forall-header expressions within a nested FORALL may depend on 9the values of outer index-name variables. 154 MAY 2004 WORKING DRAFT J3/04-007 1 Section 8: Execution control 2 The execution sequence may be controlled by constructs containing blocks and by certain executable 3 statements that are used to alter the execution sequence. 4 8.1 Executable constructs containing blocks 5 The following are executable constructs that contain blocks: 6 (1) ASSOCIATE construct 7 (2) CASE construct 8 (3) DO construct 9 (4) IF construct 10 (5) SELECT TYPE construct 11 There is also a nonblock form of the DO construct. 12 A block is a sequence of executable constructs that is treated as a unit. 13 R801 block is [ execution-part-construct ] ... 14 Executable constructs may be used to control which blocks of a program are executed or how many times 15 a block is executed. Blocks are always bounded by statements that are particular to the construct in 16 which they are embedded; however, in some forms of the DO construct, a sequence of executable constructs without 17 a terminating boundary statement shall obey all other rules governing blocks (8.1.1). NOTE 8.1 A block need not contain any executable constructs. Execution of such a block has no effect. 18Any of these constructs may be named. If a construct is named, the name shall be the first lexical token 19of the first statement of the construct and the last lexical token of the construct. In fixed source form, the 20 name preceding the construct shall be placed after character position 6. 21A statement belongs to the innermost construct in which it appears unless it contains a construct name, 22in which case it belongs to the named construct. NOTE 8.2 An example of a construct containing a block is: IF (A > 0.0) THEN B = SQRT (A) ! These two statements C = LOG (A) ! form a block. END IF 238.1.1 Rules governing blocks 248.1.1.1 Executable constructs in blocks 25If a block contains an executable construct, the executable construct shall be entirely within the block. 155 J3/04-007 WORKING DRAFT MAY 2004 18.1.1.2 Control flow in blocks 2Transfer of control to the interior of a block from outside the block is prohibited. Transfers within a 3block and transfers from the interior of a block to outside the block may occur. 4Subroutine and function references (12.4.2, 12.4.3) may appear in a block. 58.1.1.3 Execution of a block 6Execution of a block begins with the execution of the first executable construct in the block. Execution 7of the block is completed when the last executable construct in the sequence is executed or when a 8branch out of the block takes place. NOTE 8.3 The action that takes place at the terminal boundary depends on the particular construct and on the block within that construct. It is usually a transfer of control. 98.1.2 IF construct 10The IF construct selects for execution at most one of its constituent blocks. The selection is based 11on a sequence of logical expressions. The IF statement controls the execution of a single statement 12(8.1.2.4) based on a single logical expression. 138.1.2.1 Form of the IF construct 14R802 if-construct is if-then-stmt 15 block 16 [ else-if-stmt 17 block ] ... 18 [ else-stmt 19 block ] 20 end-if-stmt 21R803 if-then-stmt is [ if-construct-name : ] IF ( scalar-logical-expr ) THEN 22R804 else-if-stmt is ELSE IF ( scalar-logical-expr ) THEN [ if-construct-name ] 23R805 else-stmt is ELSE [ if-construct-name ] 24R806 end-if-stmt is END IF [ if-construct-name ] 25C801 (R802) If the if-then-stmt of an if-construct specifies an if-construct-name, the corresponding 26 end-if-stmt shall specify the same if-construct-name. If the if-then-stmt of an if-construct does 27 not specify an if-construct-name, the corresponding end-if-stmt shall not specify an if-construct- 28 name. If an else-if-stmt or else-stmt specifies an if-construct-name, the corresponding if-then- 29 stmt shall specify the same if-construct-name. 308.1.2.2 Execution of an IF construct 31At most one of the blocks in the IF construct is executed. If there is an ELSE statement in the construct, 32exactly one of the blocks in the construct is executed. The scalar logical expressions are evaluated in 33the order of their appearance in the construct until a true value is found or an ELSE statement or END 34IF statement is encountered. If a true value or an ELSE statement is found, the block immediately 35following is executed and this completes the execution of the construct. The scalar logical expressions 36in any remaining ELSE IF statements of the IF construct are not evaluated. If none of the evaluated 37expressions is true and there is no ELSE statement, the execution of the construct is completed without 38the execution of any block within the construct. 39An ELSE IF statement or an ELSE statement shall not be a branch target statement. It is permissible 156 MAY 2004 WORKING DRAFT J3/04-007 1to branch to an END IF statement only from within its IF construct. Execution of an END IF statement 2has no effect. 38.1.2.3 Examples of IF constructs NOTE 8.4 IF (CVAR == 'RESET') THEN I = 0; J = 0; K = 0 END IF PROOF_DONE: IF (PROP) THEN WRITE (3, '(''QED'')') STOP ELSE PROP = NEXTPROP END IF PROOF_DONE IF (A > 0) THEN B = C/A IF (B > 0) THEN D = 1.0 END IF ELSE IF (C > 0) THEN B = A/C D = -1.0 ELSE B = ABS (MAX (A, C)) D = 0 END IF 48.1.2.4 IF statement 5The IF statement controls a single action statement (R214). 6R807 if-stmt is IF ( scalar-logical-expr ) action-stmt 7C802 (R807) The action-stmt in the if-stmt shall not be an if-stmt, end-program-stmt, end-function- 8 stmt, or end-subroutine-stmt. 9Execution of an IF statement causes evaluation of the scalar logical expression. If the value of the 10expression is true, the action statement is executed. If the value is false, the action statement is not 11executed and execution continues. 12The execution of a function reference in the scalar logical expression may affect entities in the action 13statement. NOTE 8.5 An example of an IF statement is: IF (A > 0.0) A = LOG (A) 157 J3/04-007 WORKING DRAFT MAY 2004 18.1.3 CASE construct 2The CASE construct selects for execution at most one of its constituent blocks. The selection is 3based on the value of an expression. 48.1.3.1 Form of the CASE construct 5R808 case-construct is select-case-stmt 6 [ case-stmt 7 block ] ... 8 end-select-stmt 9R809 select-case-stmt is [ case-construct-name : ] SELECT CASE ( case-expr ) 10R810 case-stmt is CASE case-selector [case-construct-name] 11R811 end-select-stmt is END SELECT [ case-construct-name ] 12C803 (R808) If the select-case-stmt of a case-construct specifies a case-construct-name, the corre- 13 sponding end-select-stmt shall specify the same case-construct-name. If the select-case-stmt 14 of a case-construct does not specify a case-construct-name, the corresponding end-select-stmt 15 shall not specify a case-construct-name. If a case-stmt specifies a case-construct-name, the 16 corresponding select-case-stmt shall specify the same case-construct-name. 17R812 case-expr is scalar-int-expr 18 or scalar-char-expr 19 or scalar-logical-expr 20R813 case-selector is ( case-value-range-list ) 21 or DEFAULT 22C804 (R808) No more than one of the selectors of one of the CASE statements shall be DEFAULT. 23R814 case-value-range is case-value 24 or case-value : 25 or : case-value 26 or case-value : case-value 27R815 case-value is scalar-int-initialization-expr 28 or scalar-char-initialization-expr 29 or scalar-logical-initialization-expr 30C805 (R808) For a given case-construct, each case-value shall be of the same type as case-expr. For 31 character type, the kind type parameters shall be the same; character length differences are 32 allowed. 33C806 (R808) A case-value-range using a colon shall not be used if case-expr is of type logical. 34C807 (R808) For a given case-construct, the case-value-ranges shall not overlap; that is, there shall 35 be no possible value of the case-expr that matches more than one case-value-range. 368.1.3.2 Execution of a CASE construct 37The execution of the SELECT CASE statement causes the case expression to be evaluated. The resulting 38value is called the case index. For a case value range list, a match occurs if the case index matches any 39of the case value ranges in the list. For a case index with a value of c, a match is determined as follows: 40 (1) If the case value range contains a single value v without a colon, a match occurs for type 41 logical if the expression c .EQV. v is true, and a match occurs for type integer or character 42 if the expression c == v is true. 43 (2) If the case value range is of the form low : high, a match occurs if the expression low <= c 44 .AND. c <= high is true. 158 MAY 2004 WORKING DRAFT J3/04-007 1 (3) If the case value range is of the form low :, a match occurs if the expression low <= c is true. 2 (4) If the case value range is of the form : high, a match occurs if the expression c <= high is 3 true. 4 (5) If no other selector matches and a DEFAULT selector appears, it matches the case index. 5 (6) If no other selector matches and the DEFAULT selector does not appear, there is no match. 6The block following the CASE statement containing the matching selector, if any, is executed. This 7completes execution of the construct. 8At most one of the blocks of a CASE construct is executed. 9A CASE statement shall not be a branch target statement. It is permissible to branch to an end-select- 10stmt only from within its CASE construct. 118.1.3.3 Examples of CASE constructs NOTE 8.6 An integer signum function: INTEGER FUNCTION SIGNUM (N) SELECT CASE (N) CASE (:-1) SIGNUM = -1 CASE (0) SIGNUM = 0 CASE (1:) SIGNUM = 1 END SELECT END NOTE 8.7 A code fragment to check for balanced parentheses: CHARACTER (80) :: LINE ... LEVEL = 0 SCAN_LINE: DO I = 1, 80 CHECK_PARENS: SELECT CASE (LINE (I:I)) CASE ('(') LEVEL = LEVEL + 1 CASE (')') LEVEL = LEVEL - 1 IF (LEVEL < 0) THEN PRINT *, 'UNEXPECTED RIGHT PARENTHESIS' EXIT SCAN_LINE END IF CASE DEFAULT ! Ignore all other characters END SELECT CHECK_PARENS END DO SCAN_LINE IF (LEVEL > 0) THEN PRINT *, 'MISSING RIGHT PARENTHESIS' END IF 159 J3/04-007 WORKING DRAFT MAY 2004 NOTE 8.8 The following three fragments are equivalent: IF (SILLY == 1) THEN CALL THIS ELSE CALL THAT END IF SELECT CASE (SILLY == 1) CASE (.TRUE.) CALL THIS CASE (.FALSE.) CALL THAT END SELECT SELECT CASE (SILLY) CASE DEFAULT CALL THAT CASE (1) CALL THIS END SELECT NOTE 8.9 A code fragment showing several selections of one block: SELECT CASE (N) CASE (1, 3:5, 8) ! Selects 1, 3, 4, 5, 8 CALL SUB CASE DEFAULT CALL OTHER END SELECT 18.1.4 ASSOCIATE construct 2The ASSOCIATE construct associates named entities with expressions or variables during the execution 3of its block. These named construct entities (16.3) are associating entities (16.4.1.5). The names are 4associate names. 58.1.4.1 Form of the ASSOCIATE construct 6R816 associate-construct is associate-stmt 7 block 8 end-associate-stmt 9R817 associate-stmt is [ associate-construct-name : ] ASSOCIATE 10 (association-list ) 11R818 association is associate-name => selector 12R819 selector is expr 13 or variable 14C808 (R818) If selector is not a variable or is a variable that has a vector subscript, associate-name 15 shall not appear in a variable definition context (16.5.7). 16C809 (R818) An associate-name shall not be the same as another associate-name in the same associate- 17 stmt. 160 MAY 2004 WORKING DRAFT J3/04-007 1R820 end-associate-stmt is END ASSOCIATE [ associate-construct-name ] 2C810 (R820) If the associate-stmt of an associate-construct specifies an associate-construct-name, 3 the corresponding end-associate-stmt shall specify the same associate-construct-name. If the 4 associate-stmt of an associate-construct does not specify an associate-construct-name, the cor- 5 responding end-associate-stmt shall not specify an associate-construct-name. 68.1.4.2 Execution of the ASSOCIATE construct 7Execution of an ASSOCIATE construct causes execution of its associate-stmt followed by execution 8of its block. During execution of that block each associate name identifies an entity, which is associ- 9ated (16.4.1.5) with the corresponding selector. The associating entity assumes the declared type and 10type parameters of the selector. If and only if the selector is polymorphic, the associating entity is 11polymorphic. 12The other attributes of the associating entity are described in 8.1.4.3. 13It is permissible to branch to an end-associate-stmt only from within its ASSOCIATE construct. 148.1.4.3 Attributes of associate names 15Within a SELECT TYPE or ASSOCIATE construct, each associating entity has the same rank as its 16associated selector. The lower bound of each dimension is the result of the intrinsic function LBOUND 17(13.7.60) applied to the corresponding dimension of selector. The upper bound of each dimension is one 18less than the sum of the lower bound and the extent. The associating entity has the ASYNCHRONOUS, 19TARGET, or VOLATILE attribute if and only if the selector is a variable and has the attribute. If the 20associating entity is polymorphic, it assumes the dynamic type and type parameter values of the selector. 21If the selector has the OPTIONAL attribute, it shall be present. 22If the selector (8.1.4.1) is not permitted to appear in a variable definition context (16.5.7) or is an array 23with a vector subscript, the associate name shall not appear in a variable definition context. 248.1.4.4 Examples of the ASSOCIATE construct NOTE 8.10 The following example illustrates an association with an expression. ASSOCIATE ( Z => EXP(-(X**2+Y**2)) * COS(THETA) ) PRINT *, A+Z, A-Z END ASSOCIATE The following example illustrates an association with a derived-type variable. ASSOCIATE ( XC => AX%B(I,J)%C ) XC%DV = XC%DV + PRODUCT(XC%EV(1:N)) END ASSOCIATE The following example illustrates association with an array section. ASSOCIATE ( ARRAY => AX%B(I,:)%C ) ARRAY(N)%EV = ARRAY(N-1)%EV END ASSOCIATE The following example illustrates multiple associations. 161 J3/04-007 WORKING DRAFT MAY 2004 NOTE 8.10 (cont.) ASSOCIATE ( W => RESULT(I,J)%W, ZX => AX%B(I,J)%D, ZY => AY%B(I,J)%D ) W = ZX*X + ZY*Y END ASSOCIATE 18.1.5 SELECT TYPE construct 2The SELECT TYPE construct selects for execution at most one of its constituent blocks. The selection 3is based on the dynamic type of an expression. A name is associated with the expression (16.3, 16.4.1.5), 4in the same way as for the ASSOCIATE construct. 58.1.5.1 Form of the SELECT TYPE construct 6R821 select-type-construct is select-type-stmt 7 [ type-guard-stmt 8 block ] ... 9 end-select-type-stmt 10R822 select-type-stmt is [ select-construct-name : ] SELECT TYPE 11 ( [ associate-name => ] selector ) 12C811 (R822) If selector is not a named variable, associate-name => shall appear. 13C812 (R822) If selector is not a variable or is a variable that has a vector subscript, associate-name 14 shall not appear in a variable definition context (16.5.7). 15C813 (R822) The selector in a select-type-stmt shall be polymorphic. 16R823 type-guard-stmt is TYPE IS ( type-spec ) [ select-construct-name ] 17 or CLASS IS ( type-spec ) [ select-construct-name ] 18 or CLASS DEFAULT [ select-construct-name ] 19C814 (R823) The type-spec shall specify that each length type parameter is assumed. 20C815 (R823) The type-spec shall not specify a sequence derived type or a type with the BIND attribute. 21C816 (R823) If selector is not unlimited polymorphic, the type-spec shall specify an extension of the 22 declared type of selector. 23C817 (R823) For a given select-type-construct, the same type and kind type parameter values shall 24 not be specified in more than one TYPE IS type-guard-stmt and shall not be specified in more 25 than one CLASS IS type-guard-stmt. 26C818 (R823) For a given select-type-construct, there shall be at most one CLASS DEFAULT type- 27 guard-stmt. 28R824 end-select-type-stmt is END SELECT [ select-construct-name ] 29C819 (R821) If the select-type-stmt of a select-type-construct specifies a select-construct-name, the 30 corresponding end-select-type-stmt shall specify the same select-construct-name. If the select- 31 type-stmt of a select-type-construct does not specify a select-construct-name, the corresponding 32 end-select-type-stmt shall not specify a select-construct-name. If a type-guard-stmt specifies a 33 select-construct-name, the corresponding select-type-stmt shall specify the same select-construct- 34 name. 35The associate name of a SELECT TYPE construct is the associate-name if specified; otherwise it is the 36name that constitutes the selector. 162 MAY 2004 WORKING DRAFT J3/04-007 18.1.5.2 Execution of the SELECT TYPE construct 2Execution of a SELECT TYPE construct whose selector is not a variable causes the selector expression 3to be evaluated. 4A SELECT TYPE construct selects at most one block to be executed. During execution of that block, 5the associate name identifies an entity, which is associated (16.4.1.5) with the selector. 6A TYPE IS type guard statement matches the selector if the dynamic type and type parameter values of 7the selector are the same as those specified by the statement. A CLASS IS type guard statement matches 8the selector if the dynamic type of the selector is an extension of the type specified by the statement 9and the kind type parameter values specified by the statement are the same as the corresponding type 10parameter values of the dynamic type of the selector. 11The block to be executed is selected as follows: 12 (1) If a TYPE IS type guard statement matches the selector, the block following that statement 13 is executed. 14 (2) Otherwise, if exactly one CLASS IS type guard statement matches the selector, the block 15 following that statement is executed. 16 (3) Otherwise, if several CLASS IS type guard statements match the selector, one of these 17 statements must specify a type that is an extension of all the types specified in the others; 18 the block following that statement is executed. 19 (4) Otherwise, if there is a CLASS DEFAULT type guard statement, the block following that 20 statement is executed. NOTE 8.11 This algorithm does not examine the type guard statements in source text order when it looks for a match; it selects the most particular type guard when there are several potential matches. 21Within the block following a TYPE IS type guard statement, the associating entity (16.4.5) is not 22polymorphic (5.1.1.2), has the type named in the type guard statement, and has the type parameter 23values of the selector. 24Within the block following a CLASS IS type guard statement, the associating entity is polymorphic and 25has the declared type named in the type guard statement. The type parameter values of the associating 26entity are the corresponding type parameter values of the selector. 27Within the block following a CLASS DEFAULT type guard statement, the associating entity is poly- 28morphic and has the same declared type as the selector. The type parameter values of the associating 29entity are those of the declared type of the selector. NOTE 8.12 If the declared type of the selector is T, specifying CLASS DEFAULT has the same effect as specifying CLASS IS (T). 30The other attributes of the associating entity are described in 8.1.4.3. 31A type guard statement shall not be a branch target statement. It is permissible to branch to an 32end-select-type-stmt only from within its SELECT TYPE construct. 338.1.5.3 Examples of the SELECT TYPE construct 163 J3/04-007 WORKING DRAFT MAY 2004 NOTE 8.13 TYPE POINT REAL :: X, Y END TYPE POINT TYPE, EXTENDS(POINT) :: POINT_3D REAL :: Z END TYPE POINT_3D TYPE, EXTENDS(POINT) :: COLOR_POINT INTEGER :: COLOR END TYPE COLOR_POINT TYPE(POINT), TARGET :: P TYPE(POINT_3D), TARGET :: P3 TYPE(COLOR_POINT), TARGET :: C CLASS(POINT), POINTER :: P_OR_C P_OR_C => C SELECT TYPE ( A => P_OR_C ) CLASS IS ( POINT ) ! "CLASS ( POINT ) :: A" implied here PRINT *, A%X, A%Y ! This block gets executed TYPE IS ( POINT_3D ) ! "TYPE ( POINT_3D ) :: A" implied here PRINT *, A%X, A%Y, A%Z END SELECT NOTE 8.14 The following example illustrates the omission of associate-name. It uses the declarations from Note 8.13. P_OR_C => P3 SELECT TYPE ( P_OR_C ) CLASS IS ( POINT ) ! "CLASS ( POINT ) :: P_OR_C" implied here PRINT *, P_OR_C%X, P_OR_C%Y TYPE IS ( POINT_3D ) ! "TYPE ( POINT_3D ) :: P_OR_C" implied here PRINT *, P_OR_C%X, P_OR_C%Y, P_OR_C%Z ! This block gets executed END SELECT 18.1.6 DO construct 2The DO construct specifies the repeated execution of a sequence of executable constructs. Such a 3repeated sequence is called a loop. The EXIT and CYCLE statements may be used to modify the 4execution of a loop. 5The number of iterations of a loop may be determined at the beginning of execution of the DO construct, 6or may be left indefinite ("DO forever" or DO WHILE). In either case, an EXIT statement (8.1.6.4.4) 7anywhere in the DO construct may be executed to terminate the loop immediately. The current iteration 8of the loop may be curtailed by executing a CYCLE statement (8.1.6.4.3). 164 MAY 2004 WORKING DRAFT J3/04-007 18.1.6.1 Forms of the DO construct 2The DO construct may be written in either a block form or a nonblock form. 3R825 do-construct is block-do-construct 4 or nonblock-do-construct 58.1.6.1.1 Form of the block DO construct 6R826 block-do-construct is do-stmt 7 do-block 8 end-do 9R827 do-stmt is label-do-stmt 10 or nonlabel-do-stmt 11R828 label-do-stmt is [ do-construct-name : ] DO label [ loop-control ] 12R829 nonlabel-do-stmt is [ do-construct-name : ] DO [ loop-control ] 13R830 loop-control is [ , ] do-variable = scalar-int-expr, scalar-int-expr 14 [ , scalar-int-expr ] 15 or [ , ] WHILE ( scalar-logical-expr ) 16R831 do-variable is scalar-int-variable 17C820 (R831) The do-variable shall be a named scalar variable of type integer. 18R832 do-block is block 19R833 end-do is end-do-stmt 20 or continue-stmt 21R834 end-do-stmt is END DO [ do-construct-name ] 22C821 (R826) If the do-stmt of a block-do-construct specifies a do-construct-name, the corresponding 23 end-do shall be an end-do-stmt specifying the same do-construct-name. If the do-stmt of a 24 block-do-construct does not specify a do-construct-name, the corresponding end-do shall not 25 specify a do-construct-name. 26C822 (R826) If the do-stmt is a nonlabel-do-stmt, the corresponding end-do shall be an end-do-stmt. 27C823 (R826) If the do-stmt is a label-do-stmt, the corresponding end-do shall be identified with the 28 same label. 298.1.6.1.2 Form of the nonblock DO construct 30 R835 nonblock-do-construct is action-term-do-construct 31 or outer-shared-do-construct 32 R836 action-term-do-construct is label-do-stmt 33 do-body 34 do-term-action-stmt 35 R837 do-body is [ execution-part-construct ] ... 36 R838 do-term-action-stmt is action-stmt 37 C824 (R838) A do-term-action-stmt shall not be a continue-stmt, a goto-stmt, a return-stmt, a stop-stmt, an exit-stmt, 38 a cycle-stmt, an end-function-stmt, an end-subroutine-stmt, an end-program-stmt, or an arithmetic-if-stmt. 39 C825 (R835) The do-term-action-stmt shall be identified with a label and the corresponding label-do-stmt shall refer 40 to the same label. 41 R839 outer-shared-do-construct is label-do-stmt 42 do-body 43 shared-term-do-construct 44 R840 shared-term-do-construct is outer-shared-do-construct 45 or inner-shared-do-construct 46 R841 inner-shared-do-construct is label-do-stmt 165 J3/04-007 WORKING DRAFT MAY 2004 1 do-body 2 do-term-shared-stmt 3 R842 do-term-shared-stmt is action-stmt 4 C826 (R842) A do-term-shared-stmt shall not be a goto-stmt, a return-stmt, a stop-stmt, an exit-stmt, a cycle-stmt, 5 an end-function-stmt, an end-subroutine-stmt, an end-program-stmt, or an arithmetic-if-stmt. 6 C827 (R840) The do-term-shared-stmt shall be identified with a label and all of the label-do-stmts of the inner-shared- 7 do-construct and outer-shared-do-construct shall refer to the same label. 8 The do-term-action-stmt, do-term-shared-stmt, or shared-term-do-construct following the do-body of a nonblock DO con- 9 struct is called the DO termination of that construct. 10 Within a scoping unit, all DO constructs whose DO statements refer to the same label are nonblock DO constructs, and 11 are said to share the statement identified by that label. 128.1.6.2 Range of the DO construct 13The range of a block DO construct is the do-block, which shall satisfy the rules for blocks (8.1.1). In 14particular, transfer of control to the interior of such a block from outside the block is prohibited. It 15is permitted to branch to the end-do of a block DO construct only from within the range of that DO 16construct. 17 The range of a nonblock DO construct consists of the do-body and the following DO termination. The end of such a 18 range is not bounded by a particular statement as for the other executable constructs (e.g., END IF); nevertheless, the 19 range satisfies the rules for blocks (8.1.1). Transfer of control into the do-body or to the DO termination from outside the 20 range is prohibited; in particular, it is permitted to branch to a do-term-shared-stmt only from within the range of the 21 corresponding inner-shared-do-construct. 228.1.6.3 Active and inactive DO constructs 23A DO construct is either active or inactive. Initially inactive, a DO construct becomes active only 24when its DO statement is executed. 25Once active, the DO construct becomes inactive only when it terminates (8.1.6.4.4). 268.1.6.4 Execution of a DO construct 27A DO construct specifies a loop, that is, a sequence of executable constructs that is executed repeatedly. 28There are three phases in the execution of a DO construct: initiation of the loop, execution of the loop 29range, and termination of the loop. 308.1.6.4.1 Loop initiation 31When the DO statement is executed, the DO construct becomes active. If loop-control is 32 [ , ] do-variable = scalar-int-expr1 , scalar-int-expr2 [ , scalar-int-expr3 ] 33the following steps are performed in sequence: 34 (1) The initial parameter m1, the terminal parameter m2, and the incrementation parameter m3 35 are of type integer with the same kind type parameter as the do-variable. Their values are es- 36 tablished by evaluating scalar-int-expr1, scalar-int-expr2, and scalar-int-expr3, respectively, 37 including, if necessary, conversion to the kind type parameter of the do-variable according 38 to the rules for numeric conversion (Table 7.9). If scalar-int-expr3 does not appear, m3 has 39 the value 1. The value of m3 shall not be zero. 40 (2) The DO variable becomes defined with the value of the initial parameter m1. 166 MAY 2004 WORKING DRAFT J3/04-007 1 (3) The iteration count is established and is the value of the expression (m2 - m1 + m3)/m3, 2 unless that value is negative, in which case the iteration count is 0. NOTE 8.15 The iteration count is zero whenever: m1 > m2 and m3 > 0, or m1 < m2 and m3 < 0. 3If loop-control is omitted, no iteration count is calculated. The effect is as if a large positive iteration 4count, impossible to decrement to zero, were established. If loop-control is [ , ] WHILE (scalar-logical- 5expr), the effect is as if loop-control were omitted and the following statement inserted as the first 6statement of the do-block: 7IF (.NOT. (scalar- logical-expr )) EXIT 8At the completion of the execution of the DO statement, the execution cycle begins. 98.1.6.4.2 The execution cycle 10The execution cycle of a DO construct consists of the following steps performed in sequence repeatedly 11until termination: 12 (1) The iteration count, if any, is tested. If it is zero, the loop terminates and the DO construct 13 becomes inactive. If loop-control is [ , ] WHILE (scalar-logical-expr), the scalar-logical-expr 14 is evaluated; if the value of this expression is false, the loop terminates and the DO construct 15 becomes inactive. If, as a result, all of the DO constructs sharing the do-term-shared-stmt are inactive, 16 the execution of all of these constructs is complete. However, if some of the DO constructs sharing the 17 do-term-shared-stmt are active, execution continues with step (3) of the execution cycle of the active DO 18 construct whose DO statement was most recently executed. 19 (2) If the iteration count is nonzero, the range of the loop is executed. 20 (3) The iteration count, if any, is decremented by one. The DO variable, if any, is incremented 21 by the value of the incrementation parameter m3. 22Except for the incrementation of the DO variable that occurs in step (3), the DO variable shall neither 23be redefined nor become undefined while the DO construct is active. 248.1.6.4.3 CYCLE statement 25Step (2) in the above execution cycle may be curtailed by executing a CYCLE statement from within 26the range of the loop. 27R843 cycle-stmt is CYCLE [ do-construct-name ] 28C828 (R843) If a cycle-stmt refers to a do-construct-name, it shall be within the range of that do- 29 construct; otherwise, it shall be within the range of at least one do-construct. 30A CYCLE statement belongs to a particular DO construct. If the CYCLE statement refers to a DO 31construct name, it belongs to that DO construct; otherwise, it belongs to the innermost DO construct 32in which it appears. 33Execution of a CYCLE statement causes immediate progression to step (3) of the current execution cycle 34of the DO construct to which it belongs. If this construct is a nonblock DO construct, the do-term-action-stmt or 35 do-term-shared-stmt is not executed. 36In a block DO construct, a transfer of control to the end-do has the same effect as execution of a CYCLE 37statement belonging to that construct. In a nonblock DO construct, transfer of control to the do-term-action-stmt 167 J3/04-007 WORKING DRAFT MAY 2004 1 or do-term-shared-stmt causes that statement or construct itself to be executed. Unless a further transfer of control results, 2 step (3) of the current execution cycle of the DO construct is then executed. 38.1.6.4.4 Loop termination 4The EXIT statement provides one way of terminating a loop. 5R844 exit-stmt is EXIT [ do-construct-name ] 6C829 (R844) If an exit-stmt refers to a do-construct-name, it shall be within the range of that do- 7 construct; otherwise, it shall be within the range of at least one do-construct. 8An EXIT statement belongs to a particular DO construct. If the EXIT statement refers to a DO 9construct name, it belongs to that DO construct; otherwise, it belongs to the innermost DO construct 10in which it appears. 11The loop terminates, and the DO construct becomes inactive, when any of the following occurs: 12 (1) Determination that the iteration count is zero or the scalar-logical-expr is false, when tested 13 during step (1) of the above execution cycle 14 (2) Execution of an EXIT statement belonging to the DO construct 15 (3) Execution of an EXIT statement or a CYCLE statement that is within the range of the DO 16 construct, but that belongs to an outer DO construct 17 (4) Transfer of control from a statement within the range of a DO construct to a statement that 18 is neither the end-do nor within the range of the same DO construct 19 (5) Execution of a RETURN statement within the range of the DO construct 20 (6) Execution of a STOP statement anywhere in the program; or termination of the program 21 for any other reason. 22When a DO construct becomes inactive, the DO variable, if any, of the DO construct retains its last 23defined value. 248.1.6.5 Examples of DO constructs NOTE 8.16 The following program fragment computes a tensor product of two arrays: DO I = 1, M DO J = 1, N C (I, J) = SUM (A (I, J, :) * B (:, I, J)) END DO END DO NOTE 8.17 The following program fragment contains a DO construct that uses the WHILE form of loop- control. The loop will continue to execute until an end-of-file or input/output error is encountered, at which point the DO statement terminates the loop. When a negative value of X is read, the program skips immediately to the next READ statement, bypassing most of the range of the loop. READ (IUN, '(1X, G14.7)', IOSTAT = IOS) X DO WHILE (IOS == 0) IF (X >= 0.) THEN CALL SUBA (X) 168 MAY 2004 WORKING DRAFT J3/04-007 NOTE 8.17 (cont.) CALL SUBB (X) ... CALL SUBZ (X) ENDIF READ (IUN, '(1X, G14.7)', IOSTAT = IOS) X END DO NOTE 8.18 The following example behaves exactly the same as the one in Note 8.17. However, the READ statement has been moved to the interior of the range, so that only one READ statement is needed. Also, a CYCLE statement has been used to avoid an extra level of IF nesting. DO ! A "DO WHILE + 1/2" loop READ (IUN, '(1X, G14.7)', IOSTAT = IOS) X IF (IOS /= 0) EXIT IF (X < 0.) CYCLE CALL SUBA (X) CALL SUBB (X) . . . CALL SUBZ (X) END DO NOTE 8.19 Additional examples of DO constructs are in C.5.3. 18.2 Branching 2Branching is used to alter the normal execution sequence. A branch causes a transfer of control from 3one statement in a scoping unit to a labeled branch target statement in the same scoping unit. Branching 4may be caused by a GOTO statement, a computed GOTO statement, an arithmetic IF statement, a 5 CALL statement that has an alt-return-spec, or an input/output statement that has an END= or ERR= 6specifier. Although procedure references and control constructs can cause transfer of control, they are 7not branches. A branch target statement is an action-stmt, an associate-stmt, an end-associate-stmt, 8an if-then-stmt, an end-if-stmt, a select-case-stmt, an end-select-stmt, a select-type-stmt, an end-select- 9type-stmt, a do-stmt, an end-do-stmt, a forall-construct-stmt, a do-term-action-stmt, a do-term-shared-stmt, or 10a where-construct-stmt. 118.2.1 GO TO statement 12R845 goto-stmt is GO TO label 13C830 (R845) The label shall be the statement label of a branch target statement that appears in the 14 same scoping unit as the goto-stmt. 15Execution of a GO TO statement causes a transfer of control so that the branch target statement 16identified by the label is executed next. 169 J3/04-007 WORKING DRAFT MAY 2004 1 8.2.2 Computed GO TO statement 2 R846 computed-goto-stmt is GO TO ( label-list ) [ , ] scalar-int-expr 3 C831 (R846 Each label in label-list shall be the statement label of a branch target statement that appears in the same 4 scoping unit as the computed-goto-stmt. NOTE 8.20 The same statement label may appear more than once in a label list. 5 Execution of a computed GO TO statement causes evaluation of the scalar integer expression. If this value is i such that 6 1 i n where n is the number of labels in label-list, a transfer of control occurs so that the next statement executed is 7 the one identified by the ith label in the list of labels. If i is less than 1 or greater than n, the execution sequence continues 8 as though a CONTINUE statement were executed. 9 8.2.3 Arithmetic IF statement 10 R847 arithmetic-if-stmt is IF ( scalar-numeric-expr ) label , label , label 11 C832 (R847) Each label shall be the label of a branch target statement that appears in the same scoping unit as the 12 arithmetic-if-stmt. 13 C833 (R847) The scalar-numeric-expr shall not be of type complex. NOTE 8.21 The same label may appear more than once in one arithmetic IF statement. 14 Execution of an arithmetic IF statement causes evaluation of the numeric expression followed by a transfer of control. The 15 branch target statement identified by the first label, the second label, or the third label is executed next depending on 16 whether the value of the numeric expression is less than zero, equal to zero, or greater than zero, respectively. 178.3 CONTINUE statement 18Execution of a CONTINUE statement has no effect. 19R848 continue-stmt is CONTINUE 208.4 STOP statement 21R849 stop-stmt is STOP [ stop-code ] 22R850 stop-code is scalar-char-constant 23 or digit [ digit [ digit [ digit [ digit ] ] ] ] 24C834 (R850) scalar-char-constant shall be of type default character. 25Execution of a STOP statement causes normal termination (2.3.4) of execution of the program. At the 26time of termination, the stop code, if any, is available in a processor-dependent manner. Leading zero 27digits in the stop code are not significant. If any exception (14) is signaling, the processor shall issue 28a warning indicating which exceptions are signaling; this warning shall be on the unit identified by the 29named constant ERROR UNIT from the ISO FORTRAN ENV intrinsic module (13.8.2.2). 170 MAY 2004 WORKING DRAFT J3/04-007 1Section 9: Input/output statements 2Input statements provide the means of transferring data from external media to internal storage or 3from an internal file to internal storage. This process is called reading. Output statements provide 4the means of transferring data from internal storage to external media or from internal storage to an 5internal file. This process is called writing. Some input/output statements specify that editing of the 6data is to be performed. 7In addition to the statements that transfer data, there are auxiliary input/output statements to ma- 8nipulate the external medium, or to describe or inquire about the properties of the connection to the 9external medium. 10The input/output statements are the OPEN, CLOSE, READ, WRITE, PRINT, BACKSPACE, END- 11FILE, REWIND, FLUSH, WAIT, and INQUIRE statements. 12The READ statement is a data transfer input statement. The WRITE statement and the PRINT 13statement are data transfer output statements. The OPEN statement and the CLOSE state- 14ment are file connection statements. The INQUIRE statement is a file inquiry statement. The 15BACKSPACE, ENDFILE, and REWIND statements are file positioning statements. 16A file is composed of either a sequence of file storage units (9.2.4) or a sequence of records, which 17provide an extra level of organization to the file. A file composed of records is called a record file. A 18file composed of file storage units is called a stream file. A processor may allow a file to be viewed 19both as a record file and as a stream file; in this case the relationship between the file storage units when 20viewed as a stream file and the records when viewed as a record file is processor dependent. 21A file is either an external file (9.2) or an internal file (9.3). 229.1 Records 23A record is a sequence of values or a sequence of characters. For example, a line on a terminal is usually 24considered to be a record. However, a record does not necessarily correspond to a physical entity. There 25are three kinds of records: 26 (1) Formatted 27 (2) Unformatted 28 (3) Endfile NOTE 9.1 What is called a "record" in Fortran is commonly called a "logical record". There is no concept in Fortran of a "physical record." 299.1.1 Formatted record 30A formatted record consists of a sequence of characters that are capable of representation in the 31processor; however, a processor may prohibit some control characters (3.1) from appearing in a formatted 32record. The length of a formatted record is measured in characters and depends primarily on the number 33of characters put into the record when it is written. However, it may depend on the processor and the 34external medium. The length may be zero. Formatted records may be read or written only by formatted 35input/output statements. 171 J3/04-007 WORKING DRAFT MAY 2004 1Formatted records may be prepared by means other than Fortran. 29.1.2 Unformatted record 3An unformatted record consists of a sequence of values in a processor-dependent form and may contain 4data of any type or may contain no data. The length of an unformatted record is measured in file storage 5units (9.2.4) and depends on the output list (9.5.2) used when it is written, as well as on the processor 6and the external medium. The length may be zero. Unformatted records may be read or written only 7by unformatted input/output statements. 89.1.3 Endfile record 9An endfile record is written explicitly by the ENDFILE statement; the file shall be connected for 10sequential access. An endfile record is written implicitly to a file connected for sequential access when 11the most recent data transfer statement referring to the file is a data transfer output statement, no 12intervening file positioning statement referring to the file has been executed, and 13 (1) A REWIND or BACKSPACE statement references the unit to which the file is connected 14 or 15 (2) The unit is closed, either explicitly by a CLOSE statement, implicitly by a program termi- 16 nation not caused by an error condition, or implicitly by another OPEN statement for the 17 same unit. 18An endfile record may occur only as the last record of a file. An endfile record does not have a length 19property. NOTE 9.2 An endfile record does not necessarily have any physical embodiment. The processor may use a record count or other means to register the position of the file at the time an ENDFILE statement is executed, so that it can take appropriate action when that position is reached again during a read operation. The endfile record, however it is implemented, is considered to exist for the BACKSPACE statement (9.7.1). 209.2 External files 21An external file is any file that exists in a medium external to the program. 22At any given time, there is a processor-dependent set of allowed access methods, a processor-dependent 23set of allowed forms, a processor-dependent set of allowed actions, and a processor-dependent set of 24allowed record lengths for a file. NOTE 9.3 For example, the processor-dependent set of allowed actions for a printer would likely include the write action, but not the read action. 25A file may have a name; a file that has a name is called a named file. The name of a named file is 26represented by a character string value. The set of allowable names for a file is processor dependent. 27An external file that is connected to a unit has a position property (9.2.3). NOTE 9.4 For more explanatory information on external files, see C.6.1. 172 MAY 2004 WORKING DRAFT J3/04-007 19.2.1 File existence 2At any given time, there is a processor-dependent set of external files that are said to exist for a program. 3A file may be known to the processor, yet not exist for a program at a particular time. NOTE 9.5 Security reasons may prevent a file from existing for a program. A newly created file may exist but contain no records. 4To create a file means to cause a file to exist that did not exist previously. To delete a file means to 5terminate the existence of the file. 6All input/output statements may refer to files that exist. An INQUIRE, OPEN, CLOSE, WRITE, 7PRINT, REWIND, FLUSH, or ENDFILE statement also may refer to a file that does not exist. Execu- 8tion of a WRITE, PRINT, or ENDFILE statement referring to a preconnected file that does not exist 9creates the file. 109.2.2 File access 11There are three methods of accessing the data of an external file: sequential, direct, and stream. Some 12files may have more than one allowed access method; other files may be restricted to one access method. NOTE 9.6 For example, a processor may allow only sequential access to a file on magnetic tape. Thus, the set of allowed access methods depends on the file and the processor. 13The method of accessing a file is determined when the file is connected to a unit (9.4.3) or when the file 14is created if the file is preconnected (9.4.4). 159.2.2.1 Sequential access 16Sequential access is a method of accessing the records of an external record file in order. 17When connected for sequential access, an external file has the following properties: 18 (1) The order of the records is the order in which they were written if the direct access method 19 is not a member of the set of allowed access methods for the file. If the direct access method 20 is also a member of the set of allowed access methods for the file, the order of the records 21 is the same as that specified for direct access. In this case, the first record accessible by 22 sequential access is the record whose record number is 1 for direct access. The second record 23 accessible by sequential access is the record whose record number is 2 for direct access, etc. 24 A record that has not been written since the file was created shall not be read. 25 (2) The records of the file are either all formatted or all unformatted, except that the last record 26 of the file may be an endfile record. Unless the previous reference to the file was a data 27 transfer output statement, the last record, if any, of the file shall be an endfile record. 28 (3) The records of the file shall be read or written only by sequential access input/output 29 statements. 309.2.2.2 Direct access 31Direct access is a method of accessing the records of an external record file in arbitrary order. 32When connected for direct access, an external file has the following properties: 173 J3/04-007 WORKING DRAFT MAY 2004 1 (1) Each record of the file is uniquely identified by a positive integer called the record number. 2 The record number of a record is specified when the record is written. Once established, 3 the record number of a record can never be changed. The order of the records is the order 4 of their record numbers. NOTE 9.7 A record cannot be deleted; however, a record may be rewritten. 5 (2) The records of the file are either all formatted or all unformatted. If the sequential access 6 method is also a member of the set of allowed access methods for the file, its endfile record, 7 if any, is not considered to be part of the file while it is connected for direct access. If the 8 sequential access method is not a member of the set of allowed access methods for the file, 9 the file shall not contain an endfile record. 10 (3) The records of the file shall be read or written only by direct access input/output statements. 11 (4) All records of the file have the same length. 12 (5) Records need not be read or written in the order of their record numbers. Any record may 13 be written into the file while it is connected to a unit. For example, it is permissible to write 14 record 3, even though records 1 and 2 have not been written. Any record may be read from 15 the file while it is connected to a unit, provided that the record has been written since the 16 file was created, and if a READ statement for this connection is permitted. 17 (6) The records of the file shall not be read or written using list-directed formatting (10.9), 18 namelist formatting (10.10), or a nonadvancing input/output statement (9.2.3.1). 199.2.2.3 Stream access 20Stream access is a method of accessing the file storage units (9.2.4) of an external stream file. 21The properties of an external file connected for stream access depend on whether the connection is for 22unformatted or formatted access. 23When connected for unformatted stream access, an external file has the following properties: 24 (1) The file storage units of the file shall be read or written only by stream access input/output 25 statements. 26 (2) Each file storage unit in the file is uniquely identified by a positive integer called the position. 27 The first file storage unit in the file is at position 1. The position of each subsequent file 28 storage unit is one greater than that of its preceding file storage unit. 29 (3) If it is possible to position the file, the file storage units need not be read or written in 30 order of their position. For example, it might be permissible to write the file storage unit 31 at position 3, even though the file storage units at positions 1 and 2 have not been written. 32 Any file storage unit may be read from the file while it is connected to a unit, provided that 33 the file storage unit has been written since the file was created, and if a READ statement 34 for this connection is permitted. 35When connected for formatted stream access, an external file has the following properties: 36 (1) Some file storage units of the file may contain record markers; this imposes a record structure 37 on the file in addition to its stream structure. There might or might not be a record marker 38 at the end of the file. If there is no record marker at the end of the file, the final record is 39 incomplete. 40 (2) No maximum length (9.4.5.12) is applicable to these records. 41 (3) Writing an empty record with no record marker has no effect. 174 MAY 2004 WORKING DRAFT J3/04-007 NOTE 9.8 Because the record structure is determined from the record markers that are stored in the file itself, an incomplete record at the end of the file is necessarily not empty. 1 (4) The file storage units of the file shall be read or written only by formatted stream access 2 input/output statements. 3 (5) Each file storage unit in the file is uniquely identified by a positive integer called the position. 4 The first file storage unit in the file is at position 1. The relationship between positions of 5 successive file storage units is processor dependent; not all positive integers need correspond 6 to valid positions. 7 (6) If it is possible to position the file, the file position can be set to a position that was 8 previously identified by the POS= specifier in an INQUIRE statement. NOTE 9.9 There may be some character positions in the file that do not correspond to characters written; this is because on some processors a record marker may be written to the file as a carriage-return/line- feed or other sequence. The means of determining the position in a file connected for stream access is via the POS= specifier in an INQUIRE statement (9.9.1.21). 9 (7) A processor may prohibit some control characters (3.1) from appearing in a formatted stream 10 file. 119.2.3 File position 12Execution of certain input/output statements affects the position of an external file. Certain circum- 13stances can cause the position of a file to become indeterminate. 14The initial point of a file is the position just before the first record or file storage unit. The terminal 15point is the position just after the last record or file storage unit. If there are no records or file storage 16units in the file, the initial point and the terminal point are the same position. 17If a record file is positioned within a record, that record is the current record; otherwise, there is no 18current record. 19Let n be the number of records in the file. If 1 < i n and a file is positioned within the ith record or 20between the (i - 1)th record and the ith record, the (i - 1)th record is the preceding record. If n 1 21and the file is positioned at its terminal point, the preceding record is the nth and last record. If n = 0 22or if a file is positioned at its initial point or within the first record, there is no preceding record. 23If 1 i < n and a file is positioned within the ith record or between the ith and (i + 1)th record, the 24(i+1)th record is the next record. If n 1 and the file is positioned at its initial point, the first record 25is the next record. If n = 0 or if a file is positioned at its terminal point or within the nth (last) record, 26there is no next record. 27For a file connected for stream access, the file position is either between two file storage units, at the 28initial point of the file, at the terminal point of the file, or undefined. 299.2.3.1 Advancing and nonadvancing input/output 30An advancing input/output statement always positions a record file after the last record read or 31written, unless there is an error condition. 32A nonadvancing input/output statement may position a record file at a character position within 33the current record, or a subsequent record (10.7.2). Using nonadvancing input/output, it is possible to 34read or write a record of the file by a sequence of input/output statements, each accessing a portion 35of the record. It is also possible to read variable-length records and be notified of their lengths. If a 175 J3/04-007 WORKING DRAFT MAY 2004 1nonadvancing output statement leaves a file positioned within a current record and no further output 2statement is executed for the file before it is closed or a BACKSPACE, ENDFILE, or REWIND statement 3is executed for it, the effect is as if the output statement were the corresponding advancing output 4statement. 59.2.3.2 File position prior to data transfer 6The positioning of the file prior to data transfer depends on the method of access: sequential, direct, or 7stream. 8For sequential access on input, if there is a current record, the file position is not changed. Otherwise, 9the file is positioned at the beginning of the next record and this record becomes the current record. 10Input shall not occur if there is no next record or if there is a current record and the last data transfer 11statement accessing the file performed output. 12If the file contains an endfile record, the file shall not be positioned after the endfile record prior to data 13transfer. However, a REWIND or BACKSPACE statement may be used to reposition the file. 14For sequential access on output, if there is a current record, the file position is not changed and the 15current record becomes the last record of the file. Otherwise, a new record is created as the next record 16of the file; this new record becomes the last and current record of the file and the file is positioned at 17the beginning of this record. 18For direct access, the file is positioned at the beginning of the record specified by the REC= specifier. 19This record becomes the current record. 20For stream access, the file is positioned immediately before the file storage unit specified by the POS= 21specifier; if there is no POS= specifier, the file position is not changed. 22File positioning for child data transfer statements is described in 9.5.3.7. 239.2.3.3 File position after data transfer 24If an error condition (9.10) occurred, the position of the file is indeterminate. If no error condition 25occurred, but an end-of-file condition (9.10) occurred as a result of reading an endfile record, the file is 26positioned after the endfile record. 27For unformatted stream access, if no error condition occurred, the file position is not changed. For 28unformatted stream output, if the file position exceeds the previous terminal point of the file, the 29terminal point is set to the file position. NOTE 9.10 An unformatted stream output statement with a POS= specifier and an empty output list can have the effect of extending the terminal point of a file without actually writing any data. 30For a formatted stream output statement, if no error condition occurred, the terminal point of the file 31is set to the highest-numbered position to which data was transferred by the statement. NOTE 9.11 The highest-numbered position might not be the current one if the output involved T or TL edit descriptors (10.7.1.1). 32For formatted stream input, if an end-of-file condition occurred, the file position is not changed. 33For nonadvancing input, if no error condition or end-of-file condition occurred, but an end-of-record 176 MAY 2004 WORKING DRAFT J3/04-007 1condition (9.10) occurred, the file is positioned after the record just read. If no error condition, end-of- 2file condition, or end-of-record condition occurred in a nonadvancing input statement, the file position 3is not changed. If no error condition occurred in a nonadvancing output statement, the file position is 4not changed. 5In all other cases, the file is positioned after the record just read or written and that record becomes the 6preceding record. 79.2.4 File storage units 8A file storage unit is the basic unit of storage in a stream file or an unformatted record file. It is the 9unit of file position for stream access, the unit of record length for unformatted files, and the unit of file 10size for all external files. 11Every value in a stream file or an unformatted record file shall occupy an integer number of file storage 12units; if the stream or record file is unformatted, this number shall be the same for all scalar values of 13the same type and type parameters. The number of file storage units required for an item of a given type 14and type parameters may be determined using the IOLENGTH= specifier of the INQUIRE statement 15(9.9.3). 16For a file connected for unformatted stream access, the processor shall not have alignment restrictions 17that prevent a value of any type from being stored at any positive integer file position. 18The number of bits in a file storage unit is given by the constant FILE STORAGE SIZE (13.8.2.3) 19defined in the intrinsic module ISO FORTRAN ENV. It is recommended that the file storage unit be 20an 8-bit octet where this choice is practical. NOTE 9.12 The requirement that every data value occupy an integer number of file storage units implies that data items inherently smaller than a file storage unit will require padding. This suggests that the file storage unit be small to avoid wasted space. Ideally, the file storage unit would be chosen such that padding is never required. A file storage unit of one bit would always meet this goal, but would likely be impractical because of the alignment requirements. The prohibition on alignment restrictions prohibits the processor from requiring data alignments larger than the file storage unit. The 8-bit octet is recommended as a good compromise that is small enough to accommodate the requirements of many applications, yet not so small that the data alignment requirements are likely to cause significant performance problems. 219.3 Internal files 22Internal files provide a means of transferring and converting data from internal storage to internal 23storage. 24An internal file is a record file with the following properties: 25 (1) The file is a variable of default, ASCII, or ISO 10646 character type that is not an array 26 section with a vector subscript. 27 (2) A record of an internal file is a scalar character variable. 28 (3) If the file is a scalar character variable, it consists of a single record whose length is the same 29 as the length of the scalar character variable. If the file is a character array, it is treated 30 as a sequence of character array elements. Each array element, if any, is a record of the 31 file. The ordering of the records of the file is the same as the ordering of the array elements 177 J3/04-007 WORKING DRAFT MAY 2004 1 in the array (6.2.2.2) or the array section (6.2.2.3). Every record of the file has the same 2 length, which is the length of an array element in the array. 3 (4) A record of the internal file becomes defined by writing the record. If the number of 4 characters written in a record is less than the length of the record, the remaining portion 5 of the record is filled with blanks. The number of characters to be written shall not exceed 6 the length of the record. 7 (5) A record may be read only if the record is defined. 8 (6) A record of an internal file may become defined (or undefined) by means other than an 9 output statement. For example, the character variable may become defined by a character 10 assignment statement. 11 (7) An internal file is always positioned at the beginning of the first record prior to data transfer, 12 except for child data transfer statements (9.5.3.7). This record becomes the current record. 13 (8) The initial value of a connection mode (9.4.1) is the value that would be implied by an 14 initial OPEN statement without the corresponding keyword. 15 (9) Reading and writing records shall be accomplished only by sequential access formatted 16 input/output statements. 17 (10) An internal file shall not be specified as the unit in a file connection statement, a file 18 positioning statement, or a file inquiry statement. 199.4 File connection 20A unit, specified by an io-unit, provides a means for referring to a file. 21R901 io-unit is file-unit-number 22 or * 23 or internal-file-variable 24R902 file-unit-number is scalar-int-expr 25R903 internal-file-variable is char-variable 26C901 (R903) The char-variable shall not be an array section with a vector subscript. 27C902 (R903) The char-variable shall be of type default character, ASCII character, or ISO 10646 28 character. 29A unit is either an external unit or an internal unit. An external unit is used to refer to an external 30file and is specified by an asterisk or a file-unit-number whose value is nonnegative or equal to one of 31the named constants INPUT UNIT, OUTPUT UNIT, or ERROR UNIT of the ISO FORTRAN ENV 32module (13.8.2). An internal unit is used to refer to an internal file and is specified by an internal- 33file-variable or a file-unit-number whose value is equal to the unit argument of an active derived-type 34input/output procedure (9.5.3.7). The value of a file-unit-number shall identify a valid unit. 35The external unit identified by a particular value of a scalar-int-expr is the same external unit in all 36program units of the program. NOTE 9.13 In the example: SUBROUTINE A READ (6) X ... SUBROUTINE B N = 6 REWIND N 178 MAY 2004 WORKING DRAFT J3/04-007 NOTE 9.13 (cont.) the value 6 used in both program units identifies the same external unit. 1An asterisk identifies particular processor-dependent external units that are preconnected for format- 2ted sequential access (9.5.3.2). These units are also identified by unit numbers defined by the named 3constants INPUT UNIT and OUTPUT UNIT of the ISO FORTRAN ENV module (13.8.2). 4This standard identifies a processor-dependent external unit for the purpose of error reporting. This 5unit shall be preconnected for sequential formatted output. The processor may define this to be the 6same as the output unit identified by an asterisk. This unit is also identified by a unit number defined 7by the named constant ERROR UNIT of the ISO FORTRAN ENV intrinsic module. 89.4.1 Connection modes 9A connection for formatted input/output has several changeable modes: the blank interpretation mode 10(10.7.6), delimiter mode (10.9.2, 10.10.2.1), sign mode (10.7.4), decimal edit mode (10.7.8), I/O round- 11ing mode (10.6.1.2.6), pad mode (9.5.3.4.2), and scale factor (10.7.5). A connection for unformatted 12input/output has no changeable modes. 13Values for the modes of a connection are established when the connection is initiated. If the connection 14is initiated by an OPEN statement, the values are as specified, either explicitly or implicitly, by the 15OPEN statement. If the connection is initiated other than by an OPEN statement (that is, if the file is 16an internal file or preconnected file) the values established are those that would be implied by an initial 17OPEN statement without the corresponding keywords. 18The scale factor cannot be explicitly specified in an OPEN statement; it is implicitly 0. 19The modes of a connection to an external file may be changed by a subsequent OPEN statement that 20modifies the connection. 21The modes of a connection may be temporarily changed by a corresponding keyword specifier in a 22data transfer statement or by an edit descriptor. Keyword specifiers take effect at the beginning of 23execution of the data transfer statement. Edit descriptors take effect when they are encountered in 24format processing. When a data transfer statement terminates, the values for the modes are reset to the 25values in effect immediately before the data transfer statement was executed. 269.4.2 Unit existence 27At any given time, there is a processor-dependent set of external units that are said to exist for a 28program. 29All input/output statements may refer to units that exist. The CLOSE, INQUIRE, and WAIT state- 30ments also may refer to units that do not exist. 319.4.3 Connection of a file to a unit 32An external unit has a property of being connected or not connected. If connected, it refers to an 33external file. An external unit may become connected by preconnection or by the execution of an OPEN 34statement. The property of connection is symmetric; the unit is connected to a file if and only if the file 35is connected to the unit. 36Every input/output statement except an OPEN, CLOSE, INQUIRE, or WAIT statement shall refer to 37a unit that is connected to a file and thereby make use of or affect that file. 179 J3/04-007 WORKING DRAFT MAY 2004 1A file may be connected and not exist (9.2.1). NOTE 9.14 An example is a preconnected external file that has not yet been written. 2A unit shall not be connected to more than one file at the same time, and a file shall not be connected to 3more than one unit at the same time. However, means are provided to change the status of an external 4unit and to connect a unit to a different file. 5This standard defines means of portable interoperation with C. C streams are described in 7.19.2 of the C 6International Standard. Whether a unit may be connected to a file that is also connected to a C stream 7is processor dependent. If the processor allows a unit to be connected to a file that is also connected to 8a C stream, the results of performing input/output operations on such a file are processor dependent. 9It is processor dependent whether the files connected to the units INPUT UNIT, OUTPUT UNIT, 10and ERROR UNIT correspond to the predefined C text streams standard input, standard output, and 11standard error. If a procedure defined by means of Fortran and a procedure defined by means other than 12Fortran perform input/output operations on the same external file, the results are processor dependent. 13A procedure defined by means of Fortran and a procedure defined by means other than Fortran can 14perform input/output operations on different external files without interference. 15After an external unit has been disconnected by the execution of a CLOSE statement, it may be con- 16nected again within the same program to the same file or to a different file. After an external file has 17been disconnected by the execution of a CLOSE statement, it may be connected again within the same 18program to the same unit or to a different unit. NOTE 9.15 The only means of referencing a file that has been disconnected is by the appearance of its name in an OPEN or INQUIRE statement. There might be no means of reconnecting an unnamed file once it is disconnected. 19An internal unit is always connected to the internal file designated by the variable that identifies the 20unit. NOTE 9.16 For more explanatory information on file connection properties, see C.6.5. 219.4.4 Preconnection 22Preconnection means that the unit is connected to a file at the beginning of execution of the program 23and therefore it may be specified in input/output statements without the prior execution of an OPEN 24statement. 259.4.5 The OPEN statement 26An OPEN statement initiates or modifies the connection between an external file and a specified unit. 27The OPEN statement may be used to connect an existing file to a unit, create a file that is preconnected, 28create a file and connect it to a unit, or change certain modes of a connection between a file and a unit. 29An external unit may be connected by an OPEN statement in any program unit of a program and, once 30connected, a reference to it may appear in any program unit of the program. 31If a unit is connected to a file that exists, execution of an OPEN statement for that unit is permitted. 32If the FILE= specifier is not included in such an OPEN statement, the file to be connected to the unit 33is the same as the file to which the unit is already connected. 180 MAY 2004 WORKING DRAFT J3/04-007 1If the file to be connected to the unit does not exist but is the same as the file to which the unit is 2preconnected, the modes specified by an OPEN statement become a part of the connection. 3If the file to be connected to the unit is not the same as the file to which the unit is connected, the effect 4is as if a CLOSE statement without a STATUS= specifier had been executed for the unit immediately 5prior to the execution of an OPEN statement. 6If the file to be connected to the unit is the same as the file to which the unit is connected, only the 7specifiers for changeable modes (9.4.1) may have values different from those currently in effect. If the 8POSITION= specifier appears in such an OPEN statement, the value specified shall not disagree with 9the current position of the file. If the STATUS= specifier is included in such an OPEN statement, it shall 10be specified with the value OLD. Execution of such an OPEN statement causes any new values of the 11specifiers for changeable modes to be in effect, but does not cause any change in any of the unspecified 12specifiers and the position of the file is unaffected. The ERR=, IOSTAT=, and IOMSG= specifiers from 13any previously executed OPEN statement have no effect on any currently executed OPEN statement. 14A STATUS= specifier with a value of OLD is always allowed when the file to be connected to the unit is 15the same as the file to which the unit is connected. In this case, if the status of the file was SCRATCH 16before execution of the OPEN statement, the file will still be deleted when the unit is closed, and the 17file is still considered to have a status of SCRATCH. 18If a file is already connected to a unit, execution of an OPEN statement on that file and a different unit 19is not permitted. 20R904 open-stmt is OPEN ( connect-spec-list ) 21R905 connect-spec is [ UNIT = ] file-unit-number 22 or ACCESS = scalar-default-char-expr 23 or ACTION = scalar-default-char-expr 24 or ASYNCHRONOUS = scalar-default-char-expr 25 or BLANK = scalar-default-char-expr 26 or DECIMAL = scalar-default-char-expr 27 or DELIM = scalar-default-char-expr 28 or ENCODING = scalar-default-char-expr 29 or ERR = label 30 or FILE = file-name-expr 31 or FORM = scalar-default-char-expr 32 or IOMSG = iomsg-variable 33 or IOSTAT = scalar-int-variable 34 or PAD = scalar-default-char-expr 35 or POSITION = scalar-default-char-expr 36 or RECL = scalar-int-expr 37 or ROUND = scalar-default-char-expr 38 or SIGN = scalar-default-char-expr 39 or STATUS = scalar-default-char-expr 40R906 file-name-expr is scalar-default-char-expr 41R907 iomsg-variable is scalar-default-char-variable 42C903 (R905) No specifier shall appear more than once in a given connect-spec-list. 43C904 (R905) A file-unit-number shall be specified; if the optional characters UNIT= are omitted, the 44 file-unit-number shall be the first item in the connect-spec-list. 45C905 (R905) The label used in the ERR= specifier shall be the statement label of a branch target 46 statement that appears in the same scoping unit as the OPEN statement. 47If the STATUS= specifier has the value NEW or REPLACE, the FILE= specifier shall appear. If the 181 J3/04-007 WORKING DRAFT MAY 2004 1STATUS= specifier has the value SCRATCH, the FILE= specifier shall not appear. If the STATUS= 2specifier has the value OLD, the FILE= specifier shall appear unless the unit is connected and the file 3connected to the unit exists. 4A specifier that requires a scalar-default-char-expr may have a limited list of character values. These 5values are listed for each such specifier. Any trailing blanks are ignored. The value specified is without 6regard to case. Some specifiers have a default value if the specifier is omitted. 7The IOSTAT=, ERR=, and IOMSG= specifiers are described in 9.10. NOTE 9.17 An example of an OPEN statement is: OPEN (10, FILE = 'employee.names', ACTION = 'READ', PAD = 'YES') NOTE 9.18 For more explanatory information on the OPEN statement, see C.6.4. 89.4.5.1 ACCESS= specifier in the OPEN statement 9The scalar-default-char-expr shall evaluate to SEQUENTIAL, DIRECT, or STREAM. The ACCESS= 10specifier specifies the access method for the connection of the file as being sequential, direct, or stream. 11If this specifier is omitted, the default value is SEQUENTIAL. For an existing file, the specified access 12method shall be included in the set of allowed access methods for the file. For a new file, the processor 13creates the file with a set of allowed access methods that includes the specified method. 149.4.5.2 ACTION= specifier in the OPEN statement 15The scalar-default-char-expr shall evaluate to READ, WRITE, or READWRITE. READ specifies that 16the WRITE, PRINT, and ENDFILE statements shall not refer to this connection. WRITE specifies 17that READ statements shall not refer to this connection. READWRITE permits any input/output 18statements to refer to this connection. If this specifier is omitted, the default value is processor dependent. 19If READWRITE is included in the set of allowable actions for a file, both READ and WRITE also shall 20be included in the set of allowed actions for that file. For an existing file, the specified action shall be 21included in the set of allowed actions for the file. For a new file, the processor creates the file with a set 22of allowed actions that includes the specified action. 239.4.5.3 ASYNCHRONOUS= specifier in the OPEN statement 24The scalar-default-char-expr shall evaluate to YES or NO. If YES is specified, asynchronous input/output 25on the unit is allowed. If NO is specified, asynchronous input/output on the unit is not allowed. If this 26specifier is omitted, the default value is NO. 279.4.5.4 BLANK= specifier in the OPEN statement 28The scalar-default-char-expr shall evaluate to NULL or ZERO. The BLANK= specifier is permitted only 29for a connection for formatted input/output. It specifies the current value of the blank interpretation 30mode (10.7.6, 9.5.1.5) for input for this connection. This mode has no effect on output. It is a changeable 31mode (9.4.1). If this specifier is omitted in an OPEN statement that initiates a connection, the default 32value is NULL. 182 MAY 2004 WORKING DRAFT J3/04-007 19.4.5.5 DECIMAL= specifier in the OPEN statement 2The scalar-default-char-expr shall evaluate to COMMA or POINT. The DECIMAL= specifier is per- 3mitted only for a connection for formatted input/output. It specifies the current value of the decimal 4edit mode (10.7.8, 9.5.1.6) for this connection. This is a changeable mode (9.4.1). If this specifier is 5omitted in an OPEN statement that initiates a connection, the default value is POINT. 69.4.5.6 DELIM= specifier in the OPEN statement 7The scalar-default-char-expr shall evaluate to APOSTROPHE, QUOTE, or NONE. The DELIM= spec- 8ifier is permitted only for a connection for formatted input/output. It specifies the current value of the 9delimiter mode (9.5.1.7) for list-directed (10.9.2) and namelist (10.10.2.1) output for the connection. 10This mode has no effect on input. It is a changeable mode (9.4.1). If this specifier is omitted in an 11OPEN statement that initiates a connection, the default value is NONE. 129.4.5.7 ENCODING= specifier in the OPEN statement 13The scalar-default-char-expr shall evaluate to UTF-8 or DEFAULT. The ENCODING= specifier is 14permitted only for a connection for formatted input/output. The value UTF-8 specifies that the encoding 15form of the file is UTF-8 as specified by ISO/IEC 10646-1:2000. Such a file is called a Unicode file, 16and all characters therein are of ISO 10646 character type. The value UTF-8 shall not be specified if 17the processor does not support the ISO 10646 character type. The value DEFAULT specifies that the 18encoding form of the file is processor-dependent. If this specifier is omitted in an OPEN statement that 19initiates a connection, the default value is DEFAULT. 209.4.5.8 FILE= specifier in the OPEN statement 21The value of the FILE= specifier is the name of the file to be connected to the specified unit. Any trailing 22blanks are ignored. The file-name-expr shall be a name that is allowed by the processor. If this specifier 23is omitted and the unit is not connected to a file, the STATUS= specifier shall be specified with a value 24of SCRATCH; in this case, the connection is made to a processor-dependent file. The interpretation of 25case is processor dependent. 269.4.5.9 FORM= specifier in the OPEN statement 27The scalar-default-char-expr shall evaluate to FORMATTED or UNFORMATTED. The FORM= spec- 28ifier determines whether the file is being connected for formatted or unformatted input/output. If this 29specifier is omitted, the default value is UNFORMATTED if the file is being connected for direct access 30or stream access, and the default value is FORMATTED if the file is being connected for sequential 31access. For an existing file, the specified form shall be included in the set of allowed forms for the file. 32For a new file, the processor creates the file with a set of allowed forms that includes the specified form. 339.4.5.10 PAD= specifier in the OPEN statement 34The scalar-default-char-expr shall evaluate to YES or NO. The PAD= specifier is permitted only for a 35connection for formatted input/output. It specifies the current value of the pad mode (9.5.3.4.2, 9.5.1.9) 36for input for this connection. This mode has no effect on output. It is a changeable mode (9.4.1). If this 37specifier is omitted in an OPEN statement that initiates a connection, the default value is YES. NOTE 9.19 For nondefault character types, the blank padding character is processor dependent. 183 J3/04-007 WORKING DRAFT MAY 2004 19.4.5.11 POSITION= specifier in the OPEN statement 2The scalar-default-char-expr shall evaluate to ASIS, REWIND, or APPEND. The connection shall be 3for sequential or stream access. A new file is positioned at its initial point. REWIND positions an 4existing file at its initial point. APPEND positions an existing file such that the endfile record is the 5next record, if it has one. If an existing file does not have an endfile record, APPEND positions the 6file at its terminal point. ASIS leaves the position unchanged if the file exists and already is connected. 7ASIS leaves the position unspecified if the file exists but is not connected. If this specifier is omitted, 8the default value is ASIS. 99.4.5.12 RECL= specifier in the OPEN statement 10The value of the RECL= specifier shall be positive. It specifies the length of each record in a file being 11connected for direct access, or specifies the maximum length of a record in a file being connected for 12sequential access. This specifier shall not appear when a file is being connected for stream access. This 13specifier shall appear when a file is being connected for direct access. If this specifier is omitted when 14a file is being connected for sequential access, the default value is processor dependent. If the file is 15being connected for formatted input/output, the length is the number of characters for all records that 16contain only characters of type default character. When a record contains any nondefault characters, 17the appropriate value for the RECL= specifier is processor dependent. If the file is being connected for 18unformatted input/output, the length is measured in file storage units. For an existing file, the value of 19the RECL= specifier shall be included in the set of allowed record lengths for the file. For a new file, 20the processor creates the file with a set of allowed record lengths that includes the specified value. 219.4.5.13 ROUND= specifier in the OPEN statement 22The scalar-default-char-expr shall evaluate to one of UP, DOWN, ZERO, NEAREST, COMPATIBLE, 23or PROCESSOR DEFINED. The ROUND= specifier is permitted only for a connection for formatted 24input/output. It specifies the current value of the I/O rounding mode (10.6.1.2.6, 9.5.1.12) for this 25connection. This is a changeable mode (9.4.1). If this specifier is omitted in an OPEN statement that 26initiates a connection, the I/O rounding mode is processor dependent; it shall be one of the above modes. NOTE 9.20 A processor is free to select any I/O rounding mode for the default mode. The mode might correspond to UP, DOWN, ZERO, NEAREST, or COMPATIBLE; or it might be a completely different I/O rounding mode. 279.4.5.14 SIGN= specifier in the OPEN statement 28The scalar-default-char-expr shall evaluate to one of PLUS, SUPPRESS, or PROCESSOR DEFINED. 29The SIGN= specifier is permitted only for a connection for formatted input/output. It specifies the 30current value of the sign mode (10.7.4, 9.5.1.13) for this connection. This is a changeable mode (9.4.1). 31If this specifier is omitted in an OPEN statement that initiates a connection, the default value is PRO- 32CESSOR DEFINED. 339.4.5.15 STATUS= specifier in the OPEN statement 34The scalar-default-char-expr shall evaluate to OLD, NEW, SCRATCH, REPLACE, or UNKNOWN. If 35OLD is specified, the file shall exist. If NEW is specified, the file shall not exist. 36Successful execution of an OPEN statement with NEW specified creates the file and changes the status 37to OLD. If REPLACE is specified and the file does not already exist, the file is created and the status is 38changed to OLD. If REPLACE is specified and the file does exist, the file is deleted, a new file is created 39with the same name, and the status is changed to OLD. If SCRATCH is specified, the file is created 184 MAY 2004 WORKING DRAFT J3/04-007 1and connected to the specified unit for use by the program but is deleted at the execution of a CLOSE 2statement referring to the same unit or at the normal termination of the program. NOTE 9.21 SCRATCH shall not be specified with a named file. 3If UNKNOWN is specified, the status is processor dependent. If this specifier is omitted, the default 4value is UNKNOWN. 59.4.6 The CLOSE statement 6The CLOSE statement is used to terminate the connection of a specified unit to an external file. 7Execution of a CLOSE statement for a unit may occur in any program unit of a program and need not 8occur in the same program unit as the execution of an OPEN statement referring to that unit. 9Execution of a CLOSE statement performs a wait operation for any pending asynchronous data transfer 10operations for the specified unit. 11Execution of a CLOSE statement specifying a unit that does not exist or has no file connected to it is 12permitted and affects no file. 13After a unit has been disconnected by execution of a CLOSE statement, it may be connected again 14within the same program, either to the same file or to a different file. After a named file has been 15disconnected by execution of a CLOSE statement, it may be connected again within the same program, 16either to the same unit or to a different unit, provided that the file still exists. 17At normal termination of execution of a program, all units that are connected are closed. Each unit 18is closed with status KEEP unless the file status prior to termination of execution was SCRATCH, in 19which case the unit is closed with status DELETE. NOTE 9.22 The effect is as though a CLOSE statement without a STATUS= specifier were executed on each connected unit. 20R908 close-stmt is CLOSE ( close-spec-list ) 21R909 close-spec is [ UNIT = ] file-unit-number 22 or IOSTAT = scalar-int-variable 23 or IOMSG = iomsg-variable 24 or ERR = label 25 or STATUS = scalar-default-char-expr 26C906 (R909) No specifier shall appear more than once in a given close-spec-list. 27C907 (R909) A file-unit-number shall be specified; if the optional characters UNIT= are omitted, the 28 file-unit-number shall be the first item in the close-spec-list. 29C908 (R909) The label used in the ERR= specifier shall be the statement label of a branch target 30 statement that appears in the same scoping unit as the CLOSE statement. 31The scalar-default-char-expr has a limited list of character values. Any trailing blanks are ignored. The 32value specified is without regard to case. 33The IOSTAT=, ERR=, and IOMSG= specifiers are described in 9.10. 185 J3/04-007 WORKING DRAFT MAY 2004 NOTE 9.23 An example of a CLOSE statement is: CLOSE (10, STATUS = 'KEEP') NOTE 9.24 For more explanatory information on the CLOSE statement, see C.6.6. 19.4.6.1 STATUS= specifier in the CLOSE statement 2The scalar-default-char-expr shall evaluate to KEEP or DELETE. The STATUS= specifier determines 3the disposition of the file that is connected to the specified unit. KEEP shall not be specified for a file 4whose status prior to execution of a CLOSE statement is SCRATCH. If KEEP is specified for a file that 5exists, the file continues to exist after the execution of a CLOSE statement. If KEEP is specified for a 6file that does not exist, the file will not exist after the execution of a CLOSE statement. If DELETE is 7specified, the file will not exist after the execution of a CLOSE statement. If this specifier is omitted, the 8default value is KEEP, unless the file status prior to execution of the CLOSE statement is SCRATCH, 9in which case the default value is DELETE. 109.5 Data transfer statements 11The READ statement is the data transfer input statement. The WRITE statement and the 12PRINT statement are the data transfer output statements. 13R910 read-stmt is READ ( io-control-spec-list ) [ input-item-list ] 14 or READ format [ , input-item-list ] 15R911 write-stmt is WRITE ( io-control-spec-list ) [ output-item-list ] 16R912 print-stmt is PRINT format [ , output-item-list ] NOTE 9.25 Examples of data transfer statements are: READ (6, *) SIZE READ 10, A, B WRITE (6, 10) A, S, J PRINT 10, A, S, J 10 FORMAT (2E16.3, I5) 179.5.1 Control information list 18A control information list is an io-control-spec-list. It governs data transfer. 19R913 io-control-spec is [ UNIT = ] io-unit 20 or [ FMT = ] format 21 or [ NML = ] namelist-group-name 22 or ADVANCE = scalar-default-char-expr 23 or ASYNCHRONOUS = scalar-char-initialization-expr 24 or BLANK = scalar-default-char-expr 25 or DECIMAL = scalar-default-char-expr 26 or DELIM = scalar-default-char-expr 27 or END = label 28 or EOR = label 186 MAY 2004 WORKING DRAFT J3/04-007 1 or ERR = label 2 or ID = scalar-int-variable 3 or IOMSG = iomsg-variable 4 or IOSTAT = scalar-int-variable 5 or PAD = scalar-default-char-expr 6 or POS = scalar-int-expr 7 or REC = scalar-int-expr 8 or ROUND = scalar-default-char-expr 9 or SIGN = scalar-default-char-expr 10 or SIZE = scalar-int-variable 11C909 (R913) No specifier shall appear more than once in a given io-control-spec-list. 12C910 (R913) An io-unit shall be specified; if the optional characters UNIT= are omitted, the io-unit 13 shall be the first item in the io-control-spec-list. 14C911 (R913) A DELIM= or SIGN= specifier shall not appear in a read-stmt. 15C912 (R913) A BLANK=, PAD=, END=, EOR=, or SIZE= specifier shall not appear in a write-stmt. 16C913 (R913) The label in the ERR=, EOR=, or END= specifier shall be the statement label of a 17 branch target statement that appears in the same scoping unit as the data transfer statement. 18C914 (R913) A namelist-group-name shall be the name of a namelist group. 19C915 (R913) A namelist-group-name shall not appear if an input-item-list or an output-item-list 20 appears in the data transfer statement. 21C916 (R913) An io-control-spec-list shall not contain both a format and a namelist-group-name. 22C917 (R913) If format appears without a preceding FMT=, it shall be the second item in the io- 23 control-spec-list and the first item shall be io-unit. 24C918 (R913) If namelist-group-name appears without a preceding NML=, it shall be the second item 25 in the io-control-spec-list and the first item shall be io-unit. 26C919 (R913) If io-unit is not a file-unit-number, the io-control-spec-list shall not contain a REC= 27 specifier or a POS= specifier. 28C920 (R913) If the REC= specifier appears, an END= specifier shall not appear, a namelist-group- 29 name shall not appear, and the format, if any, shall not be an asterisk. 30C921 (R913) An ADVANCE= specifier may appear only in a formatted sequential or stream in- 31 put/output statement with explicit format specification (10.1) whose control information list 32 does not contain an internal-file-variable as the io-unit. 33C922 (R913) If an EOR= specifier appears, an ADVANCE= specifier also shall appear. 34C923 (R913) If a SIZE= specifier appears, an ADVANCE= specifier also shall appear. 35C924 (R913) The scalar-char-initialization-expr in an ASYNCHRONOUS= specifier shall be of type 36 default character and shall have the value YES or NO. 37C925 (R913) An ASYNCHRONOUS= specifier with a value YES shall not appear unless io-unit is a 38 file-unit-number. 39C926 (R913) If an ID= specifier appears, an ASYNCHRONOUS= specifier with the value YES shall 187 J3/04-007 WORKING DRAFT MAY 2004 1 also appear. 2C927 (R913) If a POS= specifier appears, the io-control-spec-list shall not contain a REC= specifier. 3C928 (R913) If a DECIMAL=, BLANK=, PAD=, SIGN=, or ROUND= specifier appears, a format 4 or namelist-group-name shall also appear. 5C929 (R913) If a DELIM= specifier appears, either format shall be an asterisk or namelist-group-name 6 shall appear. 7A SIZE= specifier may appear only in an input statement that contains an ADVANCE= specifier with 8the value NO. 9An EOR= specifier may appear only in an input statement that contains an ADVANCE= specifier with 10the value NO. 11If the data transfer statement contains a format or namelist-group-name, the statement is a formatted 12input/output statement; otherwise, it is an unformatted input/output statement. 13The ADVANCE=, ASYNCHRONOUS=, DECIMAL=, BLANK=, DELIM=, PAD=, SIGN=, and 14ROUND= specifiers have a limited list of character values. Any trailing blanks are ignored. The 15values specified are without regard to case. 16The IOSTAT=, ERR=, EOR=, END=, and IOMSG= specifiers are described in 9.10. NOTE 9.26 An example of a READ statement is: READ (IOSTAT = IOS, UNIT = 6, FMT = '(10F8.2)') A, B 179.5.1.1 FMT= specifier in a data transfer statement 18The FMT= specifier supplies a format specification or specifies list-directed formatting for a formatted 19input/output statement. 20R914 format is default-char-expr 21 or label 22 or * 23C930 (R914) The label shall be the label of a FORMAT statement that appears in the same scoping 24 unit as the statement containing the FMT= specifier. 25The default-char-expr shall evaluate to a valid format specification (10.1.1 and 10.1.2). NOTE 9.27 A default-char-expr includes a character constant. 26If default-char-expr is an array, it is treated as if all of the elements of the array were specified in array 27element order and were concatenated. 28If format is *, the statement is a list-directed input/output statement. NOTE 9.28 An example in which the format is a character expression is: READ (6, FMT = "(" // CHAR_FMT // ")" ) X, Y, Z 188 MAY 2004 WORKING DRAFT J3/04-007 NOTE 9.28 (cont.) where CHAR FMT is a default character variable. 19.5.1.2 NML= specifier in a data transfer statement 2The NML= specifier supplies the namelist-group-name (5.4). This name identifies a particular collection 3of data objects on which transfer is to be performed. 4If a namelist-group-name appears, the statement is a namelist input/output statement. 59.5.1.3 ADVANCE= specifier in a data transfer statement 6The scalar-default-char-expr shall evaluate to YES or NO. The ADVANCE= specifier determines wheth- 7er advancing input/output occurs for this input/output statement. If YES is specified, advancing in- 8put/output occurs. If NO is specified, nonadvancing input/output occurs (9.2.3.1). If this specifier is 9omitted from an input/output statement that allows the specifier, the default value is YES. 109.5.1.4 ASYNCHRONOUS= specifier in a data transfer statement 11The ASYNCHRONOUS= specifier determines whether this input/output statement is synchronous or 12asynchronous. If YES is specified, the statement and the input/output operation are said to be asyn- 13chronous. If NO is specified or if the specifier is omitted, the statement and the input/output operation 14are said to be synchronous. 15Asynchronous input/output is permitted only for external files opened with an ASYNCHRONOUS= 16specifier with the value YES in the OPEN statement. NOTE 9.29 Both synchronous and asynchronous input/output are allowed for files opened with an ASYN- CHRONOUS= specifier of YES. For other files, only synchronous input/output is allowed; this includes files opened with an ASYNCHRONOUS= specifier of NO, files opened without an ASYN- CHRONOUS= specifier, preconnected files accessed without an OPEN statement, and internal files. The ASYNCHRONOUS= specifier value in a data transfer statement is an initialization expression because it effects compiler optimizations and, therefore, needs to be known at compile time. 17The processor may perform an asynchronous data transfer operation asynchronously, but it is not re- 18quired to do so. For each external file, records and file storage units read or written by asynchronous 19data transfer statements are read, written, and processed in the same order as they would have been if 20the data transfer statements were synchronous. 21If a variable is used in an asynchronous data transfer statement as 22 (1) an item in an input/output list, 23 (2) a group object in a namelist, or 24 (3) a SIZE= specifier 25the base object of the data-ref is implicitly given the ASYNCHRONOUS attribute in the scoping unit 26of the data transfer statement. This attribute may be confirmed by explicit declaration. 27When an asynchronous input/output statement is executed, the set of storage units specified by the 28item list or NML= specifier, plus the storage units specified by the SIZE= specifier, is defined to be the 29pending input/output storage sequence for the data transfer operation. 189 J3/04-007 WORKING DRAFT MAY 2004 NOTE 9.30 A pending input/output storage sequence is not necessarily a contiguous set of storage units. 1A pending input/output storage sequence affector is a variable of which any part is associated with a 2storage unit in a pending input/output storage sequence. 39.5.1.5 BLANK= specifier in a data transfer statement 4The scalar-default-char-expr shall evaluate to NULL or ZERO. The BLANK= specifier temporarily 5changes (9.4.1) the blank interpretation mode (10.7.6, 9.4.5.4) for the connection. If the specifier is 6omitted, the mode is not changed. 79.5.1.6 DECIMAL= specifier in a data transfer statement 8The scalar-default-char-expr shall evaluate to COMMA or POINT. The DECIMAL= specifier temporar- 9ily changes (9.4.1) the decimal edit mode (10.7.8, 9.4.5.5) for the connection. If the specifier is omitted, 10the mode is not changed. 119.5.1.7 DELIM= specifier in a data transfer statement 12The scalar-default-char-expr shall evaluate to APOSTROPHE, QUOTE, or NONE. The DELIM= spec- 13ifier temporarily changes (9.4.1) the delimiter mode (10.9.2, 10.10.2.1, 9.4.5.6) for the connection. If the 14specifier is omitted, the mode is not changed. 159.5.1.8 ID= specifier in a data transfer statement 16Successful execution of an asynchronous data transfer statement containing an ID= specifier causes the 17variable specified in the ID= specifier to become defined with a processor-dependent value. This value 18is referred to as the identifier of the data transfer operation. It can be used in a subsequent WAIT or 19INQUIRE statement to identify the particular data transfer operation. 20If an error occurs during the execution of a data transfer statement containing an ID= specifier, the 21variable specified in the ID= specifier becomes undefined. 22A child data transfer statement shall not specify the ID= specifier. 239.5.1.9 PAD= specifier in a data transfer statement 24The scalar-default-char-expr shall evaluate to YES or NO. The PAD= specifier temporarily changes 25(9.4.1) the pad mode (9.5.3.4.2, 9.4.5.10) for the connection. If the specifier is omitted, the mode is not 26changed. 279.5.1.10 POS= specifier in a data transfer statement 28The POS= specifier specifies the file position in file storage units. This specifier may appear in a data 29transfer statement only if the statement specifies a unit connected for stream access. A child data 30transfer statement shall not specify this specifier. 31A processor may prohibit the use of POS= with particular files that do not have the properties necessary 32to support random positioning. A processor may also prohibit positioning a particular file to any 33position prior to its current file position if the file does not have the properties necessary to support such 34positioning. 190 MAY 2004 WORKING DRAFT J3/04-007 NOTE 9.31 A file that represents connection to a device or data stream might not be positionable. 1If the file is connected for formatted stream access, the file position specified by POS= shall be equal to 2either 1 (the beginning of the file) or a value previously returned by a POS= specifier in an INQUIRE 3statement for the file. 49.5.1.11 REC= specifier in a data transfer statement 5The REC= specifier specifies the number of the record that is to be read or written. This specifier 6may appear only in an input/output statement that specifies a unit connected for direct access; it 7shall not appear in a child data transfer statement. If the control information list contains a REC= 8specifier, the statement is a direct access input/output statement. A child data transfer statement 9is a direct access data transfer statement if the parent is a direct access data transfer statement. Any 10other data transfer statement is a sequential access input/output statement or a stream access 11input/output statement, depending on whether the file connection is for sequential access or stream 12access. 139.5.1.12 ROUND= specifier in a data transfer statement 14The scalar-default-char-expr shall evaluate to one of the values specified in 9.4.5.13. The ROUND= 15specifier temporarily changes (9.4.1) the I/O rounding mode (10.6.1.2.6, 9.4.5.13) for the connection. If 16the specifier is omitted, the mode is not changed. 179.5.1.13 SIGN= specifier in a data transfer statement 18The scalar-default-char-expr shall evaluate to PLUS, SUPPRESS, or PROCESSOR DEFINED. The 19SIGN= specifier temporarily changes (9.4.1) the sign mode (10.7.4, 9.4.5.14) for the connection. If the 20specifier is omitted, the mode is not changed. 219.5.1.14 SIZE= specifier in a data transfer statement 22When a synchronous nonadvancing input statement terminates, the variable specified in the SIZE= 23specifier becomes defined with the count of the characters transferred by data edit descriptors during 24execution of the current input statement. Blanks inserted as padding (9.5.3.4.2) are not counted. 25For asynchronous nonadvancing input, the storage units specified in the SIZE= specifier become defined 26with the count of the characters transferred when the corresponding wait operation is executed. 279.5.2 Data transfer input/output list 28An input/output list specifies the entities whose values are transferred by a data transfer input/output 29statement. 30R915 input-item is variable 31 or io-implied-do 32R916 output-item is expr 33 or io-implied-do 34R917 io-implied-do is ( io-implied-do-object-list , io-implied-do-control ) 35R918 io-implied-do-object is input-item 36 or output-item 37R919 io-implied-do-control is do-variable = scalar-int-expr , 191 J3/04-007 WORKING DRAFT MAY 2004 1 scalar-int-expr [ , scalar-int-expr ] 2C931 (R915) A variable that is an input-item shall not be a whole assumed-size array. 3C932 (R915) A variable that is an input-item shall not be a procedure pointer. 4C933 (R919) The do-variable shall be a named scalar variable of type integer. 5C934 (R918) In an input-item-list, an io-implied-do-object shall be an input-item. In an output-item- 6 list, an io-implied-do-object shall be an output-item. 7C935 (R916) An expression that is an output-item shall not have a value that is a procedure pointer. 8An input-item shall not appear as, nor be associated with, the do-variable of any io-implied-do that 9contains the input-item. NOTE 9.32 A constant, an expression involving operators or function references, or an expression enclosed in parentheses may appear as an output list item but shall not appear as an input list item. 10If an input item is a pointer, it shall be associated with a definable target and data are transferred from 11the file to the associated target. If an output item is a pointer, it shall be associated with a target and 12data are transferred from the target to the file. NOTE 9.33 Data transfers always involve the movement of values between a file and internal storage. A pointer as such cannot be read or written. Therefore, a pointer shall not appear as an item in an input/output list unless it is associated with a target that can receive a value (input) or can deliver a value (output). 13If an input item or an output item is allocatable, it shall be allocated. 14A list item shall not be polymorphic unless it is processed by a user-defined derived-type input/output 15procedure (9.5.3.7). 16The do-variable of an io-implied-do that is in another io-implied-do shall not appear as, nor be associated 17with, the do-variable of the containing io-implied-do. 18The following rules describing whether to expand an input/output list item are re-applied to each 19expanded list item until none of the rules apply. 20If an array appears as an input/output list item, it is treated as if the elements, if any, were specified in 21array element order (6.2.2.2). However, no element of that array may affect the value of any expression 22in the input-item, nor may any element appear more than once in an input-item. NOTE 9.34 For example: INTEGER A (100), J (100) ... READ *, A (A) ! Not allowed READ *, A (LBOUND (A, 1) : UBOUND (A, 1)) ! Allowed READ *, A (J) ! Allowed if no two elements ! of J have the same value A(1) = 1; A(10) = 10 192 MAY 2004 WORKING DRAFT J3/04-007 NOTE 9.34 (cont.) READ *, A (A (1) : A (10)) ! Not allowed 1If a list item of derived type in an unformatted input/output statement is not processed by a user-defined 2derived-type input/output procedure (9.5.3.7), and if any subobject of that list item would be processed 3by a user-defined derived-type input/output procedure, the list item is treated as if all of the components 4of the object were specified in the list in component order (4.5.3.5); those components shall be accessible 5in the scoping unit containing the input/output statement and shall not be pointers or allocatable. 6An effective input/output list item of derived type in an unformatted input/output statement is treated 7as a single value in a processor-dependent form unless the list item or a subobject thereof is processed 8by a user-defined derived-type input/output procedure (9.5.3.7). NOTE 9.35 The appearance of a derived-type object as an input/output list item in an unformatted in- put/output statement is not equivalent to the list of its components. Unformatted input/output involving derived-type list items forms the single exception to the rule that the appearance of an aggregate list item (such as an array) is equivalent to the appearance of its expanded list of component parts. This exception permits the processor greater latitude in improving efficiency or in matching the processor-dependent sequence of values for a derived-type object to similar sequences for aggregate objects used by means other than Fortran. However, formatted input/output of all list items and unformatted input/output of list items other than those of derived types adhere to the above rule. 9If a list item of derived type in a formatted input/output statement is not processed by a user-defined 10derived-type input/output procedure, that list item is treated as if all of the components of the list item 11were specified in the list in component order; those components shall be accessible in the scoping unit 12containing the input/output statement and shall not be pointers or allocatable. 13If a derived-type list item is not treated as a list of its individual components, that list item's ultimate 14components shall not have the POINTER or ALLOCATABLE attribute unless that list item is processed 15by a user-defined derived-type input/output procedure. 16The scalar objects resulting when a data transfer statement's list items are expanded according to the 17rules in this section for handling array and derived-type list items are called effective items. Zero-sized 18arrays and io-implied-dos with an iteration count of zero do not contribute to the effective list items. A 19scalar character item of zero length is an effective list item. NOTE 9.36 In a formatted input/output statement, edit descriptors are associated with effective list items, which are always scalar. The rules in 9.5.2 determine the set of effective list items corresponding to each actual list item in the statement. These rules may have to be applied repetitively until all of the effective list items are scalar items. 20For an io-implied-do, the loop initialization and execution is the same as for a DO construct (8.1.6.4). 21An input/output list shall not contain an item of nondefault character type if the input/output statement 22specifies an internal file of default character type. An input/output list shall not contain an item of 23nondefault character type other than ISO 10646 or ASCII character type if the input/output statement 24specifies an internal file of ISO 10646 character type. An input/output list shall not contain a character 25item of any character type other than ASCII character type if the input/output statement specifies an 193 J3/04-007 WORKING DRAFT MAY 2004 1internal file of ASCII character type. NOTE 9.37 An example of an output list with an implied DO is: WRITE (LP, FMT = '(10F8.2)') (LOG (A (I)), I = 1, N + 9, K), G 29.5.3 Execution of a data transfer input/output statement 3Execution of a WRITE or PRINT statement for a file that does not exist creates the file unless an error 4condition occurs. 5The effect of executing a synchronous data transfer input/output statement shall be as if the following 6operations were performed in the order specified: 7 (1) Determine the direction of data transfer. 8 (2) Identify the unit. 9 (3) Perform a wait operation for all pending input/output operations for the unit. If an error, 10 end-of-file, or end-of-record condition occurs during any of the wait operations, steps 4 11 through 8 are skipped for the current data transfer statement. 12 (4) Establish the format if one is specified. 13 (5) If the statement is not a child data transfer statement (9.5.3.7), 14 (a) position the file prior to data transfer (9.2.3.2), and 15 (b) for formatted data transfer, set the left tab limit (10.7.1.1). 16 (6) Transfer data between the file and the entities specified by the input/output list (if any) or 17 namelist. 18 (7) Determine whether an error, end-of-file, or end-of-record condition has occurred. 19 (8) Position the file after data transfer (9.2.3.3) unless the statement is a child data transfer 20 statement (9.5.3.7). 21 (9) Cause any variable specified in a SIZE= specifier to become defined. 22 (10) If an error, end-of-file, or end-of-record condition occurred, processing continues as specified 23 in 9.10; otherwise any variable specified in an IOSTAT= specifier is assigned the value zero. 24The effect of executing an asynchronous data transfer input/output statement shall be as if the following 25operations were performed in the order specified: 26 (1) Determine the direction of data transfer. 27 (2) Identify the unit. 28 (3) Establish the format if one is specified. 29 (4) Position the file prior to data transfer (9.2.3.2) and, for formatted data transfer, set the left 30 tab limit (10.7.1.1). 31 (5) Establish the set of storage units identified by the input/output list. For a READ statement, 32 this might require some or all of the data in the file to be read if an input variable is used 33 as a scalar-int-expr in an io-implied-do-control in the input/output list, as a subscript, 34 substring-range, stride, or is otherwise referenced. 35 (6) Initiate an asynchronous data transfer between the file and the entities specified by the 36 input/output list (if any) or namelist. The asynchronous data transfer may complete (and 37 an error, end-of-file, or end-of-record condition may occur) during the execution of this data 38 transfer statement or during a later wait operation. 39 (7) Determine whether an error, end-of-file, or end-of-record condition has occurred. The con- 40 ditions may occur during the execution of this data transfer statement or during the corre- 41 sponding wait operation, but not both. 194 MAY 2004 WORKING DRAFT J3/04-007 1 Also, any of these conditions that would have occurred during the corresponding wait oper- 2 ation for a previously pending data transfer operation that does not have an ID= specifier 3 may occur during the execution of this data transfer statement. 4 (8) Position the file as if the data transfer had finished (9.2.3.3). 5 (9) Cause any variable specified in a SIZE= specifier to become undefined. 6 (10) If an error, end-of-file, or end-of-record condition occurred, processing continues as specified 7 in 9.10; otherwise any variable specified in an IOSTAT= specifier is assigned the value zero. 8For an asynchronous data transfer statement, the data transfers may occur during execution of the 9statement, during execution of the corresponding wait operation, or anywhere between. The data transfer 10operation is considered to be pending until a corresponding wait operation is performed. 11For asynchronous output, a pending input/output storage sequence affector (9.5.1.4) shall not be rede- 12fined, become undefined, or have its pointer association status changed. 13For asynchronous input, a pending input/output storage sequence affector shall not be referenced, be- 14come defined, become undefined, become associated with a dummy argument that has the VALUE 15attribute, or have its pointer association status changed. 16Error, end-of-file, and end-of-record conditions in an asynchronous data transfer operation may occur 17during execution of either the data transfer statement or the corresponding wait operation. If an ID= 18specifier does not appear in the initiating data transfer statement, the conditions may occur during the 19execution of any subsequent data transfer or wait operation for the same unit. When a condition occurs 20for a previously executed asynchronous data transfer statement, a wait operation is performed for all 21pending data transfer operations on that unit. When a condition occurs during a subsequent statement, 22any actions specified by IOSTAT=, IOMSG=, ERR=, END=, and EOR= specifiers for that statement 23are taken. NOTE 9.38 Because end-of-file and error conditions for asynchronous data transfer statements without an ID= specifier may be reported by the processor during the execution of a subsequent data transfer statement, it may be impossible for the user to determine which input/output statement caused the condition. Reliably detecting which READ statement caused an end-of-file condition requires that all asynchronous READ statements for the unit include an ID= specifier. 249.5.3.1 Direction of data transfer 25Execution of a READ statement causes values to be transferred from a file to the entities specified by 26the input list, if any, or specified within the file itself for namelist input. Execution of a WRITE or 27PRINT statement causes values to be transferred to a file from the entities specified by the output list 28and format specification, if any, or by the namelist-group-name for namelist output. 299.5.3.2 Identifying a unit 30A data transfer input/output statement that contains an input/output control list includes a UNIT= 31specifier that identifies an external or internal unit. A READ statement that does not contain an 32input/output control list specifies a particular processor-dependent unit, which is the same as the unit 33identified by * in a READ statement that contains an input/output control list. The PRINT statement 34specifies some other processor-dependent unit, which is the same as the unit identified by * in a WRITE 35statement. Thus, each data transfer input/output statement identifies an external or internal unit. 36The unit identified by a data transfer input/output statement shall be connected to a file when execution 37of the statement begins. 195 J3/04-007 WORKING DRAFT MAY 2004 NOTE 9.39 The file may be preconnected. 19.5.3.3 Establishing a format 2If the input/output control list contains * as a format, list-directed formatting is established. If namelist- 3group-name appears, namelist formatting is established. If no format or namelist-group-name is spec- 4ified, unformatted data transfer is established. Otherwise, the format specification identified by the 5FMT= specifier is established. 6On output, if an internal file has been specified, a format specification that is in the file or is associated 7with the file shall not be specified. 89.5.3.4 Data transfer 9Data are transferred between the file and the entities specified by the input/output list or namelist. 10The list items are processed in the order of the input/output list for all data transfer input/output 11statements except namelist formatted data transfer statements. The list items for a namelist input 12statement are processed in the order of the entities specified within the input records. The list items 13for a namelist output statement are processed in the order in which the variables are specified in the 14namelist-group-object-list. Effective items are derived from the input/output list items as described in 159.5.2. 16All values needed to determine which entities are specified by an input/output list item are determined 17at the beginning of the processing of that item. 18All values are transmitted to or from the entities specified by a list item prior to the processing of any 19succeeding list item for all data transfer input/output statements. NOTE 9.40 In the example, READ (N) N, X (N) the old value of N identifies the unit, but the new value of N is the subscript of X. 20All values following the name= part of the namelist entity (10.10) within the input records are transmit- 21ted to the matching entity specified in the namelist-group-object-list prior to processing any succeeding 22entity within the input record for namelist input statements. If an entity is specified more than once 23within the input record during a namelist formatted data transfer input statement, the last occurrence 24of the entity specifies the value or values to be used for that entity. 25An input list item, or an entity associated with it, shall not contain any portion of an established format 26specification. 27If the input/output item is a pointer, data are transferred between the file and the associated target. 28If an internal file has been specified, an input/output list item shall not be in the file or associated with 29the file. NOTE 9.41 The file is a data object. 30A DO variable becomes defined and its iteration count established at the beginning of processing of the 196 MAY 2004 WORKING DRAFT J3/04-007 1items that constitute the range of an io-implied-do. 2On output, every entity whose value is to be transferred shall be defined. 39.5.3.4.1 Unformatted data transfer 4During unformatted data transfer, data are transferred without editing between the file and the entities 5specified by the input/output list. If the file is connected for sequential or direct access, exactly one 6record is read or written. 7Objects of intrinsic or derived types may be transferred by means of an unformatted data transfer 8statement. 9A value in the file is stored in a contiguous sequence of file storage units, beginning with the file storage 10unit immediately following the current file position. 11After each value is transferred, the current file position is moved to a point immediately after the last 12file storage unit of the value. 13On input from a file connected for sequential or direct access, the number of file storage units required 14by the input list shall be less than or equal to the number of file storage units in the record. 15On input, if the file storage units transferred do not contain a value with the same type and type 16parameters as the input list entity, then the resulting value of the entity is processor-dependent except 17in the following cases: 18 (1) A complex list entity may correspond to two real values of the same kind stored in the file, 19 or vice-versa. 20 (2) A default character list entity of length n may correspond to n default characters stored in 21 the file, regardless of the length parameters of the entities that were written to these storage 22 units of the file. If the file is connected for stream input, the characters may have been 23 written by formatted stream output. 24On output to a file connected for unformatted direct access, the output list shall not specify more values 25than can fit into the record. If the file is connected for direct access and the values specified by the 26output list do not fill the record, the remainder of the record is undefined. 27If the file is connected for unformatted sequential access, the record is created with a length sufficient 28to hold the values from the output list. This length shall be one of the set of allowed record lengths for 29the file and shall not exceed the value specified in the RECL= specifier, if any, of the OPEN statement 30that established the connection. 31If the file is not connected for unformatted input/output, unformatted data transfer is prohibited. 32The unit specified shall be an external unit. 339.5.3.4.2 Formatted data transfer 34During formatted data transfer, data are transferred with editing between the file and the entities 35specified by the input/output list or by the namelist-group-name. Format control is initiated and editing 36is performed as described in Section 10. 37The current record and possibly additional records are read or written. 38Values may be transferred by means of a formatted data transfer statement to or from objects of intrinsic 39or derived types. In the latter case, the transfer is in the form of values of intrinsic types to or from the 40components of intrinsic types that ultimately comprise these structured objects unless the derived-type 41list item is processed by a user-defined derived-type input/output procedure (9.5.3.7). 197 J3/04-007 WORKING DRAFT MAY 2004 1If the file is not connected for formatted input/output, formatted data transfer is prohibited. 2During advancing input when the pad mode has the value NO, the input list and format specification 3shall not require more characters from the record than the record contains. 4During advancing input when the pad mode has the value YES, blank characters are supplied by the 5processor if the input list and format specification require more characters from the record than the 6record contains. 7During nonadvancing input when the pad mode has the value NO, an end-of-record condition (9.10) 8occurs if the input list and format specification require more characters from the record than the record 9contains, and the record is complete (9.2.2.3). If the record is incomplete, an end-of-file condition occurs 10instead of an end-of-record condition. 11During nonadvancing input when the pad mode has the value YES, blank characters are supplied by the 12processor if an input item and its corresponding data edit descriptor require more characters from the 13record than the record contains. If the record is incomplete, an end-of-file condition occurs; otherwise 14an end-of-record condition occurs. 15If the file is connected for direct access, the record number is increased by one as each succeeding record 16is read or written. 17On output, if the file is connected for direct access or is an internal file and the characters specified by 18the output list and format do not fill a record, blank characters are added to fill the record. 19On output, the output list and format specification shall not specify more characters for a record than 20have been specified by a RECL= specifier in the OPEN statement or the record length of an internal 21file. 229.5.3.5 List-directed formatting 23If list-directed formatting has been established, editing is performed as described in 10.9. 249.5.3.6 Namelist formatting 25If namelist formatting has been established, editing is performed as described in 10.10. 26Every allocatable namelist-group-object in the namelist group shall be allocated and every namelist- 27group-object that is a pointer shall be associated with a target. If a namelist-group-object is polymorphic 28or has an ultimate component that is allocatable or a pointer, that object shall be processed by a user- 29defined derived-type input/output procedure (9.5.3.7). 309.5.3.7 User-defined derived-type input/output 31User-defined derived-type input/output procedures allow a program to override the default handling of 32derived-type objects and values in data transfer input/output statements described in 9.5.2. 33A user-defined derived-type input/output procedure is a procedure accessible by a dtio-generic-spec 34(12.3.2.1). A particular user-defined derived-type input/output procedure is selected as described in 359.5.3.7.3. 369.5.3.7.1 Executing user-defined derived-type input/output data transfers 37If a derived-type input/output procedure is selected as specified in 9.5.3.7.3, the processor shall call the se- 38lected user-defined derived-type input/output procedure for any appropriate data transfer input/output 39statements executed in that scoping unit. The user-defined derived-type input/output procedure controls 40the actual data transfer operations for the derived-type list item. 198 MAY 2004 WORKING DRAFT J3/04-007 1A data transfer statement that includes a derived-type list item and that causes a user-defined derived- 2type input/output procedure to be invoked is called a parent data transfer statement. A data 3transfer statement that is executed while a parent data transfer statement is being processed and that 4specifies the unit passed into a user-defined derived-type input/output procedure is called a child data 5transfer statement. NOTE 9.42 A user-defined derived-type input/output procedure will usually contain child data transfer state- ments that read values from or write values to the current record or at the current file position. The effect of executing the user-defined derived-type input/output procedure is similar to that of substituting the list items from any child data transfer statements into the parent data transfer statement's list items, along with similar substitutions in the format specification. NOTE 9.43 A particular execution of a READ, WRITE or PRINT statement can be both a parent and a child data transfer statement. A user-defined derived-type input/output procedure can indirectly call itself or another user-defined derived-type input/output procedure by executing a child data transfer statement containing a list item of derived type, where a matching interface is accessible for that derived type. If a user-defined derived-type input/output procedure calls itself indirectly in this manner, it shall be declared RECURSIVE. 6A child data transfer statement is processed differently from a nonchild data transfer statement in the 7following ways: 8 · Executing a child data transfer statement does not position the file prior to data transfer. 9 · An unformatted child data transfer statement does not position the file after data transfer is 10 complete. 119.5.3.7.2 User-defined derived-type input/output procedures 12For a particular derived type and a particular set of kind type parameter values, there are four possible 13sets of characteristics for user-defined derived-type input/output procedures; one each for formatted 14input, formatted output, unformatted input, and unformatted output. The user need not supply all four 15procedures. The procedures are specified to be used for derived-type input/output by interface blocks 16(12.3.2.1) or by generic bindings (4.5.4), with a dtio-generic-spec (R1208). 17In the four interfaces, which specify the characteristics of user-defined procedures for derived-type in- 18put/output, the following syntax term is used: 19R920 dtv-type-spec is TYPE( derived-type-spec ) 20 or CLASS( derived-type-spec ) 21C936 (R920) If derived-type-spec specifies an extensible type, the CLASS keyword shall be used; 22 otherwise, the TYPE keyword shall be used. 23C937 (R920) All length type parameters of derived-type-spec shall be assumed. 24If the dtio-generic-spec is READ (FORMATTED), the characteristics shall be the same as those specified 25by the following interface: 26 SUBROUTINE my_read_routine_formatted & 27 (dtv, & 199 J3/04-007 WORKING DRAFT MAY 2004 1 unit, & 2 iotype, v_list, & 3 iostat, iomsg) 4 ! the derived-type value/variable 5 dtv-type-spec , INTENT(INOUT) :: dtv 6 INTEGER, INTENT(IN) :: unit ! unit number 7 ! the edit descriptor string 8 CHARACTER (LEN=*), INTENT(IN) :: iotype 9 INTEGER, INTENT(IN) :: v_list(:) 10 INTEGER, INTENT(OUT) :: iostat 11 CHARACTER (LEN=*), INTENT(INOUT) :: iomsg 12 END 13If the dtio-generic-spec is READ (UNFORMATTED), the characteristics shall be the same as those 14specified by the following interface: 15 SUBROUTINE my_read_routine_unformatted & 16 (dtv, & 17 unit, & 18 iostat, iomsg) 19 ! the derived-type value/variable 20 dtv-type-spec , INTENT(INOUT) :: dtv 21 INTEGER, INTENT(IN) :: unit 22 INTEGER, INTENT(OUT) :: iostat 23 CHARACTER (LEN=*), INTENT(INOUT) :: iomsg 24 END 25If the dtio-generic-spec is WRITE (FORMATTED), the characteristics shall be the same as those spec- 26ified by the following interface: 27 SUBROUTINE my_write_routine_formatted & 28 (dtv, & 29 unit, & 30 iotype, v_list, & 31 iostat, iomsg) 32 ! the derived-type value/variable 33 dtv-type-spec , INTENT(IN) :: dtv 34 INTEGER, INTENT(IN) :: unit 35 ! the edit descriptor string 36 CHARACTER (LEN=*), INTENT(IN) :: iotype 37 INTEGER, INTENT(IN) :: v_list(:) 38 INTEGER, INTENT(OUT) :: iostat 39 CHARACTER (LEN=*), INTENT(INOUT) :: iomsg 40 END 41If the dtio-generic-spec is WRITE (UNFORMATTED), the characteristics shall be the same as those 42specified by the following interface: 43 SUBROUTINE my_write_routine_unformatted & 44 (dtv, & 45 unit, & 200 MAY 2004 WORKING DRAFT J3/04-007 1 iostat, iomsg) 2 ! the derived-type value/variable 3 dtv-type-spec , INTENT(IN) :: dtv 4 INTEGER, INTENT(IN) :: unit 5 INTEGER, INTENT(OUT) :: iostat 6 CHARACTER (LEN=*), INTENT(INOUT) :: iomsg 7 END 8The actual specific procedure names (the my ... routine ... procedure names above) are not signifi- 9cant. In the discussion here and elsewhere, the dummy arguments in these interfaces are referred by the 10names given above; the names are, however, arbitrary. 11When a user-defined derived-type input/output procedure is invoked, the processor shall pass a unit 12argument that has a value as follows: 13 · If the parent data transfer statement uses a file-unit-number, the value of the unit argument shall 14 be that of the file-unit-number. 15 · If the parent data transfer statement is a WRITE statement with an asterisk unit or a PRINT 16 statement, the unit argument shall have the same value as the OUTPUT UNIT named constant 17 of the ISO FORTRAN ENV intrinsic module (13.8.2). 18 · If the parent data transfer statement is a READ statement with an asterisk unit or a READ 19 statement without an io-control-spec-list, the unit argument shall have the same value as the 20 INPUT UNIT named constant of the ISO FORTRAN ENV intrinsic module (13.8.2). 21 · Otherwise the parent data transfer statement must access an internal file, in which case the unit 22 argument shall have a processor-dependent negative value. NOTE 9.44 Because the unit argument value will be negative when the parent data transfer statement speci- fies an internal file, a user-defined derived-type input/output procedure should not execute an IN- QUIRE statement without checking that the unit argument is nonnegative or is equal to one of the named constants INPUT UNIT, OUTPUT UNIT, or ERROR UNIT of the ISO FORTRAN ENV intrinsic module (13.8.2). 23For formatted data transfer, the processor shall pass an iotype argument that has a value as follows: 24 · "LISTDIRECTED" if the parent data transfer statement specified list directed formatting, 25 · "NAMELIST" if the parent data transfer statement specified namelist formatting, or 26 · "DT" concatenated with the char-literal-constant, if any, of the edit descriptor, if the parent data 27 transfer statement contained a format specification and the list item's corresponding edit descriptor 28 was a DT edit descriptor. 29If the parent data transfer statement is a READ statement, the dtv dummy argument is argument 30associated with the effective list item that caused the user-defined derived-type input procedure to be 31invoked, as if the effective list item were an actual argument in this procedure reference (2.5.6). 32If the parent data transfer statement is a WRITE or PRINT statement, the processor shall provide the 33value of the effective list item in the dtv dummy argument. 201 J3/04-007 WORKING DRAFT MAY 2004 1If the v-list of the edit descriptor appears in the parent data transfer statement, the processor shall 2provide the values from it in the v list dummy argument, with the same number of elements in the 3same order as v-list. If there is no v-list in the edit descriptor or if the data transfer statement specifies 4list-directed or namelist formatting, the processor shall provide v list as a zero-sized array. NOTE 9.45 The user's procedure may choose to interpret an element of the v list argument as a field width, but this is not required. If it does, it would be appropriate to fill an output field with "*"s if the width is too small. 5The iostat argument is used to report whether an error, end-of-record, or end-of-file condition (9.10) 6occurs. If an error condition occurs, the user-defined derived-type input/output procedure shall assign 7a positive value to the iostat argument. Otherwise, if an end-of-file condition occurs, the user-defined 8derived-type input procedure shall assign the value of the named constant IOSTAT END (13.8.2.5) to the 9iostat argument. Otherwise, if an end-of-record condition occurs, the user-defined derived-type input 10procedure shall assign the value of the named constant IOSTAT EOR (13.8.2.6) to iostat. Otherwise, 11the user-defined derived-type input/output procedure shall assign the value zero to the iostat argument. 12If the user-defined derived-type input/output procedure returns a nonzero value for the iostat argument, 13the procedure shall also return an explanatory message in the iomsg argument. Otherwise, the procedure 14shall not change the value of the iomsg argument. NOTE 9.46 The values of the iostat and iomsg arguments set in a user-defined derived-type input/output procedure need not be passed to all of the parent data transfer statements. 15If the iostat argument of the user-defined derived-type input/output procedure has a nonzero value 16when that procedure returns, and the processor therefore terminates execution of the program as de- 17scribed in 9.10, the processor shall make the value of the iomsg argument available in a processor- 18dependent manner. 19When a parent READ statement is active, an input/output statement shall not read from any external 20unit other than the one specified by the dummy argument unit and shall not perform output to any 21external unit. 22When a parent WRITE or PRINT statement is active, an input/output statement shall not perform 23output to any external unit other than the one specified by the dummy argument unit and shall not 24read from any external unit. 25When a parent data transfer statement is active, a data transfer statement that specifies an internal file 26is permitted. 27OPEN, CLOSE, BACKSPACE, ENDFILE, and REWIND statements shall not be executed while a 28parent data transfer statement is active. 29A user-defined derived-type input/output procedure may use a FORMAT with a DT edit descriptor for 30handling a component of the derived type that is itself of a derived type. A child data transfer statement 31that is a list directed or namelist input/output statement may contain a list item of derived type. 32Because a child data transfer statement does not position the file prior to data transfer, the child data 33transfer statement starts transferring data from where the file was positioned by the parent data transfer 34statement's most recently processed effective list item or record positioning edit descriptor. This is not 35necessarily at the beginning of a record. 36A record positioning edit descriptor, such as TL and TR, used on unit by a child data transfer statement 202 MAY 2004 WORKING DRAFT J3/04-007 1shall not cause the record position to be positioned before the record position at the time the user-defined 2derived-type input/output procedure was invoked. NOTE 9.47 A robust user-defined derived-type input/output procedure may wish to use INQUIRE to deter- mine the settings of BLANK=, PAD=, ROUND=, DECIMAL=, and DELIM= for an external unit. The INQUIRE provides values as specified in 9.9. 3Neither a parent nor child data transfer statement shall be asynchronous. 4A user-defined derived-type input/output procedure, and any procedures invoked therefrom, shall not 5define, nor cause to become undefined, any storage location referenced by any input/output list item, 6the corresponding format, or any specifier in any active parent data transfer statement, except through 7the dtv argument. NOTE 9.48 A child data transfer statement shall not specify the ID=, POS=, or REC= specifiers in an input/output control list. NOTE 9.49 A simple example of derived type formatted output follows. The derived type variable chairman has two components. The type and an associated write formatted procedure are defined in a module so as to be accessible from wherever they might be needed. It would also be possible to check that iotype indeed has the value 'DT' and to set iostat and iomsg accordingly. MODULE p TYPE :: person CHARACTER (LEN=20) :: name INTEGER :: age CONTAINS GENERIC :: WRITE(FORMATTED) => pwf END TYPE person CONTAINS SUBROUTINE pwf (dtv,unit,iotype,vlist,iostat,iomsg) ! argument definitions CLASS(person), INTENT(IN) :: dtv INTEGER, INTENT(IN) :: unit CHARACTER (LEN=*), INTENT(IN) :: iotype INTEGER, INTENT(IN) :: vlist(:) INTEGER, INTENT(OUT) :: iostat CHARACTER (LEN=*), INTENT(INOUT) :: iomsg ! local variable CHARACTER (LEN=9) :: pfmt ! vlist(1) and (2) are to be used as the field widths of the two ! components of the derived type variable. First set up the format to ! be used for output. WRITE(pfmt,'(A,I2,A,I2,A)' ) '(A', vlist(1), ',I', vlist(2), ')' 203 J3/04-007 WORKING DRAFT MAY 2004 NOTE 9.49 (cont.) ! now the basic output statement WRITE(unit, FMT=pfmt, IOSTAT=iostat) dtv%name, dtv%age END SUBROUTINE pwf END MODULE p PROGRAM USE p INTEGER id, members TYPE (person) :: chairman ... WRITE(6, FMT="(I2, DT (15,6), I5)" ) id, chairman, members ! this writes a record with four fields, with lengths 2, 15, 6, 5 ! respectively END PROGRAM NOTE 9.50 In the following example, the variables of the derived type node form a linked list, with a single value at each node. The subroutine pwf is used to write the values in the list, one per line. MODULE p TYPE node INTEGER :: value = 0 TYPE (NODE), POINTER :: next_node => NULL ( ) CONTAINS GENERIC :: WRITE(FORMATTED) => pwf END TYPE node CONTAINS RECURSIVE SUBROUTINE pwf (dtv,unit,iotype,vlist,iostat,iomsg) ! Write the chain of values, each on a separate line in I9 format. CLASS(node), INTENT(IN) :: dtv INTEGER, INTENT(IN) :: unit CHARACTER (LEN=*), INTENT(IN) :: iotype INTEGER, INTENT(IN) :: vlist(:) INTEGER, INTENT(OUT) :: iostat CHARACTER (LEN=*), INTENT(INOUT) :: iomsg WRITE(unit,'(i9 /)', IOSTAT = iostat) dtv%value IF(iostat/=0) RETURN IF(ASSOCIATED(dtv%next_node)) WRITE(unit,'(dt)', IOSTAT=iostat) dtv%next_node END SUBROUTINE pwf END MODULE p 204 MAY 2004 WORKING DRAFT J3/04-007 19.5.3.7.3 Resolving derived-type input/output procedure references 2A suitable generic interface for user-defined derived-type input/output of an effective item is one that 3has a dtio-generic-spec that is appropriate to the direction (read or write) and form (formatted or 4unformatted) of the data transfer as specified in 9.5.3.7, and has a specific interface whose dtv argument 5is compatible with the effective item according to the rules for argument association in 12.4.1.2. 6When an effective item (9.5.2) that is of derived-type is encountered during a data transfer, user-defined 7derived-type input/output occurs if both of the following conditions are true: 8 (1) The circumstances of the input/output are such that user-defined derived-type input/output 9 is permitted; that is, either 10 (a) the transfer was initiated by a list-directed, namelist, or unformatted input/output 11 statement, or 12 (b) a format specification is supplied for the input/output statement, and the edit de- 13 scriptor corresponding to the effective item is a DT edit descriptor. 14 (2) A suitable user-defined derived-type input/output procedure is available; that is, either 15 (a) the declared type of the effective item has a suitable generic type-bound procedure, 16 or 17 (b) a suitable generic interface is accessible. 18If (2a) is true, the procedure referenced is determined as for explicit type-bound procedure references 19(12.4); that is, the binding with the appropriate specific interface is located in the declared type of the 20effective item, and the corresponding binding in the dynamic type of the effective item is selected. 21If (2a) is false and (2b) is true, the reference is to the procedure identified by the appropriate specific 22interface in the interface block. This reference shall not be to a dummy procedure that is not present, 23or to a disassociated procedure pointer. 249.5.4 Termination of data transfer statements 25Termination of an input/output data transfer statement occurs when any of the following conditions are 26met: 27 (1) Format processing encounters a data edit descriptor and there are no remaining elements 28 in the input-item-list or output-item-list. 29 (2) Unformatted or list-directed data transfer exhausts the input-item-list or output-item-list. 30 (3) Namelist output exhausts the namelist-group-object-list. 31 (4) An error condition occurs. 32 (5) An end-of-file condition occurs. 33 (6) A slash (/) is encountered as a value separator (10.9, 10.10) in the record being read during 34 list-directed or namelist input. 35 (7) An end-of-record condition occurs during execution of a nonadvancing input statement 36 (9.10). 379.6 Waiting on pending data transfer 38Execution of an asynchronous data transfer statement in which neither an error, end-of-record, nor end- 39of-file condition occurs initiates a pending data transfer operation. There may be multiple pending data 40transfer operations for the same or multiple units simultaneously. A pending data transfer operation 41remains pending until a corresponding wait operation is performed. A wait operation may be performed 42by a WAIT, INQUIRE, CLOSE, or file positioning statement. 205 J3/04-007 WORKING DRAFT MAY 2004 19.6.1 WAIT statement 2A WAIT statement performs a wait operation for specified pending asynchronous data transfer opera- 3tions. NOTE 9.51 The CLOSE, INQUIRE, and file positioning statements may also perform wait operations. 4R921 wait-stmt is WAIT (wait-spec-list) 5R922 wait-spec is [ UNIT = ] file-unit-number 6 or END = label 7 or EOR = label 8 or ERR = label 9 or ID = scalar-int-expr 10 or IOMSG = iomsg-variable 11 or IOSTAT = scalar-int-variable 12C938 (R922) No specifier shall appear more than once in a given wait-spec-list. 13C939 (R922) A file-unit-number shall be specified; if the optional characters UNIT= are omitted, the 14 file-unit-number shall be the first item in the wait-spec-list. 15C940 (R922) The label in the ERR=, EOR=, or END= specifier shall be the statement label of a 16 branch target statement that appears in the same scoping unit as the WAIT statement. 17The IOSTAT=, ERR=, EOR=, END=, and IOMSG= specifiers are described in 9.10. 18The value of the expression specified in the ID= specifier shall be the identifier of a pending data transfer 19operation for the specified unit. If the ID= specifier appears, a wait operation for the specified data 20transfer operation is performed. If the ID= specifier is omitted, wait operations for all pending data 21transfers for the specified unit are performed. 22Execution of a WAIT statement specifying a unit that does not exist, has no file connected to it, or was 23not opened for asynchronous input/output is permitted, provided that the WAIT statement has no ID= 24specifier; such a WAIT statement does not cause an error or end-of-file condition to occur. NOTE 9.52 An EOR= specifier has no effect if the pending data transfer operation is not a nonadvancing read. And END= specifier has no effect if the pending data transfer operation is not a READ. 259.6.2 Wait operation 26A wait operation completes the processing of a pending data transfer operation. Each wait operation 27completes only a single data transfer operation, although a single statement may perform multiple wait 28operations. 29If the actual data transfer is not yet complete, the wait operation first waits for its completion. If the 30data transfer operation is an input operation that completed without error, the storage units of the 31input/output storage sequence then become defined with the values as described in 9.5.1.14 and 9.5.3.4. 32If any error, end-of-file, or end-of-record conditions occur, the applicable actions specified by the IO- 33STAT=, IOMSG=, ERR=, END=, and EOR= specifiers of the statement that performs the wait oper- 34ation are taken. 35If an error or end-of-file condition occurs during a wait operation for a unit, the processor performs a 206 MAY 2004 WORKING DRAFT J3/04-007 1wait operation for all pending data transfer operations for that unit. NOTE 9.53 Error, end-of-file, and end-of-record conditions may be raised either during the data transfer state- ment that initiates asynchronous input/output, a subsequent asynchronous data transfer statement for the same unit, or during the wait operation. If such conditions are raised during a data transfer statement, they trigger actions according to the IOSTAT=, ERR=, END=, and EOR= specifiers of that statement; if they are raised during the wait operation, the actions are in accordance with the specifiers of the statement that performs the wait operation. 2After completion of the wait operation, the data transfer operation and its input/output storage sequence 3are no longer considered to be pending. 49.7 File positioning statements 5R923 backspace-stmt is BACKSPACE file-unit-number 6 or BACKSPACE ( position-spec-list ) 7R924 endfile-stmt is ENDFILE file-unit-number 8 or ENDFILE ( position-spec-list ) 9R925 rewind-stmt is REWIND file-unit-number 10 or REWIND ( position-spec-list ) 11A file that is connected for direct access shall not be referred to by a BACKSPACE, ENDFILE, or 12REWIND statement. A file that is connected for unformatted stream access shall not be referred to by a 13BACKSPACE statement. A file that is connected with an ACTION= specifier having the value READ 14shall not be referred to by an ENDFILE statement. 15R926 position-spec is [ UNIT = ] file-unit-number 16 or IOMSG = iomsg-variable 17 or IOSTAT = scalar-int-variable 18 or ERR = label 19C941 (R926) No specifier shall appear more than once in a given position-spec-list. 20C942 (R926) A file-unit-number shall be specified; if the optional characters UNIT= are omitted, the 21 file-unit-number shall be the first item in the position-spec-list. 22C943 (R926) The label in the ERR= specifier shall be the statement label of a branch target statement 23 that appears in the same scoping unit as the file positioning statement. 24The IOSTAT=, ERR=, and IOMSG= specifiers are described in 9.10. 25Execution of a file positioning statement performs a wait operation for all pending asynchronous data 26transfer operations for the specified unit. 279.7.1 BACKSPACE statement 28Execution of a BACKSPACE statement causes the file connected to the specified unit to be positioned 29before the current record if there is a current record, or before the preceding record if there is no current 30record. If the file is at its initial point, the position of the file is not changed. NOTE 9.54 If the preceding record is an endfile record, the file is positioned before the endfile record. 207 J3/04-007 WORKING DRAFT MAY 2004 1If a BACKSPACE statement causes the implicit writing of an endfile record, the file is positioned before 2the record that precedes the endfile record. 3Backspacing a file that is connected but does not exist is prohibited. 4Backspacing over records written using list-directed or namelist formatting is prohibited. NOTE 9.55 An example of a BACKSPACE statement is: BACKSPACE (10, IOSTAT = N) 59.7.2 ENDFILE statement 6Execution of an ENDFILE statement for a file connected for sequential access writes an endfile record 7as the next record of the file. The file is then positioned after the endfile record, which becomes the last 8record of the file. If the file also may be connected for direct access, only those records before the endfile 9record are considered to have been written. Thus, only those records may be read during subsequent 10direct access connections to the file. 11After execution of an ENDFILE statement for a file connected for sequential access, a BACKSPACE 12or REWIND statement shall be used to reposition the file prior to execution of any data transfer 13input/output statement or ENDFILE statement. 14Execution of an ENDFILE statement for a file connected for stream access causes the terminal point of 15the file to become equal to the current file position. Only file storage units before the current position are 16considered to have been written; thus only those file storage units may be subsequently read. Subsequent 17stream output statements may be used to write further data to the file. 18Execution of an ENDFILE statement for a file that is connected but does not exist creates the file; if 19the file is connected for sequential access, it is created prior to writing the endfile record. NOTE 9.56 An example of an ENDFILE statement is: ENDFILE K 209.7.3 REWIND statement 21Execution of a REWIND statement causes the specified file to be positioned at its initial point. NOTE 9.57 If the file is already positioned at its initial point, execution of this statement has no effect on the position of the file. 22Execution of a REWIND statement for a file that is connected but does not exist is permitted and has 23no effect on any file. NOTE 9.58 An example of a REWIND statement is: REWIND 10 208 MAY 2004 WORKING DRAFT J3/04-007 19.8 FLUSH statement 2The form of the FLUSH statement is: 3R927 flush-stmt is FLUSH file-unit-number 4 or FLUSH ( flush-spec-list ) 5R928 flush-spec is [UNIT =] file-unit-number 6 or IOSTAT = scalar-int-variable 7 or IOMSG = iomsg-variable 8 or ERR = label 9C944 (R928) No specifier shall appear more than once in a given flush-spec-list. 10C945 (R928) A file-unit-number shall be specified; if the optional characters UNIT= are omitted from 11 the unit specifier, the file-unit-number shall be the first item in the flush-spec-list. 12C946 (R928) The label in the ERR= specifier shall be the statement label of a branch target statement 13 that appears in the same scoping unit as the flush statement. 14The IOSTAT=, IOMSG= and ERR= specifiers are described in 9.10. The IOSTAT= variable shall 15be set to a processor-dependent positive value if an error occurs, to zero if the processor-dependent 16flush operation was successful, or to a processor-dependent negative value if the flush operation is not 17supported for the unit specified. 18Execution of a FLUSH statement causes data written to an external file to be available to other processes, 19or causes data placed in an external file by means other than Fortran to be available to a READ 20statement. The action is processor dependent. 21Execution of a FLUSH statement for a file that is connected but does not exist is permitted and has no 22effect on any file. A FLUSH statement has no effect on file position. NOTE 9.59 Because this standard does not specify the mechanism of file storage, the exact meaning of the flush operation is not precisely defined. The intention is that the flush operation should make all data written to a file available to other processes or devices, or make data recently added to a file by other processes or devices available to the program via a subsequent read operation. This is commonly called "flushing I/O buffers". NOTE 9.60 An example of a FLUSH statement is: FLUSH( 10, IOSTAT=N) 239.9 File inquiry 24The INQUIRE statement may be used to inquire about properties of a particular named file or of the 25connection to a particular unit. There are three forms of the INQUIRE statement: inquire by file, 26which uses the FILE= specifier, inquire by unit, which uses the UNIT= specifier, and inquire by 27output list, which uses only the IOLENGTH= specifier. All specifier value assignments are performed 28according to the rules for assignment statements. 29An INQUIRE statement may be executed before, while, or after a file is connected to a unit. All values 30assigned by an INQUIRE statement are those that are current at the time the statement is executed. 209 J3/04-007 WORKING DRAFT MAY 2004 1R929 inquire-stmt is INQUIRE ( inquire-spec-list ) 2 or INQUIRE ( IOLENGTH = scalar-int-variable ) 3 output-item-list NOTE 9.61 Examples of INQUIRE statements are: INQUIRE (IOLENGTH = IOL) A (1:N) INQUIRE (UNIT = JOAN, OPENED = LOG_01, NAMED = LOG_02, & FORM = CHAR_VAR, IOSTAT = IOS) 49.9.1 Inquiry specifiers 5Unless constrained, the following inquiry specifiers may be used in either of the inquire by file or inquire 6by unit forms of the INQUIRE statement: 7R930 inquire-spec is [ UNIT = ] file-unit-number 8 or FILE = file-name-expr 9 or ACCESS = scalar-default-char-variable 10 or ACTION = scalar-default-char-variable 11 or ASYNCHRONOUS = scalar-default-char-variable 12 or BLANK = scalar-default-char-variable 13 or DECIMAL = scalar-default-char-variable 14 or DELIM = scalar-default-char-variable 15 or DIRECT = scalar-default-char-variable 16 or ENCODING = scalar-default-char-variable 17 or ERR = label 18 or EXIST = scalar-default-logical-variable 19 or FORM = scalar-default-char-variable 20 or FORMATTED = scalar-default-char-variable 21 or ID = scalar-int-expr 22 or IOMSG = iomsg-variable 23 or IOSTAT = scalar-int-variable 24 or NAME = scalar-default-char-variable 25 or NAMED = scalar-default-logical-variable 26 or NEXTREC = scalar-int-variable 27 or NUMBER = scalar-int-variable 28 or OPENED = scalar-default-logical-variable 29 or PAD = scalar-default-char-variable 30 or PENDING = scalar-default-logical-variable 31 or POS = scalar-int-variable 32 or POSITION = scalar-default-char-variable 33 or READ = scalar-default-char-variable 34 or READWRITE = scalar-default-char-variable 35 or RECL = scalar-int-variable 36 or ROUND = scalar-default-char-variable 37 or SEQUENTIAL = scalar-default-char-variable 38 or SIGN = scalar-default-char-variable 39 or SIZE = scalar-int-variable 40 or STREAM = scalar-default-char-variable 41 or UNFORMATTED = scalar-default-char-variable 210 MAY 2004 WORKING DRAFT J3/04-007 1 or WRITE = scalar-default-char-variable 2C947 (R930) No specifier shall appear more than once in a given inquire-spec-list. 3C948 (R930) An inquire-spec-list shall contain one FILE= specifier or one UNIT= specifier, but not 4 both. 5C949 (R930) In the inquire by unit form of the INQUIRE statement, if the optional characters UNIT= 6 are omitted, the file-unit-number shall be the first item in the inquire-spec-list. 7C950 (R930) If an ID= specifier appears, a PENDING= specifier shall also appear. 8The value of file-unit-number shall be nonnegative or equal to one of the named constants INPUT UNIT, 9OUTPUT UNIT, or ERROR UNIT of the ISO FORTRAN ENV intrinsic module (13.8.2). 10When a returned value of a specifier other than the NAME= specifier is of type character, the value 11returned is in upper case. 12If an error condition occurs during execution of an INQUIRE statement, all of the inquiry specifier 13variables become undefined, except for variables in the IOSTAT= and IOMSG= specifiers (if any). 14The IOSTAT=, ERR=, and IOMSG= specifiers are described in 9.10. 159.9.1.1 FILE= specifier in the INQUIRE statement 16The value of the file-name-expr in the FILE= specifier specifies the name of the file being inquired about. 17The named file need not exist or be connected to a unit. The value of the file-name-expr shall be of a 18form acceptable to the processor as a file name. Any trailing blanks are ignored. The interpretation of 19case is processor dependent. 209.9.1.2 ACCESS= specifier in the INQUIRE statement 21The scalar-default-char-variable in the ACCESS= specifier is assigned the value SEQUENTIAL if the 22file is connected for sequential access, DIRECT if the file is connected for direct access, or STREAM if 23the file is connected for stream access. If there is no connection, it is assigned the value UNDEFINED. 249.9.1.3 ACTION= specifier in the INQUIRE statement 25The scalar-default-char-variable in the ACTION= specifier is assigned the value READ if the file is 26connected for input only, WRITE if the file is connected for output only, and READWRITE if it 27is connected for both input and output. If there is no connection, the scalar-default-char-variable is 28assigned the value UNDEFINED. 299.9.1.4 ASYNCHRONOUS= specifier in the INQUIRE statement 30The scalar-default-char-variable in the ASYNCHRONOUS= specifier is assigned the value YES if the 31file is connected and asynchronous input/output on the unit is allowed; it is assigned the value NO if the 32file is connected and asynchronous input/output on the unit is not allowed. If there is no connection, 33the scalar-default-char-variable is assigned the value UNDEFINED. 349.9.1.5 BLANK= specifier in the INQUIRE statement 35The scalar-default-char-variable in the BLANK= specifier is assigned the value ZERO or NULL, corre- 36sponding to the blank interpretation mode in effect for a connection for formatted input/output. If there 37is no connection, or if the connection is not for formatted input/output, the scalar-default-char-variable 38is assigned the value UNDEFINED. 211 J3/04-007 WORKING DRAFT MAY 2004 19.9.1.6 DECIMAL= specifier in the INQUIRE statement 2The scalar-default-char-variable in the DECIMAL= specifier is assigned the value COMMA or POINT, 3corresponding to the decimal edit mode in effect for a connection for formatted input/output. If there 4is no connection, or if the connection is not for formatted input/output, the scalar-default-char-variable 5is assigned the value UNDEFINED. 69.9.1.7 DELIM= specifier in the INQUIRE statement 7The scalar-default-char-variable in the DELIM= specifier is assigned the value APOSTROPHE, QUOTE, 8or NONE, corresponding to the delimiter mode in effect for a connection for formatted input/output. 9If there is no connection or if the connection is not for formatted input/output, the scalar-default-char- 10variable is assigned the value UNDEFINED. 119.9.1.8 DIRECT= specifier in the INQUIRE statement 12The scalar-default-char-variable in the DIRECT= specifier is assigned the value YES if DIRECT is 13included in the set of allowed access methods for the file, NO if DIRECT is not included in the set of 14allowed access methods for the file, and UNKNOWN if the processor is unable to determine whether or 15not DIRECT is included in the set of allowed access methods for the file. 169.9.1.9 ENCODING= specifier in the INQUIRE statement 17The scalar-default-char-variable in the ENCODING= specifier is assigned the value UTF-8 if the file 18is connected for formatted input/output with an encoding form of UTF-8, and is assigned the value 19UNDEFINED if the file is connected for unformatted input/output. If there is no connection, it is 20assigned the value UTF-8 if the processor is able to determine that the encoding form of the file is 21UTF-8. If the processor is unable to determine the encoding form of the file, the variable is assigned the 22value UNKNOWN. NOTE 9.62 The value assigned may be something other than UTF-8, UNDEFINED, or UNKNOWN if the processor supports other specific encoding forms (e.g. UTF-16BE). 239.9.1.10 EXIST= specifier in the INQUIRE statement 24Execution of an INQUIRE by file statement causes the scalar-default-logical-variable in the EXIST= 25specifier to be assigned the value true if there exists a file with the specified name; otherwise, false is 26assigned. Execution of an INQUIRE by unit statement causes true to be assigned if the specified unit 27exists; otherwise, false is assigned. 289.9.1.11 FORM= specifier in the INQUIRE statement 29The scalar-default-char-variable in the FORM= specifier is assigned the value FORMATTED if the 30file is connected for formatted input/output, and is assigned the value UNFORMATTED if the file is 31connected for unformatted input/output. If there is no connection, it is assigned the value UNDEFINED. 329.9.1.12 FORMATTED= specifier in the INQUIRE statement 33The scalar-default-char-variable in the FORMATTED= specifier is assigned the value YES if FORMAT- 34TED is included in the set of allowed forms for the file, NO if FORMATTED is not included in the set 35of allowed forms for the file, and UNKNOWN if the processor is unable to determine whether or not 36FORMATTED is included in the set of allowed forms for the file. 212 MAY 2004 WORKING DRAFT J3/04-007 19.9.1.13 ID= specifier in the INQUIRE statement 2The value of the expression specified in the ID= specifier shall be the identifier of a pending data transfer 3operation for the specified unit. This specifier interacts with the PENDING= specifier (9.9.1.20). 49.9.1.14 NAME= specifier in the INQUIRE statement 5The scalar-default-char-variable in the NAME= specifier is assigned the value of the name of the file if 6the file has a name; otherwise, it becomes undefined. NOTE 9.63 If this specifier appears in an INQUIRE by file statement, its value is not necessarily the same as the name given in the FILE= specifier. However, the value returned shall be suitable for use as the value of the file-name-expr in the FILE= specifier in an OPEN statement. The processor may return a file name qualified by a user identification, device, directory, or other relevant information. 7The case of the characters assigned to scalar-default-char-variable is processor dependent. 89.9.1.15 NAMED= specifier in the INQUIRE statement 9The scalar-default-logical-variable in the NAMED= specifier is assigned the value true if the file has a 10name; otherwise, it is assigned the value false. 119.9.1.16 NEXTREC= specifier in the INQUIRE statement 12The scalar-int-variable in the NEXTREC= specifier is assigned the value n + 1, where n is the record 13number of the last record read from or written to the file connected for direct access. If the file is con- 14nected but no records have been read or written since the connection, the scalar-int-variable is assigned 15the value 1. If the file is not connected for direct access or if the position of the file is indeterminate 16because of a previous error condition, the scalar-int-variable becomes undefined. If there are pending 17data transfer operations for the specified unit, the value assigned is computed as if all the pending data 18transfers had already completed. 199.9.1.17 NUMBER= specifier in the INQUIRE statement 20The scalar-int-variable in the NUMBER= specifier is assigned the value of the external unit number of 21the unit that is connected to the file. If there is no unit connected to the file, the value -1 is assigned. 229.9.1.18 OPENED= specifier in the INQUIRE statement 23Execution of an INQUIRE by file statement causes the scalar-default-logical-variable in the OPENED= 24specifier to be assigned the value true if the file specified is connected to a unit; otherwise, false is 25assigned. Execution of an INQUIRE by unit statement causes the scalar-default-logical-variable to be 26assigned the value true if the specified unit is connected to a file; otherwise, false is assigned. 279.9.1.19 PAD= specifier in the INQUIRE statement 28The scalar-default-char-variable in the PAD= specifier is assigned the value YES or NO, corresponding 29to the pad mode in effect for a connection for formatted input/output. If there is no connection or if 30the connection is not for formatted input/output, the scalar-default-char-variable is assigned the value 31UNDEFINED. 213 J3/04-007 WORKING DRAFT MAY 2004 19.9.1.20 PENDING= specifier in the INQUIRE statement 2The PENDING= specifier is used to determine whether or not previously pending asynchronous data 3transfers are complete. A data transfer operation is previously pending if it is pending at the beginning 4of execution of the INQUIRE statement. 5If an ID= specifier appears and the specified data transfer operation is complete, then the variable 6specified in the PENDING= specifier is assigned the value false and the INQUIRE statement performs 7the wait operation for the specified data transfer. 8If the ID= specifier is omitted and all previously pending data transfer operations for the specified unit 9are complete, then the variable specified in the PENDING= specifier is assigned the value false and the 10INQUIRE statement performs wait operations for all previously pending data transfers for the specified 11unit. 12In all other cases, the variable specified in the PENDING= specifier is assigned the value true and no 13wait operations are performed; in this case the previously pending data transfers remain pending after 14the execution of the INQUIRE statement. NOTE 9.64 The processor has considerable flexibility in defining when it considers a transfer to be complete. Any of the following approaches could be used: (1) The INQUIRE statement could consider an asynchronous data transfer to be incom- plete until after the corresponding wait operation. In this case PENDING= would always return true unless there were no previously pending data transfers for the unit. (2) The INQUIRE statement could wait for all specified data transfers to complete and then always return false for PENDING=. (3) The INQUIRE statement could actually test the state of the specified data transfer operations. 159.9.1.21 POS= specifier in the INQUIRE statement 16The scalar-int-variable in the POS= specifier is assigned the number of the file storage unit immediately 17following the current position of a file connected for stream access. If the file is positioned at its terminal 18position, the variable is assigned a value one greater than the number of the highest-numbered file storage 19unit in the file. If the file is not connected for stream access or if the position of the file is indeterminate 20because of previous error conditions, the variable becomes undefined. 219.9.1.22 POSITION= specifier in the INQUIRE statement 22The scalar-default-char-variable in the POSITION= specifier is assigned the value REWIND if the file 23is connected by an OPEN statement for positioning at its initial point, APPEND if the file is connected 24for positioning before its endfile record or at its terminal point, and ASIS if the file is connected without 25changing its position. If there is no connection or if the file is connected for direct access, the scalar- 26default-char-variable is assigned the value UNDEFINED. If the file has been repositioned since the 27connection, the scalar-default-char-variable is assigned a processor-dependent value, which shall not be 28REWIND unless the file is positioned at its initial point and shall not be APPEND unless the file is 29positioned so that its endfile record is the next record or at its terminal point if it has no endfile record. 309.9.1.23 READ= specifier in the INQUIRE statement 31The scalar-default-char-variable in the READ= specifier is assigned the value YES if READ is included 32in the set of allowed actions for the file, NO if READ is not included in the set of allowed actions for 214 MAY 2004 WORKING DRAFT J3/04-007 1the file, and UNKNOWN if the processor is unable to determine whether or not READ is included in 2the set of allowed actions for the file. 39.9.1.24 READWRITE= specifier in the INQUIRE statement 4The scalar-default-char-variable in the READWRITE= specifier is assigned the value YES if READ- 5WRITE is included in the set of allowed actions for the file, NO if READWRITE is not included in the 6set of allowed actions for the file, and UNKNOWN if the processor is unable to determine whether or 7not READWRITE is included in the set of allowed actions for the file. 89.9.1.25 RECL= specifier in the INQUIRE statement 9The scalar-int-variable in the RECL= specifier is assigned the value of the record length of a file con- 10nected for direct access, or the value of the maximum record length for a file connected for sequential 11access. If the file is connected for formatted input/output, the length is the number of characters for all 12records that contain only characters of type default character. If the file is connected for unformatted 13input/output, the length is measured in file storage units. If there is no connection, or if the connection 14is for stream access, the scalar-int-variable becomes undefined. 159.9.1.26 ROUND= specifier in the INQUIRE statement 16The scalar-default-char-variable in the ROUND= specifier is assigned the value UP, DOWN, ZERO, 17NEAREST, COMPATIBLE, or PROCESSOR DEFINED, corresponding to the I/O rounding mode in 18effect for a connection for formatted input/output. If there is no connection or if the connection is not 19for formatted input/output, the scalar-default-char-variable is assigned the value UNDEFINED. The 20processor shall return the value PROCESSOR DEFINED only if the I/O rounding mode currently in 21effect behaves differently than the UP, DOWN, ZERO, NEAREST, and COMPATIBLE modes. 229.9.1.27 SEQUENTIAL= specifier in the INQUIRE statement 23The scalar-default-char-variable in the SEQUENTIAL= specifier is assigned the value YES if SEQUEN- 24TIAL is included in the set of allowed access methods for the file, NO if SEQUENTIAL is not included 25in the set of allowed access methods for the file, and UNKNOWN if the processor is unable to determine 26whether or not SEQUENTIAL is included in the set of allowed access methods for the file. 279.9.1.28 SIGN= specifier in the INQUIRE statement 28The scalar-default-char-variable in the SIGN= specifier is assigned the value PLUS, SUPPRESS, or 29PROCESSOR DEFINED, corresponding to the sign mode in effect for a connection for formatted in- 30put/output. If there is no connection, or if the connection is not for formatted input/output, the 31scalar-default-char-variable is assigned the value UNDEFINED. 329.9.1.29 SIZE= specifier in the INQUIRE statement 33The scalar-int-variable in the SIZE= specifier is assigned the size of the file in file storage units. If the 34file size cannot be determined, the variable is assigned the value -1. 35For a file that may be connected for stream access, the file size is the number of the highest-numbered 36file storage unit in the file. 37For a file that may be connected for sequential or direct access, the file size may be different from the 38number of storage units implied by the data in the records; the exact relationship is processor-dependent. 215 J3/04-007 WORKING DRAFT MAY 2004 19.9.1.30 STREAM= specifier in the INQUIRE statement 2The scalar-default-char-variable in the STREAM= specifier is assigned the value YES if STREAM is 3included in the set of allowed access methods for the file, NO if STREAM is not included in the set of 4allowed access methods for the file, and UNKNOWN if the processor is unable to determine whether or 5not STREAM is included in the set of allowed access methods for the file. 69.9.1.31 UNFORMATTED= specifier in the INQUIRE statement 7The scalar-default-char-variable in the UNFORMATTED= specifier is assigned the value YES if UN- 8FORMATTED is included in the set of allowed forms for the file, NO if UNFORMATTED is not included 9in the set of allowed forms for the file, and UNKNOWN if the processor is unable to determine whether 10or not UNFORMATTED is included in the set of allowed forms for the file. 119.9.1.32 WRITE= specifier in the INQUIRE statement 12The scalar-default-char-variable in the WRITE= specifier is assigned the value YES if WRITE is included 13in the set of allowed actions for the file, NO if WRITE is not included in the set of allowed actions for 14the file, and UNKNOWN if the processor is unable to determine whether or not WRITE is included in 15the set of allowed actions for the file. 169.9.2 Restrictions on inquiry specifiers 17The inquire-spec-list in an INQUIRE by file statement shall contain exactly one FILE= specifier and 18shall not contain a UNIT= specifier. The inquire-spec-list in an INQUIRE by unit statement shall 19contain exactly one UNIT= specifier and shall not contain a FILE= specifier. The unit specified need 20not exist or be connected to a file. If it is connected to a file, the inquiry is being made about the 21connection and about the file connected. 229.9.3 Inquire by output list 23The inquire by output list form of the INQUIRE statement has only an IOLENGTH= specifier and an 24output list. 25The scalar-int-variable in the IOLENGTH= specifier is assigned the processor-dependent number of file 26storage units that would be required to store the data of the output list in an unformatted file. The 27value shall be suitable as a RECL= specifier in an OPEN statement that connects a file for unformatted 28direct access when there are input/output statements with the same input/output list. 29The output list in an INQUIRE statement shall not contain any derived-type list items that require a 30user-defined derived-type input/output procedure as described in section 9.5.2. If a derived-type list 31item appears in the output list, the value returned for the IOLENGTH= specifier assumes that no 32user-defined derived-type input/output procedure will be invoked. 339.10 Error, end-of-record, and end-of-file conditions 34The set of input/output error conditions is processor dependent. 35An end-of-record condition occurs when a nonadvancing input statement attempts to transfer data 36from a position beyond the end of the current record, unless the file is a stream file and the current 37record is at the end of the file (an end-of-file condition occurs instead). 38An end-of-file condition occurs in the following cases: 39 (1) When an endfile record is encountered during the reading of a file connected for sequential 40 access. 216 MAY 2004 WORKING DRAFT J3/04-007 1 (2) When an attempt is made to read a record beyond the end of an internal file. 2 (3) When an attempt is made to read beyond the end of a stream file. 3An end-of-file condition may occur at the beginning of execution of an input statement. An end-of-file 4condition also may occur during execution of a formatted input statement when more than one record 5is required by the interaction of the input list and the format. An end-of-file condition also may occur 6during execution of a stream input statement. 79.10.1 Error conditions and the ERR= specifier 8If an error condition occurs during execution of an input/output statement, the position of the file 9becomes indeterminate. 10If an error condition occurs during execution of an input/output statement that contains neither an 11ERR= nor IOSTAT= specifier, execution of the program is terminated. If an error condition occurs 12during execution of an input/output statement that contains either an ERR= specifier or an IOSTAT= 13specifier then 14 (1) Processing of the input/output list, if any, terminates, 15 (2) If the statement is a data transfer statement or the error occurs during a wait operation, 16 all do-variables in the statement that initiated the transfer become undefined, 17 (3) If an IOSTAT= specifier appears, the scalar-int-variable in the IOSTAT= specifier becomes 18 defined as specified in 9.10.4, 19 (4) If an IOMSG= specifier appears, the iomsg-variable becomes defined as specified in 9.10.5, 20 (5) If the statement is a READ statement and it contains a SIZE= specifier, the scalar-int- 21 variable in the SIZE= specifier becomes defined as specified in 9.5.1.14, 22 (6) If the statement is a READ statement or the error condition occurs in a wait operation for 23 a transfer initiated by a READ statement, all input items or namelist group objects in the 24 statement that initiated the transfer become undefined, and 25 (7) If an ERR= specifier appears, execution continues with the statement labeled by the label 26 in the ERR= specifier. 279.10.2 End-of-file condition and the END= specifier 28If an end-of-file condition occurs during execution of an input/output statement that contains neither 29an END= specifier nor an IOSTAT= specifier, execution of the program is terminated. If an end-of-file 30condition occurs during execution of an input/output statement that contains either an END= specifier 31or an IOSTAT= specifier, and an error condition does not occur then 32 (1) Processing of the input list, if any, terminates, 33 (2) If the statement is a data transfer statement or the error occurs during a wait operation, 34 all do-variables in the statement that initiated the transfer become undefined, 35 (3) If the statement is a READ statement or the end-of-file condition occurs in a wait operation 36 for a transfer initiated by a READ statement, all input list items or namelist group objects 37 in the statement that initiated the transfer become undefined, 38 (4) If the file specified in the input statement is an external record file, it is positioned after the 39 endfile record, 40 (5) If an IOSTAT= specifier appears, the scalar-int-variable in the IOSTAT= specifier becomes 41 defined as specified in 9.10.4, 42 (6) If an IOMSG= specifier appears, the iomsg-variable becomes defined as specified in 9.10.5, 43 and 44 (7) If an END= specifier appears, execution continues with the statement labeled by the label 45 in the END= specifier. 217 J3/04-007 WORKING DRAFT MAY 2004 19.10.3 End-of-record condition and the EOR= specifier 2If an end-of-record condition occurs during execution of an input/output statement that contains neither 3an EOR= specifier nor an IOSTAT= specifier, execution of the program is terminated. If an end-of- 4record condition occurs during execution of an input/output statement that contains either an EOR= 5specifier or an IOSTAT= specifier, and an error condition does not occur then 6 (1) If the pad mode has the value YES, the record is padded with blanks to satisfy the input 7 list item (9.5.3.4.2) and corresponding data edit descriptor that requires more characters 8 than the record contains. If the pad mode has the value NO, the input list item becomes 9 undefined. 10 (2) Processing of the input list, if any, terminates, 11 (3) If the statement is a data transfer statement or the error occurs during a wait operation, 12 all do-variables in the statement that initiated the transfer become undefined, 13 (4) The file specified in the input statement is positioned after the current record, 14 (5) If an IOSTAT= specifier appears, the scalar-int-variable in the IOSTAT= specifier becomes 15 defined as specified in 9.10.4, 16 (6) If an IOMSG= specifier appears, the iomsg-variable becomes defined as specified in 9.10.5, 17 (7) If a SIZE= specifier appears, the scalar-int-variable in the SIZE= specifier becomes defined 18 as specified in (9.5.1.14), and 19 (8) If an EOR= specifier appears, execution continues with the statement labeled by the label 20 in the EOR= specifier. 219.10.4 IOSTAT= specifier 22Execution of an input/output statement containing the IOSTAT= specifier causes the scalar-int-variable 23in the IOSTAT= specifier to become defined with 24 (1) A zero value if neither an error condition, an end-of-file condition, nor an end-of-record 25 condition occurs, 26 (2) A processor-dependent positive integer value if an error condition occurs, 27 (3) The processor-dependent negative integer value of the constant IOSTAT END (13.8.2.5) if 28 an end-of-file condition occurs and no error condition occurs, or 29 (4) The processor-dependent negative integer value of the constant IOSTAT EOR (13.8.2.6) if 30 an end-of-record condition occurs and no error condition or end-of-file condition occurs. NOTE 9.65 An end-of-file condition may occur only for sequential or stream input and an end-of-record con- dition may occur only for nonadvancing input. Consider the example: READ (FMT = "(E8.3)", UNIT = 3, IOSTAT = IOSS) X IF (IOSS < 0) THEN ! Perform end-of-file processing on the file connected to unit 3. CALL END_PROCESSING ELSE IF (IOSS > 0) THEN ! Perform error processing CALL ERROR_PROCESSING END IF 218 MAY 2004 WORKING DRAFT J3/04-007 19.10.5 IOMSG= specifier 2If an error, end-of-file, or end-of-record condition occurs during execution of an input/output statement, 3the processor shall assign an explanatory message to iomsg-variable. If no such condition occurs, the 4processor shall not change the value of iomsg-variable. 59.11 Restrictions on input/output statements 6If a unit, or a file connected to a unit, does not have all of the properties required for the execution of 7certain input/output statements, those statements shall not refer to the unit. 8An input/output statement that is executed while another input/output statement is being executed is 9called a recursive input/output statement. 10A recursive input/output statement shall not identify an external unit except that a child data transfer 11statement may identify its parent data transfer statement external unit. 12An input/output statement shall not cause the value of any established format specification to be 13modified. 14A recursive input/output statement shall not modify the value of any internal unit except that a recursive 15WRITE statement may modify the internal unit identified by that recursive WRITE statement. 16The value of a specifier in an input/output statement shall not depend on any input-item, io-implied- 17do do-variable, or on the definition or evaluation of any other specifier in the io-control-spec-list or 18inquire-spec-list in that statement. 19The value of any subscript or substring bound of a variable that appears in a specifier in an input/output 20statement shall not depend on any input-item, io-implied-do do-variable, or on the definition or evalua- 21tion of any other specifier in the io-control-spec-list or inquire-spec-list in that statement. 22In a data transfer statement, the variable specified in an IOSTAT=, IOMSG=, or SIZE= specifier, if 23any, shall not be associated with any entity in the data transfer input/output list (9.5.2) or namelist- 24group-object-list, nor with a do-variable of an io-implied-do in the data transfer input/output list. 25In a data transfer statement, if a variable specified in an IOSTAT=, IOMSG=, or SIZE= specifier is an 26array element reference, its subscript values shall not be affected by the data transfer, the io-implied-do 27processing, or the definition or evaluation of any other specifier in the io-control-spec-list. 28A variable that may become defined or undefined as a result of its use in a specifier in an INQUIRE 29statement, or any associated entity, shall not appear in another specifier in the same INQUIRE statement. 30A STOP statement shall not be executed during execution of an input/output statement. NOTE 9.66 Restrictions on the evaluation of expressions (7.1.8) prohibit certain side effects. 219 J3/04-007 WORKING DRAFT MAY 2004 220 MAY 2004 WORKING DRAFT J3/04-007 1Section 10: Input/output editing 2A format used in conjunction with an input/output statement provides information that directs the 3editing between the internal representation of data and the characters of a sequence of formatted records. 4A FMT= specifier (9.5.1.1) in an input/output statement may refer to a FORMAT statement or to a 5character expression that contains a format specification. A format specification provides explicit editing 6information. The FMT= specifier alternatively may be an asterisk (*), which indicates list-directed 7formatting (10.9). Namelist formatting (10.10) may be indicated by specifying a namelist-group-name 8instead of a format. 910.1 Explicit format specification methods 10Explicit format specification may be given 11 (1) In a FORMAT statement or 12 (2) In a character expression. 1310.1.1 FORMAT statement 14R1001 format-stmt is FORMAT format-specification 15R1002 format-specification is ( [ format-item-list ] ) 16C1001 (R1001) The format-stmt shall be labeled. 17C1002 (R1002) The comma used to separate format-items in a format-item-list may be omitted 18 (1) Between a P edit descriptor and an immediately following F, E, EN, ES, D, or G edit 19 descriptor (10.7.5), possibly preceded by a repeat specifier, 20 (2) Before a slash edit descriptor when the optional repeat specification is not present (10.7.2), 21 (3) After a slash edit descriptor, or 22 (4) Before or after a colon edit descriptor (10.7.3) 23Blank characters may precede the initial left parenthesis of the format specification. Additional blank 24characters may appear at any point within the format specification, with no effect on the interpretation 25of the format specification, except within a character string edit descriptor (10.8). NOTE 10.1 Examples of FORMAT statements are: 5 FORMAT (1PE12.4, I10) 9 FORMAT (I12, /, ' Dates: ', 2 (2I3, I5)) 2610.1.2 Character format specification 27A character expression used as a format in a formatted input/output statement shall evaluate to a 28character string whose leading part is a valid format specification. 221 J3/04-007 WORKING DRAFT MAY 2004 NOTE 10.2 The format specification begins with a left parenthesis and ends with a right parenthesis. 1All character positions up to and including the final right parenthesis of the format specification shall be 2defined at the time the input/output statement is executed, and shall not become redefined or undefined 3during the execution of the statement. Character positions, if any, following the right parenthesis that 4ends the format specification need not be defined and may contain any character data with no effect on 5the interpretation of the format specification. 6If the format is a character array, it is treated as if all of the elements of the array were specified in array 7element order and were concatenated. However, if a format is a character array element, the format 8specification shall be entirely within that array element. NOTE 10.3 If a character constant is used as a format in an input/output statement, care shall be taken that the value of the character constant is a valid format specification. In particular, if a format specification delimited by apostrophes contains a character constant edit descriptor delimited with apostrophes, two apostrophes shall be written to delimit the edit descriptor and four apostrophes shall be written for each apostrophe that occurs within the edit descriptor. For example, the text: 2 ISN'T 3 may be written by various combinations of output statements and format specifications: WRITE (6, 100) 2, 3 100 FORMAT (1X, I1, 1X, 'ISN''T', 1X, I1) WRITE (6, '(1X, I1, 1X, ''ISN''''T'', 1X, I1)') 2, 3 WRITE (6, '(A)') ' 2 ISN''T 3' Doubling of internal apostrophes usually can be avoided by using quotation marks to delimit the format specification and doubling of internal quotation marks usually can be avoided by using apostrophes as delimiters. 910.2 Form of a format item list 10R1003 format-item is [ r ] data-edit-desc 11 or control-edit-desc 12 or char-string-edit-desc 13 or [ r ] ( format-item-list ) 14R1004 r is int-literal-constant 15C1003 (R1004) r shall be positive. 16C1004 (R1004) r shall not have a kind parameter specified for it. 17The integer literal constant r is called a repeat specification. 1810.2.1 Edit descriptors 19An edit descriptor is a data edit descriptor, a control edit descriptor, or a character string 20edit descriptor. 222 MAY 2004 WORKING DRAFT J3/04-007 1R1005 data-edit-desc is I w [ . m ] 2 or B w [ . m ] 3 or O w [ . m ] 4 or Z w [ . m ] 5 or F w . d 6 or E w . d [ E e ] 7 or EN w . d [ E e ] 8 or ES w . d [ E e ] 9 or G w . d [ E e ] 10 or L w 11 or A [ w ] 12 or D w . d 13 or DT [ char-literal-constant ] [ ( v-list ) ] 14R1006 w is int-literal-constant 15R1007 m is int-literal-constant 16R1008 d is int-literal-constant 17R1009 e is int-literal-constant 18R1010 v is signed-int-literal-constant 19C1005 (R1009) e shall be positive. 20C1006 (R1006) w shall be zero or positive for the I, B, O, Z, and F edit descriptors. w shall be positive 21 for all other edit descriptors. 22C1007 (R1005) w, m, d, e, and v shall not have kind parameters specified for them. 23C1008 (R1005) The char-literal-constant in the DT edit descriptor shall not have a kind parameter 24 specified for it. 25I, B, O, Z, F, E, EN, ES, G, L, A, D, and DT indicate the manner of editing. 26R1011 control-edit-desc is position-edit-desc 27 or [ r ] / 28 or : 29 or sign-edit-desc 30 or k P 31 or blank-interp-edit-desc 32 or round-edit-desc 33 or decimal-edit-desc 34R1012 k is signed-int-literal-constant 35C1009 (R1012) k shall not have a kind parameter specified for it. 36In k P, k is called the scale factor. 37R1013 position-edit-desc is T n 38 or TL n 39 or TR n 40 or n X 41R1014 n is int-literal-constant 42C1010 (R1014) n shall be positive. 43C1011 (R1014) n shall not have a kind parameter specified for it. 44R1015 sign-edit-desc is SS 45 or SP 223 J3/04-007 WORKING DRAFT MAY 2004 1 or S 2R1016 blank-interp-edit-desc is BN 3 or BZ 4R1017 round-edit-desc is RU 5 or RD 6 or RZ 7 or RN 8 or RC 9 or RP 10R1018 decimal-edit-desc is DC 11 or DP 12T, TL, TR, X, slash, colon, SS, SP, S, P, BN, BZ, RU, RD, RZ, RN, RC, RP, DC, and DP indicate the 13manner of editing. 14R1019 char-string-edit-desc is char-literal-constant 15C1012 (R1019) The char-literal-constant shall not have a kind parameter specified for it. 16Each rep-char in a character string edit descriptor shall be one of the characters capable of representation 17by the processor. 18The character string edit descriptors provide constant data to be output, and are not valid for input. 19The edit descriptors are without regard to case except for the characters in the character constants. 2010.2.2 Fields 21A field is a part of a record that is read on input or written on output when format control encounters 22a data edit descriptor or a character string edit descriptor. The field width is the size in characters of 23the field. 2410.3 Interaction between input/output list and format 25The start of formatted data transfer using a format specification initiates format control (9.5.3.4.2). 26Each action of format control depends on information jointly provided by 27 (1) The next edit descriptor in the format specification and 28 (2) The next effective item in the input/output list, if one exists. 29If an input/output list specifies at least one effective list item, at least one data edit descriptor shall 30exist in the format specification. NOTE 10.4 An empty format specification of the form ( ) may be used only if the input/output list has no effective list items (9.5.3.4). Zero length character items are effective list items, but zero sized arrays and implied DO lists with an iteration count of zero are not. 31A format specification is interpreted from left to right. The exceptions are format items preceded by a 32repeat specification r, and format reversion (described below). 33A format item preceded by a repeat specification is processed as a list of r items, each identical to the 34format item but without the repeat specification and separated by commas. 224 MAY 2004 WORKING DRAFT J3/04-007 NOTE 10.5 An omitted repeat specification is treated in the same way as a repeat specification whose value is one. 1To each data edit descriptor interpreted in a format specification, there corresponds one effective item 2specified by the input/output list (9.5.2), except that an input/output list item of type complex requires 3the interpretation of two F, E, EN, ES, D, or G edit descriptors. For each control edit descriptor or 4character edit descriptor, there is no corresponding item specified by the input/output list, and format 5control communicates information directly with the record. 6Whenever format control encounters a data edit descriptor in a format specification, it determines 7whether there is a corresponding effective item specified by the input/output list. If there is such an 8item, it transmits appropriately edited information between the item and the record, and then format 9control proceeds. If there is no such item, format control terminates. 10If format control encounters a colon edit descriptor in a format specification and another effective in- 11put/output list item is not specified, format control terminates. 12If format control encounters the rightmost parenthesis of a complete format specification and another 13effective input/output list item is not specified, format control terminates. However, if another effective 14input/output list item is specified, the file is positioned in a manner identical to the way it is positioned 15when a slash edit descriptor is processed (10.7.2). Format control then reverts to the beginning of the 16format item terminated by the last preceding right parenthesis that is not part of a DT edit descriptor. 17If there is no such preceding right parenthesis, format control reverts to the first left parenthesis of the 18format specification. If any reversion occurs, the reused portion of the format specification shall contain 19at least one data edit descriptor. If format control reverts to a parenthesis that is preceded by a repeat 20specification, the repeat specification is reused. Reversion of format control, of itself, has no effect on 21the changeable modes (9.4.1). NOTE 10.6 Example: The format specification: 10 FORMAT (1X, 2(F10.3, I5)) with an output list of WRITE (10,10) 10.1, 3, 4.7, 1, 12.4, 5, 5.2, 6 produces the same output as the format specification: 10 FORMAT (1X, F10.3, I5, F10.3, I5/F10.3, I5, F10.3, I5) 2210.4 Positioning by format control 23After each data edit descriptor or character string edit descriptor is processed, the file is positioned after 24the last character read or written in the current record. 25After each T, TL, TR, or X edit descriptor is processed, the file is positioned as described in 10.7.1. 26After each slash edit descriptor is processed, the file is positioned as described in 10.7.2. 27During formatted stream output, processing of an A edit descriptor may cause file positioning to occur 28(10.6.3). 225 J3/04-007 WORKING DRAFT MAY 2004 1If format control reverts as described in 10.3, the file is positioned in a manner identical to the way it is 2positioned when a slash edit descriptor is processed (10.7.2). 3During a read operation, any unprocessed characters of the current record are skipped whenever the 4next record is read. 510.5 Decimal symbol 6The decimal symbol is the character that separates the whole and fractional parts in the decimal 7representation of a real number in an internal or external file. When the decimal edit mode is POINT, 8the decimal symbol is a decimal point. When the decimal edit mode is COMMA, the decimal symbol is 9a comma. 1010.6 Data edit descriptors 11Data edit descriptors cause the conversion of data to or from its internal representation; during formatted 12stream output, the A data edit descriptor may also cause file positioning. On input, the specified variable 13becomes defined unless an error condition, an end-of-file condition, or an end-of-record condition occurs. 14On output, the specified expression is evaluated. 15During input from a Unicode file, 16 (1) characters in the record that correspond to an ASCII character variable shall have a position 17 in the ISO 10646 character type collating sequence of 127 or less, and 18 (2) characters in the record that correspond to a default character variable shall be representable 19 in the default character type. 20During input from a non-Unicode file, 21 (1) characters in the record that correspond to a character variable shall have the kind of the 22 character variable, and 23 (2) characters in the record that correspond to a numeric or logical variable shall be of default 24 character type. 25During output to a Unicode file, all characters transmitted to the record are of ISO 10646 character 26type. If a character input/output list item or character string edit descriptor contains a character that 27is not representable in the ISO 10646 character type, the result is processor-dependent. 28During output to a non-Unicode file, characters transmitted to the record as a result of processing a 29character string edit descriptor or as a result of evaluating a numeric, logical, or default character data 30entity, are of type default character. 3110.6.1 Numeric editing 32The I, B, O, Z, F, E, EN, ES, D, and G edit descriptors may be used to specify the input/output of 33integer, real, and complex data. The following general rules apply: 34 (1) On input, leading blanks are not significant. When the input field is not an IEEE excep- 35 tional specification (10.6.1.2.1), the interpretation of blanks, other than leading blanks, is 36 determined by the blank interpretation mode (10.7.6). Plus signs may be omitted. A field 37 containing only blanks is considered to be zero. 38 (2) On input, with F, E, EN, ES, D, and G editing, a decimal symbol appearing in the input 39 field overrides the portion of an edit descriptor that specifies the decimal symbol location. 40 The input field may have more digits than the processor uses to approximate the value of 41 the datum. 226 MAY 2004 WORKING DRAFT J3/04-007 1 (3) On output with I, F, E, EN, ES, D, and G editing, the representation of a positive or zero 2 internal value in the field may be prefixed with a plus sign, as controlled by the S, SP, and 3 SS edit descriptors or the processor. The representation of a negative internal value in the 4 field shall be prefixed with a minus sign. 5 (4) On output, the representation is right justified in the field. If the number of characters 6 produced by the editing is smaller than the field width, leading blanks are inserted in the 7 field. 8 (5) On output, if the number of characters produced exceeds the field width or if an exponent 9 exceeds its specified length using the Ew.d Ee, ENw.d Ee, ESw.d Ee, or Gw.d Ee edit 10 descriptor, the processor shall fill the entire field of width w with asterisks. However, 11 the processor shall not produce asterisks if the field width is not exceeded when optional 12 characters are omitted. NOTE 10.7 When an SP edit descriptor is in effect, a plus sign is not optional. 13 (6) On output, with I, B, O, Z, and F editing, the specified value of the field width w may be 14 zero. In such cases, the processor selects the smallest positive actual field width that does 15 not result in a field filled with asterisks. The specified value of w shall not be zero on input. 1610.6.1.1 Integer editing 17The Iw, Iw.m, Bw, Bw.m, Ow, Ow.m, Zw, and Zw.m edit descriptors indicate that the field to be edited 18occupies w positions, except when w is zero. When w is zero, the processor selects the field width. On 19input, w shall not be zero. The specified input/output list item shall be of type integer. The G edit 20descriptor also may be used to edit integer data (10.6.4.1.1). 21On input, m has no effect. 22In the input field for the I edit descriptor, the character string shall be a signed-digit-string (R408), 23except for the interpretation of blanks. For the B, O, and Z edit descriptors, the character string shall 24consist of binary, octal, or hexadecimal digits (as in R412, R413, R414) in the respective input field. The 25lower-case hexadecimal digits a through f in a hexadecimal input field are equivalent to the corresponding 26upper-case hexadecimal digits. 27The output field for the Iw edit descriptor consists of zero or more leading blanks followed by a minus 28sign if the internal value is negative, or an optional plus sign otherwise, followed by the magnitude of 29the internal value as a digit-string without leading zeros. NOTE 10.8 A digit-string always consists of at least one digit. 30The output field for the Bw, Ow, and Zw descriptors consists of zero or more leading blanks followed by 31the internal value in a form identical to the digits of a binary, octal, or hexadecimal constant, respectively, 32with the same value and without leading zeros. NOTE 10.9 A binary, octal, or hexadecimal constant always consists of at least one digit. 33The output field for the Iw.m, Bw.m, Ow.m, and Zw.m edit descriptor is the same as for the Iw, Bw, 34Ow, and Zw edit descriptor, respectively, except that the digit-string consists of at least m digits. If 35necessary, sufficient leading zeros are included to achieve the minimum of m digits. The value of m shall 36not exceed the value of w, except when w is zero. If m is zero and the internal value is zero, the output 37field consists of only blank characters, regardless of the sign control in effect. When m and w are both 227 J3/04-007 WORKING DRAFT MAY 2004 1zero, and the internal value is zero, one blank character is produced. 210.6.1.2 Real and complex editing 3The F, E, EN, ES, and D edit descriptors specify the editing of real and complex data. An input/output 4list item corresponding to an F, E, EN, ES, or D edit descriptor shall be real or complex. The G edit 5descriptor also may be used to edit real and complex data (10.6.4.1.2). 6A lower-case letter is equivalent to the corresponding upper-case letter in an IEEE exceptional specifi- 7cation or the exponent in a numeric input field. 810.6.1.2.1 F editing 9The Fw.d edit descriptor indicates that the field occupies w positions, the fractional part of which 10consists of d digits. When w is zero, the processor selects the field width. On input, w shall not be zero. 11The input field is either an IEEE exceptional specification or consists of an optional sign, followed by a 12string of one or more digits optionally containing a decimal symbol, including any blanks interpreted as 13zeros. The d has no effect on input if the input field contains a decimal symbol. If the decimal symbol 14is omitted, the rightmost d digits of the string, with leading zeros assumed if necessary, are interpreted 15as the fractional part of the value represented. The string of digits may contain more digits than a 16processor uses to approximate the value. The basic form may be followed by an exponent of one of the 17following forms: 18 (1) A sign followed by a digit-string 19 (2) E followed by zero or more blanks, followed by a signed-digit-string 20 (3) D followed by zero or more blanks, followed by a signed-digit-string 21An exponent containing a D is processed identically to an exponent containing an E. NOTE 10.10 If the input field does not contain an exponent, the effect is as if the basic form were followed by an exponent with a value of -k, where k is the established scale factor (10.7.5). 22An input field that is an IEEE exceptional specification consists of optional blanks, followed by either 23of 24 (1) an optional sign, followed by the string 'INF' or the string 'INFINITY' or 25 (2) an optional sign, followed by the string 'NAN', optionally followed by zero or more alphanu- 26 meric characters enclosed in parentheses, 27optionally followed by blanks. 28The value specified by form (1) is an IEEE infinity; this form shall not be used if the processor does 29not support IEEE infinities for the input variable. The value specified by form (2) is an IEEE NaN; 30this form shall not be used if the processor does not support IEEE NaNs for the input variable. The 31NaN value is a quiet NaN if the only nonblank characters in the field are 'NAN' or 'NAN()'; otherwise, 32the NaN value is processor-dependent. The interpretation of a sign in a NaN input field is processor 33dependent. 34For an internal value that is an IEEE infinity, the output field consists of blanks, if necessary, followed 35by a minus sign for negative infinity or an optional plus sign otherwise, followed by the letters 'Inf' or 36'Infinity', right justified within the field. If w is less than 3, the field is filled with asterisks; otherwise, 37if w is less than 8, 'Inf' is produced. 38For an internal value that is an IEEE NaN, the output field consists of blanks, if necessary, followed by 228 MAY 2004 WORKING DRAFT J3/04-007 1the letters 'NaN' and optionally followed by one to w - 5 alphanumeric processor-dependent characters 2enclosed in parentheses, right justified within the field. If w is less than 3, the field is filled with asterisks. NOTE 10.11 The processor-dependent characters following 'NaN' may convey additional information about that particular NaN. 3For an internal value that is neither an IEEE infinity nor a NaN, the output field consists of blanks, if 4necessary, followed by a minus sign if the internal value is negative, or an optional plus sign otherwise, 5followed by a string of digits that contains a decimal symbol and represents the magnitude of the internal 6value, as modified by the established scale factor and rounded to d fractional digits. Leading zeros are 7not permitted except for an optional zero immediately to the left of the decimal symbol if the magnitude 8of the value in the output field is less than one. The optional zero shall appear if there would otherwise 9be no digits in the output field. 1010.6.1.2.2 E and D editing 11The Ew.d, Dw.d, and Ew.d Ee edit descriptors indicate that the external field occupies w positions, the 12fractional part of which consists of d digits, unless a scale factor greater than one is in effect, and the 13exponent part consists of e digits. The e has no effect on input. 14The form and interpretation of the input field is the same as for Fw.d editing (10.6.1.2.1). 15For an internal value that is an IEEE infinity or NaN, the form of the output field is the same as for 16Fw.d. 17For an internal value that is neither an IEEE infinity nor a NaN, the form of the output field for a scale 18factor of zero is: 19 [ ± ] [0].x1x2 ...xdexp 20where: 21 ± signifies a plus sign or a minus sign. 22 . signifies a decimal symbol (10.5). 23 x1x2 . . . xd are the d most significant digits of the internal value after rounding. 24 exp is a decimal exponent having one of the following forms: Edit Absolute Value Form of Descriptor of Exponent Exponent Ew.d |exp| 99 E±z1z2 or ±0z1z2 99 < |exp| 999 ±z1z2z3 Ew.d Ee |exp| 10e - 1 E±z1z2 ...ze Dw.d |exp| 99 D±z1z2 or E±z1z2 or ±0z1z2 99 < |exp| 999 ±z1z2z3 25 where each z is a digit. 26The sign in the exponent is produced. A plus sign is produced if the exponent value is zero. The edit 27descriptor forms Ew.d and Dw.d shall not be used if |exp| > 999. 28The scale factor k controls the decimal normalization (10.2.1, 10.7.5). If -d < k 0, the output field 29contains exactly |k| leading zeros and d-|k| significant digits after the decimal symbol. If 0 < k < d+2, 30the output field contains exactly k significant digits to the left of the decimal symbol and d - k + 1 229 J3/04-007 WORKING DRAFT MAY 2004 1significant digits to the right of the decimal symbol. Other values of k are not permitted. 210.6.1.2.3 EN editing 3The EN edit descriptor produces an output field in the form of a real number in engineering notation 4such that the decimal exponent is divisible by three and the absolute value of the significand (R418) is 5greater than or equal to 1 and less than 1000, except when the output value is zero. The scale factor 6has no effect on output. 7The forms of the edit descriptor are ENw.d and ENw.d Ee indicating that the external field occupies w 8positions, the fractional part of which consists of d digits and the exponent part consists of e digits. 9The form and interpretation of the input field is the same as for Fw.d editing (10.6.1.2.1). 10For an internal value that is an IEEE infinity or NaN, the form of the output field is the same as for 11Fw.d. 12For an internal value that is neither an IEEE infinity nor a NaN, the form of the output field is: 13 [ ± ] yyy . x1x2 ...xdexp 14where: 15 ± signifies a plus sign or a minus sign. 16 yyy are the 1 to 3 decimal digits representative of the most significant digits of the internal 17 value after rounding (yyy is an integer such that 1 yyy < 1000 or, if the output value is 18 zero, yyy = 0). 19 . signifies a decimal symbol (10.5). 20 x1x2 . . . xd are the d next most significant digits of the internal value after rounding. 21 exp is a decimal exponent, divisible by three, of one of the following forms: Edit Absolute Value Form of Descriptor of Exponent Exponent ENw.d |exp| 99 E±z1z2 or ±0z1z2 99 < |exp| 999 ±z1z2z3 ENw.d Ee |exp| 10e - 1 E±z1z2 ...ze 22 where each z is a digit. 23The sign in the exponent is produced. A plus sign is produced if the exponent value is zero. The edit 24descriptor form ENw.d shall not be used if |exp| > 999. NOTE 10.12 Examples: Internal Value Output field Using SS, EN12.3 6.421 6.421E+00 -.5 -500.000E-03 .00217 2.170E-03 4721.3 4.721E+03 2510.6.1.2.4 ES editing 26The ES edit descriptor produces an output field in the form of a real number in scientific notation such 27that the absolute value of the significand (R418) is greater than or equal to 1 and less than 10, except 230 MAY 2004 WORKING DRAFT J3/04-007 1when the output value is zero. The scale factor has no effect on output. 2The forms of the edit descriptor are ESw.d and ESw.d Ee indicating that the external field occupies w 3positions, the fractional part of which consists of d digits and the exponent part consists of e digits. 4The form and interpretation of the input field is the same as for Fw.d editing (10.6.1.2.1). 5For an internal value that is an IEEE infinity or NaN, the form of the output field is the same as for 6Fw.d. 7For an internal value that is neither an IEEE infinity nor a NaN, the form of the output field is: 8 [ ± ] y . x1x2 ...xdexp 9where: 10 ± signifies a plus sign or a minus sign. 11 y is a decimal digit representative of the most significant digit of the internal value after 12 rounding. 13 . signifies a decimal symbol (10.5). 14 x1x2 . . . xd are the d next most significant digits of the internal value after rounding. 15 exp is a decimal exponent having one of the following forms: Edit Absolute Value Form of Descriptor of Exponent Exponent ESw.d |exp| 99 E±z1z2 or ±0z1z2 99 < |exp| 999 ±z1z2z3 ESw.d Ee |exp| 10e - 1 E±z1z2 ...ze 16 where each z is a digit. 17The sign in the exponent is produced. A plus sign is produced if the exponent value is zero. The edit 18descriptor form ESw.d shall not be used if |exp| > 999. NOTE 10.13 Examples: Internal Value Output field Using SS, ES12.3 6.421 6.421E+00 -.5 -5.000E-01 .00217 2.170E-03 4721.3 4.721E+03 1910.6.1.2.5 Complex editing 20A complex datum consists of a pair of separate real data. The editing of a scalar datum of complex type 21is specified by two edit descriptors each of which specifies the editing of real data. The first of the edit 22descriptors specifies the real part; the second specifies the imaginary part. The two edit descriptors may 23be different. Control and character string edit descriptors may be processed between the edit descriptor 24for the real part and the edit descriptor for the imaginary part. 2510.6.1.2.6 Rounding mode 26The rounding mode can be specified by an OPEN statement (9.4.1), a data transfer input/output 27statement (9.5.1.12), or an edit descriptor (10.7.7). 231 J3/04-007 WORKING DRAFT MAY 2004 1In what follows, the term "decimal value" means the exact decimal number as given by the character 2string, while the term "internal value" means the number actually stored (typically in binary form) in 3the processor. For example, in dealing with the decimal constant 0.1, the decimal value is the exact 4mathematical quantity 1/10, which has no exact representation on most processors. Formatted output 5of real data involves conversion from an internal value to a decimal value; formatted input involves 6conversion from a decimal value to an internal value. 7When the I/O rounding mode is UP, the value resulting from conversion shall be the smallest repre- 8sentable value that is greater than or equal to the original value. When the I/O rounding mode is 9DOWN, the value resulting from conversion shall be the largest representable value that is less than or 10equal to the original value. When the I/O rounding mode is ZERO, the value resulting from conversion 11shall be the value closest to the original value and no greater in magnitude than the original value. When 12the I/O rounding mode is NEAREST, the value resulting from conversion shall be the closer of the two 13nearest representable values if one is closer than the other. If the two nearest representable values are 14equidistant from the original value, it is processor dependent which one of them is chosen. When the 15I/O rounding mode is COMPATIBLE, the value resulting from conversion shall be the closer of the 16two nearest representable values or the value away from zero if halfway between them. When the I/O 17rounding mode is PROCESSOR DEFINED, rounding during conversion shall be a processor dependent 18default mode, which may correspond to one of the other modes. 19On processors that support IEEE rounding on conversions, NEAREST shall correspond to round to 20nearest, as specified in the IEEE International Standard. NOTE 10.14 On processors that support IEEE rounding on conversions, the I/O rounding modes COMPATI- BLE and NEAREST will produce the same results except when the datum is halfway between the two representable values. In that case, NEAREST will pick the even value, but COMPATIBLE will pick the value away from zero. The I/O rounding modes UP, DOWN, and ZERO have the same effect as those specified in the IEEE International Standard for round toward +, round toward -, and round toward 0, respectively. 2110.6.2 Logical editing 22The Lw edit descriptor indicates that the field occupies w positions. The specified input/output list 23item shall be of type logical. The G edit descriptor also may be used to edit logical data (10.6.4.2). 24The input field consists of optional blanks, optionally followed by a period, followed by a T for true or 25F for false. The T or F may be followed by additional characters in the field, which are ignored. 26A lower-case letter is equivalent to the corresponding upper-case letter in a logical input field. NOTE 10.15 The logical constants .TRUE. and .FALSE. are acceptable input forms. 27The output field consists of w - 1 blanks followed by a T or F, depending on whether the internal value 28is true or false, respectively. 2910.6.3 Character editing 30The A[w] edit descriptor is used with an input/output list item of type character. The G edit descriptor 31also may be used to edit character data (10.6.4.3). The kind type parameter of all characters transferred 32and converted under control of one A or G edit descriptor is implied by the kind of the corresponding 33list item. 232 MAY 2004 WORKING DRAFT J3/04-007 1If a field width w is specified with the A edit descriptor, the field consists of w characters. If a field 2width w is not specified with the A edit descriptor, the number of characters in the field is the length of 3the corresponding list item, regardless of the value of the kind type parameter. 4Let len be the length of the input/output list item. If the specified field width w for an A edit descriptor 5corresponding to an input item is greater than or equal to len, the rightmost len characters will be taken 6from the input field. If the specified field width w is less than len, the w characters will appear left 7justified with len-w trailing blanks in the internal value. 8If the specified field width w for an A edit descriptor corresponding to an output item is greater than 9len, the output field will consist of w -len blanks followed by the len characters from the internal value. 10If the specified field width w is less than or equal to len, the output field will consist of the leftmost w 11characters from the internal value. NOTE 10.16 For nondefault character types, the blank padding character is processor dependent. 12If the file is connected for stream access, the output may be split across more than one record if it 13contains newline characters. A newline character is a nonblank character returned by the intrinsic 14function NEW LINE. Beginning with the first character of the output field, each character that is not 15a newline is written to the current record in successive positions; each newline character causes file 16positioning at that point as if by slash editing (the current record is terminated at that point, a new 17empty record is created following the current record, this new record becomes the last and current record 18of the file, and the file is positioned at the beginning of this new record). NOTE 10.17 If the intrinsic function NEW LINE returns a blank character for a particular character kind, then the processor does not support using a character of that kind to cause record termination in a formatted stream file. 1910.6.4 Generalized editing 20The Gw.d and Gw.d Ee edit descriptors are used with an input/output list item of any intrinsic type. 21These edit descriptors indicate that the external field occupies w positions, the fractional part of which 22consists of a maximum of d digits and the exponent part consists of e digits. When these edit descriptors 23are used to specify the input/output of integer, logical, or character data, d and e have no effect. 2410.6.4.1 Generalized numeric editing 25When used to specify the input/output of integer, real, and complex data, the Gw.d and Gw.d Ee edit 26descriptors follow the general rules for numeric editing (10.6.1). NOTE 10.18 The Gw.d Ee edit descriptor follows any additional rules for the Ew.d Ee edit descriptor. 2710.6.4.1.1 Generalized integer editing 28When used to specify the input/output of integer data, the Gw.d and Gw.d Ee edit descriptors follow 29the rules for the Iw edit descriptor (10.6.1.1), except that w shall not be zero. 3010.6.4.1.2 Generalized real and complex editing 31The form and interpretation of the input field is the same as for Fw.d editing (10.6.1.2.1). 233 J3/04-007 WORKING DRAFT MAY 2004 1For an internal value that is an IEEE infinity or NaN, the form of the output field is the same as for 2Fw.d. 3Otherwise, the method of representation in the output field depends on the magnitude of the internal 4value being edited. Let N be the magnitude of the internal value and r be the rounding mode value -1 5defined in the table below. If 0 < N < 0.1 - r × 10-d or N 10d - r, or N is identically 0 and 6d is 0, Gw.d output editing is the same as k PEw.d output editing and Gw.d Ee output editing is 7the same as k PEw.d Ee output editing, where k is the scale factor (10.7.5) currently in effect. If -1 80.1 - r × 10-d N < 10d - r or N is identically 0 and d is not zero, the scale factor has no effect, 9and the value of N determines the editing as follows: Magnitude of Internal Value Equivalent Conversion N = 0 F(w - n).(d - 1), n('b') 0.1 - r × 10-d-1 N < 1 - r × 10-d F(w - n).d, n('b') 1 - r × 10-d N < 10 - r × 10-d +1 F(w - n).(d - 1), n('b') 10 - r × 10-d +1 N < 100 - r × 10-d +2 F(w - n).(d - 2), n('b') · · · · · · 10d-2 - r × 10-2 N < 10d -1 - r × 10-1 F(w - n).1, n('b') 10d-1 - r × 10-1 N < 10d - r F(w - n).0, n('b') 10where b is a blank, n is 4 for Gw.d and e + 2 for Gw.d Ee, and r is defined for each rounding mode as 11follows: I/O Rounding Mode r COMPATIBLE 0.5 0.5 if the higher value is even NEAREST -0.5 if the lower value is even UP 1 DOWN 0 1 if internal value is negative ZERO 0 if internal value is positive 12The value of w - n shall be positive NOTE 10.19 The scale factor has no effect on output unless the magnitude of the datum to be edited is outside the range that permits effective use of F editing. 1310.6.4.2 Generalized logical editing 14When used to specify the input/output of logical data, the Gw.d and Gw.d Ee edit descriptors follow 15the rules for the Lw edit descriptor (10.6.2). 1610.6.4.3 Generalized character editing 17When used to specify the input/output of character data, the Gw.d and Gw.d Ee edit descriptors follow 18the rules for the Aw edit descriptor (10.6.3). 234 MAY 2004 WORKING DRAFT J3/04-007 110.6.5 User-defined derived-type editing 2The DT edit descriptor allows a user-provided procedure to be used instead of the processor's default 3input/output formatting for processing a list item of derived type. 4The DT edit descriptor may include a character literal constant. The character value "DT" concatenated 5with the character literal constant is passed to the user-defined derived-type input/output procedure as 6the iotype argument (9.5.3.7). The v values of the edit descriptor are passed to the user-defined 7derived-type input/output procedure as the v list array argument. NOTE 10.20 For the edit descriptor DT'Link List'(10, 4, 2), iotype is "DTLink List" and v list is (/10, 4, 2/). 8If a derived-type variable or value corresponds to a DT edit descriptor, there shall be an accessible 9interface to a corresponding derived-type input/output procedure for that derived type (9.5.3.7). A DT 10edit descriptor shall not correspond with a list item that is not of a derived type. 1110.7 Control edit descriptors 12A control edit descriptor does not cause the transfer of data or the conversion of data to or from internal 13representation, but may affect the conversions performed by subsequent data edit descriptors. 1410.7.1 Position editing 15The T, TL, TR, and X edit descriptors specify the position at which the next character will be transmitted 16to or from the record. If any character skipped by a T, TL, TR, or X edit descriptor is of type nondefault 17character, and the unit is an internal file of type default character or an external non-Unicode file, the 18result of that position editing is processor dependent. 19The position specified by a T edit descriptor may be in either direction from the current position. On 20input, this allows portions of a record to be processed more than once, possibly with different editing. 21The position specified by an X edit descriptor is forward from the current position. On input, a position 22beyond the last character of the record may be specified if no characters are transmitted from such 23positions. NOTE 10.21 An nX edit descriptor has the same effect as a TRn edit descriptor. 24On output, a T, TL, TR, or X edit descriptor does not by itself cause characters to be transmitted and 25therefore does not by itself affect the length of the record. If characters are transmitted to positions at 26or after the position specified by a T, TL, TR, or X edit descriptor, positions skipped and not previously 27filled are filled with blanks. The result is as if the entire record were initially filled with blanks. 28On output, a character in the record may be replaced. However, a T, TL, TR, or X edit descriptor never 29directly causes a character already placed in the record to be replaced. Such edit descriptors may result 30in positioning such that subsequent editing causes a replacement. 3110.7.1.1 T, TL, and TR editing 32The left tab limit affects file positioning by the T and TL edit descriptors. Immediately prior to 33nonchild data transfer, the left tab limit becomes defined as the character position of the current record 235 J3/04-007 WORKING DRAFT MAY 2004 1or the current position of the stream file. If, during data transfer, the file is positioned to another record, 2the left tab limit becomes defined as character position one of that record. 3The Tn edit descriptor indicates that the transmission of the next character to or from a record is to 4occur at the nth character position of the record, relative to the left tab limit. 5The TLn edit descriptor indicates that the transmission of the next character to or from the record is 6to occur at the character position n characters backward from the current position. However, if n is 7greater than the difference between the current position and the left tab limit, the TLn edit descriptor 8indicates that the transmission of the next character to or from the record is to occur at the left tab 9limit. 10The TRn edit descriptor indicates that the transmission of the next character to or from the record is 11to occur at the character position n characters forward from the current position. NOTE 10.22 The n in a Tn, TLn, or TRn edit descriptor shall be specified and shall be greater than zero. 1210.7.1.2 X editing 13The nX edit descriptor indicates that the transmission of the next character to or from a record is to 14occur at the position n characters forward from the current position. NOTE 10.23 The n in an nX edit descriptor shall be specified and shall be greater than zero. 1510.7.2 Slash editing 16The slash edit descriptor indicates the end of data transfer to or from the current record. 17On input from a file connected for sequential or stream access, the remaining portion of the current 18record is skipped and the file is positioned at the beginning of the next record. This record becomes 19the current record. On output to a file connected for sequential or stream access, a new empty record 20is created following the current record; this new record then becomes the last and current record of the 21file and the file is positioned at the beginning of this new record. 22For a file connected for direct access, the record number is increased by one and the file is positioned 23at the beginning of the record that has that record number, if there is such a record, and this record 24becomes the current record. NOTE 10.24 A record that contains no characters may be written on output. If the file is an internal file or a file connected for direct access, the record is filled with blank characters. An entire record may be skipped on input. 25The repeat specification is optional in the slash edit descriptor. If it is not specified, the default value is 26one. 2710.7.3 Colon editing 28The colon edit descriptor terminates format control if there are no more effective items in the in- 29put/output list (9.5.2). The colon edit descriptor has no effect if there are more effective items in the 30input/output list. 236 MAY 2004 WORKING DRAFT J3/04-007 110.7.4 SS, SP, and S editing 2The SS, SP, and S edit descriptors temporarily change (9.4.1) the sign mode (9.4.5.14, 9.5.1.13) for the 3connection. The edit descriptors SS, SP, and S set the sign mode corresponding to the SIGN= specifier 4values SUPPRESS, PLUS, and PROCESSOR DEFINED, respectively. 5The sign mode controls optional plus characters in numeric output fields. When the sign mode is PLUS, 6the processor shall produce a plus sign in any position that normally contains an optional plus sign. 7When the sign mode is SUPPRESS, the processor shall not produce a plus sign in such positions. When 8the sign mode is PROCESSOR DEFINED, the processor has the option of producing a plus sign or not 9in such positions, subject to 10.6.1(5). 10The SS, SP, and S edit descriptors affect only I, F, E, EN, ES, D, and G editing during the execution of 11an output statement. The SS, SP, and S edit descriptors have no effect during the execution of an input 12statement. 1310.7.5 P editing 14The kP edit descriptor temporarily changes (9.4.1) the scale factor for the connection to k. The scale 15factor affects the editing of F, E, EN, ES, D, and G edit descriptors for numeric quantities. 16The scale factor k affects the appropriate editing in the following manner: 17 (1) On input, with F, E, EN, ES, D, and G editing (provided that no exponent exists in the 18 field) and F output editing, the scale factor effect is that the externally represented number 19 equals the internally represented number multiplied by 10k. 20 (2) On input, with F, E, EN, ES, D, and G editing, the scale factor has no effect if there is an 21 exponent in the field. 22 (3) On output, with E and D editing, the significand (R418) part of the quantity to be produced 23 is multiplied by 10k and the exponent is reduced by k. 24 (4) On output, with G editing, the effect of the scale factor is suspended unless the magnitude 25 of the datum to be edited is outside the range that permits the use of F editing. If the use 26 of E editing is required, the scale factor has the same effect as with E output editing. 27 (5) On output, with EN and ES editing, the scale factor has no effect. 28If UP, DOWN, ZERO, or NEAREST I/O rounding mode is in effect then 29 (1) On input, the scale factor is applied to the external decimal value and then this is converted 30 using the current I/O rounding mode, and 31 (2) On output, the internal value is converted using the current I/O rounding mode and then 32 the scale factor is applied to the converted decimal value. 3310.7.6 BN and BZ editing 34The BN and BZ edit descriptors temporarily change (9.4.1) the blank interpretation mode (9.4.5.4, 359.5.1.5) for the connection. The edit descriptors BN and BZ set the blank interpretation mode corre- 36sponding to the BLANK= specifier values NULL and ZERO, respectively. 37The blank interpretation mode controls the interpretation of nonleading blanks in numeric input fields. 38Such blank characters are interpreted as zeros when the blank interpretation mode has the value ZERO; 39they are ignored when the blank interpretation mode has the value NULL. The effect of ignoring blanks 40is to treat the input field as if blanks had been removed, the remaining portion of the field right justified, 41and the blanks replaced as leading blanks. However, a field containing only blanks has the value zero. 42The blank interpretation mode affects only numeric editing (10.6.1) and generalized numeric editing 43(10.6.4.1) on input. It has no effect on output. 237 J3/04-007 WORKING DRAFT MAY 2004 110.7.7 RU, RD, RZ, RN, RC, and RP editing 2The round edit descriptors temporarily change (9.4.1) the connection's I/O rounding mode (9.4.5.13, 39.5.1.12, 10.6.1.2.6). The round edit descriptors RU, RD, RZ, RN, RC, and RP set the I/O rounding 4mode corresponding to the ROUND= specifier values UP, DOWN, ZERO, NEAREST, COMPATIBLE, 5and PROCESSOR DEFINED, respectively. The I/O rounding mode affects the conversion of real and 6complex values in formatted input/output. It affects only D, E, EN, ES, F, and G editing. 710.7.8 DC and DP editing 8The decimal edit descriptors temporarily change (9.4.1) the decimal edit mode (9.4.5.5, 9.5.1.6) for the 9connection. The edit descriptors DC and DP set the decimal edit mode corresponding to the DECIMAL= 10specifier values COMMA and POINT, respectively. 11The decimal edit mode controls the representation of the decimal symbol (10.5) during conversion of 12real and complex values in formatted input/output. The decimal edit mode affects only D, E, EN, ES, 13F, and G editing. If the mode is COMMA during list-directed input/output, the character used as a 14value separator is a semicolon in place of a comma. 1510.8 Character string edit descriptors 16A character string edit descriptor shall not be used on input. 17The character string edit descriptor causes characters to be written from the enclosed characters of the 18edit descriptor itself, including blanks. For a character string edit descriptor, the width of the field is 19the number of characters between the delimiting characters. Within the field, two consecutive delimiting 20characters are counted as a single character. NOTE 10.25 A delimiter for a character string edit descriptor is either an apostrophe or quote. 2110.9 List-directed formatting 22List-directed input/output allows data editing according to the type of the list item instead of by a 23format specification. It also allows data to be free-field, that is, separated by commas (or semicolons) 24or blanks. 25The characters in one or more list-directed records constitute a sequence of values and value separators. 26The end of a record has the same effect as a blank character, unless it is within a character constant. Any 27sequence of two or more consecutive blanks is treated as a single blank, unless it is within a character 28constant. 29Each value is either a null value or one of the forms: c r*c 30 r* 31where c is a literal constant, optionally signed if integer or real, or an undelimited character constant 32and r is an unsigned, nonzero, integer literal constant. Neither c nor r shall have kind type parameters 33specified. The constant c is interpreted as though it had the same kind type parameter as the corre- 34sponding list item. The r*c form is equivalent to r successive appearances of the constant c, and the 35r* form is equivalent to r successive appearances of the null value. Neither of these forms may contain 36embedded blanks, except where permitted within the constant c. 238 MAY 2004 WORKING DRAFT J3/04-007 1A value separator is 2 (1) A comma optionally preceded by one or more contiguous blanks and optionally followed by 3 one or more contiguous blanks, unless the decimal edit mode is COMMA, in which case a 4 semicolon is used in place of the comma, 5 (2) A slash optionally preceded by one or more contiguous blanks and optionally followed by 6 one or more contiguous blanks, or 7 (3) One or more contiguous blanks between two nonblank values or following the last nonblank 8 value, where a nonblank value is a constant, an r*c form, or an r* form. NOTE 10.26 Although a slash encountered in an input record is referred to as a separator, it actually causes termination of list-directed and namelist input statements; it does not actually separate two values. NOTE 10.27 If no list items are specified in a list-directed input/output statement, one input record is skipped or one empty output record is written. 910.9.1 List-directed input 10Input forms acceptable to edit descriptors for a given type are acceptable for list-directed formatting, 11except as noted below. The form of the input value shall be acceptable for the type of the next effective 12item in the list. Blanks are never used as zeros, and embedded blanks are not permitted in constants, 13except within character constants and complex constants as specified below. 14For the r*c form of an input value, the constant c is interpreted as an undelimited character constant 15if the first list item corresponding to this value is of type default, ASCII, or ISO 10646 character, there 16is a nonblank character immediately after r*, and that character is not an apostrophe or a quotation 17mark; otherwise, c is interpreted as a literal constant. NOTE 10.28 The end of a record has the effect of a blank, except when it appears within a character constant. 18When the next effective item is of type integer, the value in the input record is interpreted as if an Iw 19edit descriptor with a suitable value of w were used. 20When the next effective item is of type real, the input form is that of a numeric input field. A numeric 21input field is a field suitable for F editing (10.6.1.2.1) that is assumed to have no fractional digits unless 22a decimal symbol appears within the field. 23When the next effective item is of type complex, the input form consists of a left parenthesis followed 24by an ordered pair of numeric input fields separated by a separator, and followed by a right parenthesis. 25The first numeric input field is the real part of the complex constant and the second is the imaginary 26part. Each of the numeric input fields may be preceded or followed by any number of blanks and ends of 27records. The separator is a comma if the decimal edit mode is POINT; it is a semicolon if the decimal 28edit mode is COMMA. The end of a record may occur between the real part and the separator or between 29the separator and the imaginary part. 30When the next effective item is of type logical, the input form shall not include value separators among 31the optional characters permitted for L editing. 32When the next effective item is of type character, the input form consists of a possibly delimited sequence 33of zero or more rep-chars whose kind type parameter is implied by the kind of the effective list item. 34Character sequences may be continued from the end of one record to the beginning of the next record, 239 J3/04-007 WORKING DRAFT MAY 2004 1but the end of record shall not occur between a doubled apostrophe in an apostrophe-delimited character 2sequence, nor between a doubled quote in a quote-delimited character sequence. The end of the record 3does not cause a blank or any other character to become part of the character sequence. The character 4sequence may be continued on as many records as needed. The characters blank, comma, semicolon, 5and slash may appear in default, ASCII, or ISO 10646 character sequences. 6If the next effective item is of type default, ASCII, or ISO 10646 character and 7 (1) The character sequence does not contain value separators, 8 (2) The character sequence does not cross a record boundary, 9 (3) The first nonblank character is not a quotation mark or an apostrophe, 10 (4) The leading characters are not digits followed by an asterisk, and 11 (5) The character sequence contains at least one character, 12the delimiting apostrophes or quotation marks are not required. If the delimiters are omitted, the char- 13acter sequence is terminated by the first blank, comma, slash, or end of record; in this case apostrophes 14and quotation marks within the datum are not to be doubled. 15Let len be the length of the next effective item, and let w be the length of the character sequence. If 16len is less than or equal to w, the leftmost len characters of the sequence are transmitted to the next 17effective item. If len is greater than w, the sequence is transmitted to the leftmost w characters of the 18next effective item and the remaining len-w characters of the next effective item are filled with blanks. 19The effect is as though the sequence were assigned to the next effective item in a character assignment 20statement (7.4.1.3). 2110.9.1.1 Null values 22A null value is specified by 23 (1) The r* form, 24 (2) No characters between consecutive value separators, or 25 (3) No characters before the first value separator in the first record read by each execution of a 26 list-directed input statement. NOTE 10.29 The end of a record following any other value separator, with or without separating blanks, does not specify a null value in list-directed input. 27A null value has no effect on the definition status of the next effective item. A null value shall not be 28used for either the real or imaginary part of a complex constant, but a single null value may represent 29an entire complex constant. 30A slash encountered as a value separator during execution of a list-directed input statement causes 31termination of execution of that input statement after the assignment of the previous value. Any 32characters remaining in the current record are ignored. If there are additional items in the input list, 33the effect is as if null values had been supplied for them. Any do-variable in the input list is defined as 34though enough null values had been supplied for any remaining input list items. NOTE 10.30 All blanks in a list-directed input record are considered to be part of some value separator except for the following: (1) Blanks embedded in a character sequence (2) Embedded blanks surrounding the real or imaginary part of a complex constant 240 MAY 2004 WORKING DRAFT J3/04-007 NOTE 10.30 (cont.) (3) Leading blanks in the first record read by each execution of a list-directed input statement, unless immediately followed by a slash or comma NOTE 10.31 List-directed input example: INTEGER I; REAL X (8); CHARACTER (11) P; COMPLEX Z; LOGICAL G ... READ *, I, X, P, Z, G ... The input data records are: 12345,12345,,2*1.5,4* ISN'T_BOB'S,(123,0),.TEXAS$ The results are: Variable Value I 12345 X (1) 12345.0 X (2) unchanged X (3) 1.5 X (4) 1.5 X (5) ­ X (8) unchanged P ISN'T BOB'S Z (123.0,0.0) G true 110.9.2 List-directed output 2The form of the values produced is the same as that required for input, except as noted otherwise. With 3the exception of adjacent undelimited character sequences, the values are separated by one or more 4blanks or by a comma, or a semicolon if the decimal edit mode is comma, optionally preceded by one or 5more blanks and optionally followed by one or more blanks. 6The processor may begin new records as necessary, but the end of record shall not occur within a 7constant except for complex constants and character sequences. The processor shall not insert blanks 8within character sequences or within constants, except for complex constants. 9Logical output values are T for the value true and F for the value false. 10Integer output constants are produced with the effect of an Iw edit descriptor. 11Real constants are produced with the effect of either an F edit descriptor or an E edit descriptor, 12depending on the magnitude x of the value and a range 10d1 x < 10d2, where d1 and d2 are processor- 13dependent integers. If the magnitude x is within this range or is zero, the constant is produced using 140PFw.d; otherwise, 1PEw.d Ee is used. 15For numeric output, reasonable processor-dependent values of w, d, and e are used for each of the 16numeric constants output. 241 J3/04-007 WORKING DRAFT MAY 2004 1Complex constants are enclosed in parentheses with a separator between the real and imaginary parts, 2each produced as defined above for real constants. The separator is a comma if the decimal edit mode is 3POINT; it is a semicolon if the decimal edit mode is COMMA. The end of a record may occur between 4the separator and the imaginary part only if the entire constant is as long as, or longer than, an entire 5record. The only embedded blanks permitted within a complex constant are between the separator and 6the end of a record and one blank at the beginning of the next record. 7Character sequences produced when the delimiter mode has a value of NONE 8 (1) Are not delimited by apostrophes or quotation marks, 9 (2) Are not separated from each other by value separators, 10 (3) Have each internal apostrophe or quotation mark represented externally by one apostrophe 11 or quotation mark, and 12 (4) Have a blank character inserted by the processor at the beginning of any record that begins 13 with the continuation of a character sequence from the preceding record. 14Character sequences produced when the delimiter mode has a value of QUOTE are delimited by quotes, 15are preceded and followed by a value separator, and have each internal quote represented on the external 16medium by two contiguous quotes. 17Character sequences produced when the delimiter mode has a value of APOSTROPHE are delimited 18by apostrophes, are preceded and followed by a value separator, and have each internal apostrophe 19represented on the external medium by two contiguous apostrophes. 20If two or more successive values in an output record have identical values, the processor has the option 21of producing a repeated constant of the form r*c instead of the sequence of identical values. 22Slashes, as value separators, and null values are not produced as output by list-directed formatting. 23Except for continuation of delimited character sequences, each output record begins with a blank char- 24acter. NOTE 10.32 The length of the output records is not specified exactly and may be processor dependent. 2510.10 Namelist formatting 26Namelist input/output allows data editing with NAME=value subsequences. This facilitates documen- 27tation of input and output files and more flexibility on input. 28The characters in one or more namelist records constitute a sequence of name-value subsequences, 29each of which consists of an object designator followed by an equals and followed by one or more values 30and value separators. The equals may optionally be preceded or followed by one or more contiguous 31blanks. The end of a record has the same effect as a blank character, unless it is within a character 32constant. Any sequence of two or more consecutive blanks is treated as a single blank, unless it is within 33a character constant. 34The name may be any name in the namelist-group-object-list (5.4). 35Each value is either a null value (10.10.1.4) or one of the forms c r*c 36 r* 37where c is a literal constant, optionally signed if integer or real, and r is an unsigned, nonzero, integer 242 MAY 2004 WORKING DRAFT J3/04-007 1literal constant. Neither c nor r may have kind type parameters specified. The constant c is interpreted 2as though it had the same kind type parameter as the corresponding list item. The r*c form is equivalent 3to r successive appearances of the constant c, and the r* form is equivalent to r successive null values. 4Neither of these forms may contain embedded blanks, except where permitted within the constant c. 5A value separator for namelist formatting is the same as for list-directed formatting (10.9). 610.10.1 Namelist input 7Input for a namelist input statement consists of 8 (1) Optional blanks and namelist comments, 9 (2) The character & followed immediately by the namelist-group-name as specified in the 10 NAMELIST statement, 11 (3) One or more blanks, 12 (4) A sequence of zero or more name-value subsequences separated by value separators, and 13 (5) A slash to terminate the namelist input. NOTE 10.33 A slash encountered in a namelist input record causes the input statement to terminate. A slash cannot be used to separate two values in a namelist input statement. 14In each name-value subsequence, the name shall be the name of a namelist group object list item with 15an optional qualification and the name with the optional qualification shall not be a zero-sized array, a 16zero-sized array section, or a zero-length character string. The optional qualification, if any, shall not 17contain a vector subscript. 18A group name or object name is without regard to case. 1910.10.1.1 Namelist group object names 20Within the input data, each name shall correspond to a particular namelist group object name. Sub- 21scripts, strides, and substring range expressions used to qualify group object names shall be optionally 22signed integer literal constants with no kind type parameters specified. If a namelist group object is 23an array, the input record corresponding to it may contain either the array name or the designator of 24a subobject of that array, using the syntax of object designators (R603). If the namelist group object 25name is the name of a variable of derived type, the name in the input record may be either the name of 26the variable or the designator of one of its components, indicated by qualifying the variable name with 27the appropriate component name. Successive qualifications may be applied as appropriate to the shape 28and type of the variable represented. 29The order of names in the input records need not match the order of the namelist group object items. 30The input records need not contain all the names of the namelist group object items. The definition 31status of any names from the namelist-group-object-list that do not occur in the input record remains 32unchanged. In the input record, each object name or subobject designator may be preceded and followed 33by one or more optional blanks but shall not contain embedded blanks. 3410.10.1.2 Namelist input values 35The datum c (10.10) is any input value acceptable to format specifications for a given type, except for a 36restriction on the form of input values corresponding to list items of types logical, integer, and character 37as specified in 10.10.1.3. The form of a real or complex value is dependent on the decimal edit mode 38in effect (10.7.8). The form of an input value shall be acceptable for the type of the namelist group 39object list item. The number and forms of the input values that may follow the equals in a name-value 243 J3/04-007 WORKING DRAFT MAY 2004 1subsequence depend on the shape and type of the object represented by the name in the input record. 2When the name in the input record is that of a scalar variable of an intrinsic type, the equals shall 3not be followed by more than one value. Blanks are never used as zeros, and embedded blanks are not 4permitted in constants except within character constants and complex constants as specified in 10.10.1.3. 5The name-value subsequences are evaluated serially, in left-to-right order. A namelist group object 6designator may appear in more than one name-value sequence. 7When the name in the input record represents an array variable or a variable of derived type, the effect 8is as if the variable represented were expanded into a sequence of scalar list items of intrinsic data types, 9in the same way that formatted input/output list items are expanded (9.5.2). Each input value following 10the equals shall then be acceptable to format specifications for the intrinsic type of the list item in the 11corresponding position in the expanded sequence, except as noted in 10.10.1.3. The number of values 12following the equals shall not exceed the number of list items in the expanded sequence, but may be less; 13in the latter case, the effect is as if sufficient null values had been appended to match any remaining list 14items in the expanded sequence. NOTE 10.34 For example, if the name in the input record is the name of an integer array of size 100, at most 100 values, each of which is either a digit string or a null value, may follow the equals; these values would then be assigned to the elements of the array in array element order. 15A slash encountered as a value separator during the execution of a namelist input statement causes 16termination of execution of that input statement after assignment of the previous value. If there are 17additional items in the namelist group object being transferred, the effect is as if null values had been 18supplied for them. 19A namelist comment may appear after any value separator except a slash. A namelist comment is also 20permitted to start in the first nonblank position of an input record except within a character literal 21constant. 22Successive namelist records are read by namelist input until a slash is encountered; the remainder of the 23record is ignored and need not follow the rules for namelist input values. 2410.10.1.3 Namelist group object list items 25When the next effective namelist group object list item is of type real, the input form of the input value 26is that of a numeric input field. A numeric input field is a field suitable for F editing (10.6.1.2.1) that is 27assumed to have no fractional digits unless a decimal symbol appears within the field. 28When the next effective item is of type complex, the input form of the input value consists of a left 29parenthesis followed by an ordered pair of numeric input fields separated by a comma and followed by a 30right parenthesis. The first numeric input field is the real part of the complex constant and the second 31part is the imaginary part. Each of the numeric input fields may be preceded or followed by any number 32of blanks and ends of records. The end of a record may occur between the real part and the comma or 33between the comma and the imaginary part. 34When the next effective item is of type logical, the input form of the input value shall not include equals 35or value separators among the optional characters permitted for L editing (10.6.2). 36When the next effective item is of type integer, the value in the input record is interpreted as if an Iw 37edit descriptor with a suitable value of w were used. 38When the next effective item is of type character, the input form consists of a delimited sequence of zero 39or more rep-chars whose kind type parameter is implied by the kind of the corresponding list item. Such 40a sequence may be continued from the end of one record to the beginning of the next record, but the 244 MAY 2004 WORKING DRAFT J3/04-007 1end of record shall not occur between a doubled apostrophe in an apostrophe-delimited sequence, nor 2between a doubled quote in a quote-delimited sequence. The end of the record does not cause a blank 3or any other character to become part of the sequence. The sequence may be continued on as many 4records as needed. The characters blank, comma, and slash may appear in such character sequences. NOTE 10.35 A character sequence corresponding to a namelist input item of character type shall be delimited either with apostrophes or with quotes. The delimiter is required to avoid ambiguity between undelimited character sequences and object names. The value of the DELIM= specifier, if any, in the OPEN statement for an external file is ignored during namelist input (9.4.5.6). 5Let len be the length of the next effective item, and let w be the length of the character sequence. If 6len is less than or equal to w, the leftmost len characters of the sequence are transmitted to the next 7effective item. If len is greater than w, the constant is transmitted to the leftmost w characters of the 8next effective item and the remaining len-w characters of the next effective item are filled with blanks. 9The effect is as though the sequence were assigned to the next effective item in a character assignment 10statement (7.4.1.3). 1110.10.1.4 Null values 12A null value is specified by 13 (1) The r* form, 14 (2) Blanks between two consecutive value separators following an equals, 15 (3) Zero or more blanks preceding the first value separator and following an equals, or 16 (4) Two consecutive nonblank value separators. 17A null value has no effect on the definition status of the corresponding input list item. If the namelist 18group object list item is defined, it retains its previous value; if it is undefined, it remains undefined. A 19null value shall not be used as either the real or imaginary part of a complex constant, but a single null 20value may represent an entire complex constant. NOTE 10.36 The end of a record following a value separator, with or without intervening blanks, does not specify a null value in namelist input. 2110.10.1.5 Blanks 22All blanks in a namelist input record are considered to be part of some value separator except for 23 (1) Blanks embedded in a character constant, 24 (2) Embedded blanks surrounding the real or imaginary part of a complex constant, 25 (3) Leading blanks following the equals unless followed immediately by a slash or comma, or a 26 semicolon if the decimal edit mode is comma, and 27 (4) Blanks between a name and the following equals. 2810.10.1.6 Namelist Comments 29Except within a character literal constant, a "!" character after a value separator or in the first nonblank 30position of a namelist input record initiates a comment. The comment extends to the end of the current 31input record and may contain any graphic character in the processor-dependent character set. The 32comment is ignored. A slash within the namelist comment does not terminate execution of the namelist 33input statement. Namelist comments are not allowed in stream input because comments depend on 245 J3/04-007 WORKING DRAFT MAY 2004 1record structure. NOTE 10.37 Namelist input example: INTEGER I; REAL X (8); CHARACTER (11) P; COMPLEX Z; LOGICAL G NAMELIST / TODAY / G, I, P, Z, X READ (*, NML = TODAY) The input data records are: &TODAY I = 12345, X(1) = 12345, X(3:4) = 2*1.5, I=6, ! This is a comment. P = ''ISN'T_BOB'S'', Z = (123,0)/ The results stored are: Variable Value I 6 X (1) 12345.0 X (2) unchanged X (3) 1.5 X (4) 1.5 X (5) ­ X (8) unchanged P ISN'T BOB'S Z (123.0,0.0) G unchanged 210.10.2 Namelist output 3The form of the output produced is the same as that required for input, except for the forms of real, 4character, and logical values. The name in the output is in upper case. With the exception of adjacent 5undelimited character values, the values are separated by one or more blanks or by a comma, or a 6semicolon if the decimal edit mode is COMMA, optionally preceded by one or more blanks and optionally 7followed by one or more blanks. 8Namelist output shall not include namelist comments. 9The processor may begin new records as necessary. However, except for complex constants and character 10values, the end of a record shall not occur within a constant, character value, or name, and blanks shall 11not appear within a constant, character value, or name. NOTE 10.38 The length of the output records is not specified exactly and may be processor dependent. 1210.10.2.1 Namelist output editing 13Logical output values are T for the value true and F for the value false. 14Integer output constants are produced with the effect of an Iw edit descriptor. 15Real constants are produced with the effect of either an F edit descriptor or an E edit descriptor, 16depending on the magnitude x of the value and a range 10d1 x < 10d2, where d1 and d2 are processor- 17dependent integers. If the magnitude x is within this range or is zero, the constant is produced using 246 MAY 2004 WORKING DRAFT J3/04-007 10PFw.d; otherwise, 1PEw.d Ee is used. 2For numeric output, reasonable processor-dependent integer values of w, d, and e are used for each of 3the numeric constants output. 4Complex constants are enclosed in parentheses with a separator between the real and imaginary parts, 5each produced as defined above for real constants. The separator is a comma if the decimal edit mode is 6POINT; it is a semicolon if the decimal edit mode is COMMA. The end of a record may occur between 7the separator and the imaginary part only if the entire constant is as long as, or longer than, an entire 8record. The only embedded blanks permitted within a complex constant are between the separator and 9the end of a record and one blank at the beginning of the next record. 10Character sequences produced when the delimiter mode has a value of NONE 11 (1) Are not delimited by apostrophes or quotation marks, 12 (2) Are not separated from each other by value separators, 13 (3) Have each internal apostrophe or quotation mark represented externally by one apostrophe 14 or quotation mark, and 15 (4) Have a blank character inserted by the processor at the beginning of any record that begins 16 with the continuation of a character sequence from the preceding record. NOTE 10.39 Namelist output records produced with a DELIM= specifier with a value of NONE and which contain a character sequence might not be acceptable as namelist input records. 17Character sequences produced when the delimiter mode has a value of QUOTE are delimited by quotes, 18are preceded and followed by a value separator, and have each internal quote represented on the external 19medium by two contiguous quotes. 20Character sequences produced when the delimiter mode has a value of APOSTROPHE are delimited 21by apostrophes, are preceded and followed by a value separator, and have each internal apostrophe 22represented on the external medium by two contiguous apostrophes. 2310.10.2.2 Namelist output records 24If two or more successive values in an array in an output record produced have identical values, the 25processor has the option of producing a repeated constant of the form r*c instead of the sequence of 26identical values. 27The name of each namelist group object list item is placed in the output record followed by an equals 28and a list of values of the namelist group object list item. 29An ampersand character followed immediately by a namelist-group-name will be produced by namelist 30formatting at the start of the first output record to indicate which particular group of data objects is 31being output. A slash is produced by namelist formatting to indicate the end of the namelist formatting. 32A null value is not produced by namelist formatting. 33Except for continuation of delimited character sequences, each output record begins with a blank char- 34acter. 247 J3/04-007 WORKING DRAFT MAY 2004 248 MAY 2004 WORKING DRAFT J3/04-007 1Section 11: Program units 2The terms and basic concepts of program units were introduced in 2.2. A program unit is a main 3program, an external subprogram, a module, or a block data program unit. 4This section describes main programs, modules, and block data program units. Section 12 describes 5external subprograms. 611.1 Main program 7A Fortran main program is a program unit that does not contain a SUBROUTINE, FUNCTION, 8MODULE, or BLOCK DATA statement as its first statement. 9R1101 main-program is [ program-stmt ] 10 [ specification-part ] 11 [ execution-part ] 12 [ internal-subprogram-part ] 13 end-program-stmt 14R1102 program-stmt is PROGRAM program-name 15R1103 end-program-stmt is END [ PROGRAM [ program-name ] ] 16C1101 (R1101) In a main-program, the execution-part shall not contain a RETURN statement or an 17 ENTRY statement. 18C1102 (R1101) The program-name may be included in the end-program-stmt only if the optional 19 program-stmt is used and, if included, shall be identical to the program-name specified in the 20 program-stmt. 21C1103 (R1101) An automatic object shall not appear in the specification-part (R204) of a main program. NOTE 11.1 The program name is global to the program (16.1). For explanatory information about uses for the program name, see section C.8.1. NOTE 11.2 An example of a main program is: PROGRAM ANALYZE REAL A, B, C (10,10) ! Specification part CALL FIND ! Execution part CONTAINS SUBROUTINE FIND ! Internal subprogram ... END SUBROUTINE FIND END PROGRAM ANALYZE 22The main program may be defined by means other than Fortran; in that case, the program shall not 23contain a main-program program unit. 24A reference to a Fortran main-program shall not appear in any program unit in the program, including 249 J3/04-007 WORKING DRAFT MAY 2004 1itself. 211.2 Modules 3A module contains specifications and definitions that are to be accessible to other program units. A 4module that is provided as an inherent part of the processor is an intrinsic module. A nonintrinsic 5module is defined by a module program unit or a means other than Fortran. 6Procedures and types defined in an intrinsic module are not themselves intrinsic. 7R1104 module is module-stmt 8 [ specification-part ] 9 [ module-subprogram-part ] 10 end-module-stmt 11R1105 module-stmt is MODULE module-name 12R1106 end-module-stmt is END [ MODULE [ module-name ] ] 13R1107 module-subprogram-part is contains-stmt 14 module-subprogram 15 [ module-subprogram ] ... 16R1108 module-subprogram is function-subprogram 17 or subroutine-subprogram 18C1104 (R1104) If the module-name is specified in the end-module-stmt, it shall be identical to the 19 module-name specified in the module-stmt. 20C1105 (R1104) A module specification-part shall not contain a stmt-function-stmt, an entry-stmt, or a 21 format-stmt. 22C1106 (R1104) An automatic object shall not appear in the specification-part of a module. 23C1107 (R1104) If an object of a type for which component-initialization is specified (R444) appears 24 in the specification-part of a module and does not have the ALLOCATABLE or POINTER 25 attribute, the object shall have the SAVE attribute. NOTE 11.3 The module name is global to the program (16.1). NOTE 11.4 Although statement function definitions, ENTRY statements, and FORMAT statements shall not appear in the specification part of a module, they may appear in the specification part of a module subprogram in the module. A module is host to any module subprograms (12.1.2.2) it contains, and the entities in the module are therefore accessible in the module subprograms through host association. NOTE 11.5 For a discussion of the impact of modules on dependent compilation, see section C.8.2. NOTE 11.6 For examples of the use of modules, see section C.8.3. 26If a procedure declared in the scoping unit of a module has an implicit interface, it shall be given the 250 MAY 2004 WORKING DRAFT J3/04-007 1EXTERNAL attribute in that scoping unit; if it is a function, its type and type parameters shall be 2explicitly declared in a type declaration statement in that scoping unit. 3If an intrinsic procedure is declared in the scoping unit of a module, it shall explicitly be given the 4INTRINSIC attribute in that scoping unit or be used as an intrinsic procedure in that scoping unit. 511.2.1 The USE statement and use association 6The USE statement specifies use association. A USE statement is a module reference to the module 7it specifies. At the time a USE statement is processed, the public portions of the specified module shall 8be available. A module shall not reference itself, either directly or indirectly. 9The USE statement provides the means by which a scoping unit accesses named data objects, derived 10types, interface blocks, procedures, abstract interfaces, generic identifiers (12.3.2.1), and namelist groups 11in a module. The entities in the scoping unit are said to be use associated with the entities in the 12module. The accessed entities have the attributes specified in the module, except that an entity may 13have a different accessibility attribute or it may have the ASYNCHRONOUS or VOLATILE attribute 14in the local scoping unit even if the associated module entity does not. The entities made accessible are 15identified by the names or generic identifiers used to identify them in the module. By default, they are 16identified by the same identifiers in the scoping unit containing the USE statement, but it is possible to 17specify that different local identifiers are used. NOTE 11.7 The accessibility of module entities may be controlled by accessibility attributes (4.5.1.1, 5.1.2.1), and the ONLY option of the USE statement. Definability of module entities can be controlled by the PROTECTED attribute (5.1.2.12). 18R1109 use-stmt is USE [ [ , module-nature ] :: ] module-name [ , rename-list ] 19 or USE [ [ , module-nature ] :: ] module-name , 20 ONLY : [ only-list ] 21R1110 module-nature is INTRINSIC 22 or NON INTRINSIC 23R1111 rename is local-name => use-name 24 or OPERATOR (local-defined-operator) => 25 OPERATOR (use-defined-operator) 26R1112 only is generic-spec 27 or only-use-name 28 or rename 29R1113 only-use-name is use-name 30C1108 (R1109) If module-nature is INTRINSIC, module-name shall be the name of an intrinsic module. 31C1109 (R1109) If module-nature is NON INTRINSIC, module-name shall be the name of a nonintrinsic 32 module. 33C1110 (R1109) A scoping unit shall not access an intrinsic module and a nonintrinsic module of the 34 same name. 35C1111 (R1111) OPERATOR(use-defined-operator) shall not identify a generic-binding. 36C1112 (R1112) The generic-spec shall not identify a generic-binding. NOTE 11.8 The above two constraints do not prevent accessing a generic-spec that is declared by an interface block, even if a generic-binding has the same generic-spec. 251 J3/04-007 WORKING DRAFT MAY 2004 1C1113 (R1112) Each generic-spec shall be a public entity in the module. 2C1114 (R1113) Each use-name shall be the name of a public entity in the module. 3R1114 local-defined-operator is defined-unary-op 4 or defined-binary-op 5R1115 use-defined-operator is defined-unary-op 6 or defined-binary-op 7C1115 (R1115) Each use-defined-operator shall be a public entity in the module. 8A use-stmt without a module-nature provides access either to an intrinsic or to a nonintrinsic module. 9If the module-name is the name of both an intrinsic and a nonintrinsic module, the nonintrinsic module 10is accessed. 11The USE statement without the ONLY option provides access to all public entities in the specified 12module. 13A USE statement with the ONLY option provides access only to those entities that appear as generic- 14specs, use-names, or use-defined-operators in the only-list. 15More than one USE statement for a given module may appear in a scoping unit. If one of the USE 16statements is without an ONLY qualifier, all public entities in the module are accessible. If all the USE 17statements have ONLY qualifiers, only those entities in one or more of the only-lists are accessible. 18An accessible entity in the referenced module has one or more local identifiers. These identifiers are 19 (1) The identifier of the entity in the referenced module if that identifier appears as an only- 20 use-name or as the defined-operator of a generic-spec in any only for that module, 21 (2) Each of the local-names or local-defined-operators that the entity is given in any rename for 22 that module, and 23 (3) The identifier of the entity in the referenced module if that identifier does not appear as a 24 use-name or use-defined-operator in any rename for that module. 25Two or more accessible entities, other than generic interfaces or defined operators, may have the same 26identifier only if the identifier is not used to refer to an entity in the scoping unit. Generic interfaces and 27defined operators are handled as described in section 16.2.3. Except for these cases, the local identifier 28of any entity given accessibility by a USE statement shall differ from the local identifiers of all other 29entities accessible to the scoping unit through USE statements and otherwise. NOTE 11.9 There is no prohibition against a use-name or use-defined-operator appearing multiple times in one USE statement or in multiple USE statements involving the same module. As a result, it is possible for one use-associated entity to be accessible by more than one local identifier. 30The local identifier of an entity made accessible by a USE statement shall not appear in any other 31nonexecutable statement that would cause any attribute (5.1.2) of the entity to be specified in the 32scoping unit that contains the USE statement, except that it may appear in a PUBLIC or PRIVATE 33statement in the scoping unit of a module and it may be given the ASYNCHRONOUS or VOLATILE 34attribute. 35The appearance of such a local identifier in a PUBLIC statement in a module causes the entity accessible 36by the USE statement to be a public entity of that module. If the identifier appears in a PRIVATE 37statement in a module, the entity is not a public entity of that module. If the local identifier does not 38appear in either a PUBLIC or PRIVATE statement, it assumes the default accessibility attribute (5.2.1) 252 MAY 2004 WORKING DRAFT J3/04-007 1of that scoping unit. NOTE 11.10 The constraints in sections 5.5.1, 5.5.2, and 5.4 prohibit the local-name from appearing as a common-block-object in a COMMON statement, an equivalence-object in an EQUIVALENCE state- ment, or a namelist-group-name in a NAMELIST statement, respectively. There is no prohibition against the local-name appearing as a common-block-name or a namelist-group-object. NOTE 11.11 For a discussion of the impact of the ONLY clause and renaming on dependent compilation, see section C.8.2.1. NOTE 11.12 Examples: USE STATS LIB provides access to all public entities in the module STATS LIB. USE MATH LIB; USE STATS LIB, SPROD => PROD makes all public entities in both MATH LIB and STATS LIB accessible. If MATH LIB contains an entity called PROD, it is accessible by its own name while the entity PROD of STATS LIB is accessible by the name SPROD. USE STATS LIB, ONLY: YPROD; USE STATS LIB, ONLY : PROD makes public entities YPROD and PROD in STATS LIB accessible. USE STATS LIB, ONLY : YPROD; USE STATS LIB makes all public entities in STATS LIB accessible. 211.3 Block data program units 3A block data program unit is used to provide initial values for data objects in named common blocks. 4R1116 block-data is block-data-stmt 5 [ specification-part ] 6 end-block-data-stmt 7R1117 block-data-stmt is BLOCK DATA [ block-data-name ] 8R1118 end-block-data-stmt is END [ BLOCK DATA [ block-data-name ] ] 9C1116 (R1116) The block-data-name shall be included in the end-block-data-stmt only if it was provided 10 in the block-data-stmt and, if included, shall be identical to the block-data-name in the block- 11 data-stmt. 12C1117 (R1116) A block-data specification-part shall contain only derived-type definitions and ASYN- 13 CHRONOUS, BIND, COMMON, DATA, DIMENSION, EQUIVALENCE, IMPLICIT, INTRIN- 14 SIC, PARAMETER, POINTER, SAVE, TARGET, USE, VOLATILE, and type declaration 253 J3/04-007 WORKING DRAFT MAY 2004 1 statements. 2C1118 (R1116) A type declaration statement in a block-data specification-part shall not contain AL- 3 LOCATABLE, EXTERNAL, or BIND attribute specifiers. NOTE 11.13 For explanatory information about the uses for the block-data-name, see section C.8.1. 4If an object in a named common block is initially defined, all storage units in the common block storage 5sequence shall be specified even if they are not all initially defined. More than one named common block 6may have objects initially defined in a single block data program unit. NOTE 11.14 In the example BLOCK DATA INIT REAL A, B, C, D, E, F COMMON /BLOCK1/ A, B, C, D DATA A /1.2/, C /2.3/ COMMON /BLOCK2/ E, F DATA F /6.5/ END BLOCK DATA INIT common blocks BLOCK1 and BLOCK2 both have objects that are being initialized in a single block data program unit. B, D, and E are not initialized but they need to be specified as part of the common blocks. 7Only an object in a named common block may be initially defined in a block data program unit. NOTE 11.15 Objects associated with an object in a common block are considered to be in that common block. 8The same named common block shall not be specified in more than one block data program unit in a 9program. 10There shall not be more than one unnamed block data program unit in a program. NOTE 11.16 An example of a block data program unit is: BLOCK DATA WORK COMMON /WRKCOM/ A, B, C (10, 10) REAL :: A, B, C DATA A /1.0/, B /2.0/, C /100 * 0.0/ END BLOCK DATA WORK 254 MAY 2004 WORKING DRAFT J3/04-007 1Section 12: Procedures 2The concept of a procedure was introduced in 2.2.3. This section contains a complete description of 3procedures. The actions specified by a procedure are performed when the procedure is invoked by 4execution of a reference to it. 5The sequence of actions encapsulated by a procedure has access to entities in the invoking scoping 6unit by way of argument association (12.4.1). A dummy argument is a name that appears in the 7SUBROUTINE, FUNCTION, or ENTRY statement in the declaration of a procedure (R1233). Dummy 8arguments are also specified for intrinsic procedures and procedures in intrinsic modules in Sections 13, 914, and 15. 10The entities in the invoking scoping unit are specified by actual arguments. An actual argument is an 11entity that appears in a procedure reference (R1221). 12A procedure may also have access to entities in other scoping units, not necessarily the invoking scoping 13unit, by use association (16.4.1.2), host association (16.4.1.3), linkage association (16.4.1.4), storage 14association (16.4.3), or by reference to external procedures (5.1.2.6). 1512.1 Procedure classifications 16A procedure is classified according to the form of its reference and the way it is defined. 1712.1.1 Procedure classification by reference 18The definition of a procedure specifies it to be a function or a subroutine. A reference to a function either 19appears explicitly as a primary within an expression, or is implied by a defined operation (7.1.3) within 20an expression. A reference to a subroutine is a CALL statement or a defined assignment statement 21(7.4.1.4). 22A procedure is classified as elemental if it is a procedure that may be referenced elementally (12.7). 2312.1.2 Procedure classification by means of definition 24A procedure is either an intrinsic procedure, an external procedure, a module procedure, an internal 25procedure, a dummy procedure (which may be a dummy procedure pointer), a nondummy procedure 26pointer, or a statement function. 2712.1.2.1 Intrinsic procedures 28A procedure that is provided as an inherent part of the processor is an intrinsic procedure. 2912.1.2.2 External, internal, and module procedures 30An external procedure is a procedure that is defined by an external subprogram or by a means other 31than Fortran. 32An internal procedure is a procedure that is defined by an internal subprogram. Internal subprograms 33may appear in the main program, in an external subprogram, or in a module subprogram. Internal 34subprograms shall not appear in other internal subprograms. Internal subprograms are the same as 35external subprograms except that the name of the internal procedure is not a global identifier, an 255 J3/04-007 WORKING DRAFT MAY 2004 1internal subprogram shall not contain an ENTRY statement, the internal procedure name shall not be 2argument associated with a dummy procedure (12.4.1.3), and the internal subprogram has access to host 3entities by host association. 4A module procedure is a procedure that is defined by a module subprogram. 5A subprogram defines a procedure for the SUBROUTINE or FUNCTION statement. If the subprogram 6has one or more ENTRY statements, it also defines a procedure for each of them. 712.1.2.3 Dummy procedures 8A dummy argument that is specified to be a procedure or appears in a procedure reference is a dummy 9procedure. A dummy procedure with the POINTER attribute is a dummy procedure pointer. 1012.1.2.4 Procedure pointers 11A procedure pointer is a procedure that has the EXTERNAL and POINTER attributes; it may be 12pointer associated with an external procedure, a module procedure, an intrinsic procedure, or a dummy 13procedure that is not a procedure pointer. 1412.1.2.5 Statement functions 15 A function that is defined by a single statement is a statement function (12.5.4). 1612.2 Characteristics of procedures 17The characteristics of a procedure are the classification of the procedure as a function or subroutine, 18whether it is pure, whether it is elemental, whether it has the BIND attribute, the characteristics of its 19dummy arguments, and the characteristics of its result value if it is a function. 2012.2.1 Characteristics of dummy arguments 21Each dummy argument has the characteristic that it is a dummy data object, a dummy procedure, a 22dummy procedure pointer, or an asterisk (alternate return indicator). A dummy argument other than an asterisk 23may be specified to have the OPTIONAL attribute. This attribute means that the dummy argument 24need not be associated with an actual argument for any particular reference to the procedure. 2512.2.1.1 Characteristics of dummy data objects 26The characteristics of a dummy data object are its type, its type parameters (if any), its shape, its 27intent (5.1.2.7, 5.2.7), whether it is optional (5.1.2.9, 5.2.8), whether it is allocatable (5.1.2.5.3), whether 28it has the VALUE (5.1.2.15), ASYNCHRONOUS (5.1.2.3), or VOLATILE (5.1.2.16) attributes, whether 29it is polymorphic, and whether it is a pointer (5.1.2.11, 5.2.10) or a target (5.1.2.14, 5.2.13). If a type 30parameter of an object or a bound of an array is not an initialization expression, the exact dependence 31on the entities in the expression is a characteristic. If a shape, size, or type parameter is assumed or 32deferred, it is a characteristic. 3312.2.1.2 Characteristics of dummy procedures and dummy procedure pointers 34The characteristics of a dummy procedure are the explicitness of its interface (12.3.1), its characteristics 35as a procedure if the interface is explicit, whether it is a pointer, and whether it is optional (5.1.2.9, 5.2.8). 3612.2.1.3 Characteristics of asterisk dummy arguments 37 An asterisk as a dummy argument has no characteristics. 256 MAY 2004 WORKING DRAFT J3/04-007 112.2.2 Characteristics of function results 2The characteristics of a function result are its type, type parameters (if any), rank, whether it is poly- 3morphic, whether it is allocatable, whether it is a pointer, and whether it is a procedure pointer. If a 4function result is an array that is not allocatable or a pointer, its shape is a characteristic. If a type 5parameter of a function result or a bound of a function result array is not an initialization expression, the 6exact dependence on the entities in the expression is a characteristic. If type parameters of a function 7result are deferred, which parameters are deferred is a characteristic. If the length of a character function 8 result is assumed, this is a characteristic. 912.3 Procedure interface 10The interface of a procedure determines the forms of reference through which it may be invoked. 11The procedure's interface consists of its abstract interface, its name, its binding label if any, and the 12procedure's generic identifiers, if any. The characteristics of a procedure are fixed, but the remainder of 13the interface may differ in different scoping units. 14An abstract interface consists of procedure characteristics and the names of dummy arguments. NOTE 12.1 For more explanatory information on procedure interfaces, see C.9.3. 1512.3.1 Implicit and explicit interfaces 16If a procedure is accessible in a scoping unit, its interface is either explicit or implicit in that scoping 17unit. The interface of an internal procedure, module procedure, or intrinsic procedure is always explicit 18in such a scoping unit. The interface of a subroutine or a function with a separate result name is explicit 19within the subprogram that defines it. The interface of a statement function is always implicit. The interface of 20an external procedure or dummy procedure is explicit in a scoping unit other than its own if an interface 21body (12.3.2.1) for the procedure is supplied or accessible, and implicit otherwise. NOTE 12.2 For example, the subroutine LLS of C.8.3.5 has an explicit interface. 2212.3.1.1 Explicit interface 23A procedure other than a statement function shall have an explicit interface if it is referenced and 24 (1) A reference to the procedure appears 25 (a) With an argument keyword (12.4.1), 26 (b) As a reference by its generic name (12.3.2.1), 27 (c) As a defined assignment (subroutines only), 28 (d) In an expression as a defined operator (functions only), or 29 (e) In a context that requires it to be pure, 30 (2) The procedure has a dummy argument that 31 (a) has the ALLOCATABLE, ASYNCHRONOUS, OPTIONAL, POINTER, TARGET, 32 VALUE, or VOLATILE attribute, 33 (b) is an assumed-shape array, 34 (c) is of a parameterized derived type, or 35 (d) is polymorphic, 257 J3/04-007 WORKING DRAFT MAY 2004 1 (3) The procedure has a result that 2 (a) is an array, 3 (b) is a pointer or is allocatable, or 4 (c) has a nonassumed type parameter value that is not an initialization expression, 5 (4) The procedure is elemental, or 6 (5) The procedure has the BIND attribute. 712.3.2 Specification of the procedure interface 8The interface for an internal, external, module, or dummy procedure is specified by a FUNCTION, 9SUBROUTINE, or ENTRY statement and by specification statements for the dummy arguments and 10the result of a function. These statements may appear in the procedure definition, in an interface body, 11or both, except that the ENTRY statement shall not appear in an interface body. NOTE 12.3 An interface body cannot be used to describe the interface of an internal procedure, a module procedure, or an intrinsic procedure because the interfaces of such procedures are already explicit. However, the name of a procedure may appear in a PROCEDURE statement in an interface block (12.3.2.1). 1212.3.2.1 Interface block 13R1201 interface-block is interface-stmt 14 [ interface-specification ] ... 15 end-interface-stmt 16R1202 interface-specification is interface-body 17 or procedure-stmt 18R1203 interface-stmt is INTERFACE [ generic-spec ] 19 or ABSTRACT INTERFACE 20R1204 end-interface-stmt is END INTERFACE [ generic-spec ] 21R1205 interface-body is function-stmt 22 [ specification-part ] 23 end-function-stmt 24 or subroutine-stmt 25 [ specification-part ] 26 end-subroutine-stmt 27R1206 procedure-stmt is [ MODULE ] PROCEDURE procedure-name-list 28R1207 generic-spec is generic-name 29 or OPERATOR ( defined-operator ) 30 or ASSIGNMENT ( = ) 31 or dtio-generic-spec 32R1208 dtio-generic-spec is READ (FORMATTED) 33 or READ (UNFORMATTED) 34 or WRITE (FORMATTED) 35 or WRITE (UNFORMATTED) 36R1209 import-stmt is IMPORT [[ :: ] import-name-list ] 37C1201 (R1201) An interface-block in a subprogram shall not contain an interface-body for a procedure 38 defined by that subprogram. 39C1202 (R1201) The generic-spec shall be included in the end-interface-stmt only if it is provided in the 40 interface-stmt. If the end-interface-stmt includes generic-name, the interface-stmt shall specify 41 the same generic-name. If the end-interface-stmt includes ASSIGNMENT(=), the interface- 258 MAY 2004 WORKING DRAFT J3/04-007 1 stmt shall specify ASSIGNMENT(=). If the end-interface-stmt includes dtio-generic-spec, 2 the interface-stmt shall specify the same dtio-generic-spec. If the end-interface-stmt includes 3 OPERATOR(defined-operator), the interface-stmt shall specify the same defined-operator. If 4 one defined-operator is .LT., .LE., .GT., .GE., .EQ., or .NE., the other is permitted to be the 5 corresponding operator <, <=, >, >=, ==, or /=. 6C1203 (R1203) If the interface-stmt is ABSTRACT INTERFACE, then the function-name in the 7 function-stmt or the subroutine-name in the subroutine-stmt shall not be the same as a keyword 8 that specifies an intrinsic type. 9C1204 (R1202) A procedure-stmt is allowed only in an interface block that has a generic-spec. 10C1205 (R1205) An interface-body of a pure procedure shall specify the intents of all dummy arguments 11 except pointer, alternate return, and procedure arguments. 12C1206 (R1205) An interface-body shall not contain an entry-stmt, data-stmt, format-stmt, or stmt- 13 function-stmt. 14C1207 (R1206) A procedure-name shall have an explicit interface and shall refer to an accessible pro- 15 cedure pointer, external procedure, dummy procedure, or module procedure. 16C1208 (R1206) If MODULE appears in a procedure-stmt, each procedure-name in that statement shall 17 be accessible in the current scope as a module procedure. 18C1209 (R1206) A procedure-name shall not specify a procedure that is specified previously in any 19 procedure-stmt in any accessible interface with the same generic identifier. 20C1210 (R1209) The IMPORT statement is allowed only in an interface-body. 21C1211 (R1209) Each import-name shall be the name of an entity in the host scoping unit. 22An external or module subprogram specifies a specific interface for the procedures defined in that 23subprogram. Such a specific interface is explicit for module procedures and implicit for external proce- 24dures. 25An interface block introduced by ABSTRACT INTERFACE is an abstract interface block. An 26interface body in an abstract interface block specifies an abstract interface. An interface block with a 27generic specification is a generic interface block. An interface block with neither ABSTRACT nor a 28generic specification is a specific interface block. 29The name of the entity declared by an interface body is the function-name in the function-stmt or the 30subroutine-name in the subroutine-stmt that begins the interface body. 31An interface body in a generic or specific interface block specifies the EXTERNAL attribute and an 32explicit specific interface for an external procedure or a dummy procedure. If the name of the declared 33procedure is that of a dummy argument in the subprogram containing the interface body, the procedure 34is a dummy procedure; otherwise, it is an external procedure. 35An interface body specifies all of the characteristics of the explicit specific interface or abstract interface. 36The specification part of an interface body may specify attributes or define values for data entities that 37do not determine characteristics of the procedure. Such specifications have no effect. 38If an explicit specific interface is specified by an interface body or a procedure declaration statement 39(12.3.2.3) for an external procedure, the characteristics shall be consistent with those specified in the 40procedure definition, except that the interface may specify a procedure that is not pure if the procedure 41is defined to be pure. An interface for a procedure named by an ENTRY statement may be specified by 42using the entry name as the procedure name in the interface body. An explicit specific interface may 43be specified by an interface body for an external procedure that does not exist in the program if the 259 J3/04-007 WORKING DRAFT MAY 2004 1procedure is never used in any way. A procedure shall not have more than one explicit specific interface 2in a given scoping unit. NOTE 12.4 The dummy argument names may be different because the name of a dummy argument is not a characteristic. 3The IMPORT statement specifies that the named entities from the host scoping unit are accessible in 4the interface body by host association. An entity that is imported in this manner and is defined in the 5host scoping unit shall be explicitly declared prior to the interface body. The name of an entity made 6accessible by an IMPORT statement shall not appear in any of the contexts described in 16.4.1.3 that 7cause the host entity of that name to be inaccessible. 8Within an interface body, if an IMPORT statement with no import-name-list appears, each host entity 9not named in an IMPORT statement also is made accessible by host association if its name does not 10appear in any of the contexts described in 16.4.1.3 that cause the host entity of that name to be 11inaccessible. If an entity that is made accessible by this means is accessed by host association and is 12defined in the host scoping unit, it shall be explicitly declared prior to the interface body. NOTE 12.5 An example of an interface block without a generic specification is: INTERFACE SUBROUTINE EXT1 (X, Y, Z) REAL, DIMENSION (100, 100) :: X, Y, Z END SUBROUTINE EXT1 SUBROUTINE EXT2 (X, Z) REAL X COMPLEX (KIND = 4) Z (2000) END SUBROUTINE EXT2 FUNCTION EXT3 (P, Q) LOGICAL EXT3 INTEGER P (1000) LOGICAL Q (1000) END FUNCTION EXT3 END INTERFACE This interface block specifies explicit interfaces for the three external procedures EXT1, EXT2, and EXT3. Invocations of these procedures may use argument keywords (12.4.1); for example: EXT3 (Q = P_MASK (N+1 : N+1000), P = ACTUAL_P) NOTE 12.6 The IMPORT statement can be used to allow module procedures to have dummy arguments that are procedures with assumed-shape arguments of an opaque type. For example: MODULE M TYPE T PRIVATE ! T is an opaque type ... END TYPE CONTAINS SUBROUTINE PROCESS(X,Y,RESULT,MONITOR) 260 MAY 2004 WORKING DRAFT J3/04-007 NOTE 12.6 (cont.) TYPE(T),INTENT(IN) :: X(:,:),Y(:,:) TYPE(T),INTENT(OUT) :: RESULT(:,:) INTERFACE SUBROUTINE MONITOR(ITERATION_NUMBER,CURRENT_ESTIMATE) IMPORT T INTEGER,INTENT(IN) :: ITERATION_NUMBER TYPE(T),INTENT(IN) :: CURRENT_ESTIMATE(:,:) END SUBROUTINE END INTERFACE ... END SUBROUTINE END MODULE The MONITOR dummy procedure requires an explicit interface because it has an assumed-shape array argument, but TYPE(T) would not be available inside the interface body without the IM- PORT statement. 1A generic interface block specifies a generic interface for each of the procedures in the interface 2block. The PROCEDURE statement lists procedure pointers, external procedures, dummy procedures, 3or module procedures that have this generic interface. A generic interface is always explicit. 4Any procedure may be referenced via its specific interface if the specific interface is accessible. It also 5may be referenced via a generic interface. The generic-spec in an interface-stmt is a generic identifier 6for all the procedures in the interface block. The rules specifying how any two procedures with the same 7generic identifier shall differ are given in 16.2.3. They ensure that any generic invocation applies to at 8most one specific procedure. 9A generic name specifies a single name to reference all of the procedure names in the interface block. 10A generic name may be the same as any one of the procedure names in the interface block, or the same 11as any accessible generic name. 12A generic name may be the same as a derived-type name, in which case all of the procedures in the 13interface block shall be functions. NOTE 12.7 An example of a generic procedure interface is: INTERFACE SWITCH SUBROUTINE INT_SWITCH (X, Y) INTEGER, INTENT (INOUT) :: X, Y END SUBROUTINE INT_SWITCH SUBROUTINE REAL_SWITCH (X, Y) REAL, INTENT (INOUT) :: X, Y END SUBROUTINE REAL_SWITCH SUBROUTINE COMPLEX_SWITCH (X, Y) COMPLEX, INTENT (INOUT) :: X, Y END SUBROUTINE COMPLEX_SWITCH END INTERFACE SWITCH Any of these three subroutines (INT SWITCH, REAL SWITCH, COMPLEX SWITCH) may be referenced with the generic name SWITCH, as well as by its specific name. For example, a reference to INT SWITCH could take the form: 261 J3/04-007 WORKING DRAFT MAY 2004 NOTE 12.7 (cont.) CALL SWITCH (MAX_VAL, LOC_VAL) ! MAX_VAL and LOC_VAL are of type INTEGER 1An interface-stmt having a dtio-generic-spec is an interface for a user-defined derived-type input/output 2procedure (9.5.3.7) 312.3.2.1.1 Defined operations 4If OPERATOR is specified in a generic specification, all of the procedures specified in the generic interface 5shall be functions that may be referenced as defined operations (7.1.3, 7.1.8.7, 7.2, 12.4). In the case of 6functions of two arguments, infix binary operator notation is implied. In the case of functions of one 7argument, prefix operator notation is implied. OPERATOR shall not be specified for functions with no 8arguments or for functions with more than two arguments. The dummy arguments shall be nonoptional 9dummy data objects and shall be specified with INTENT (IN). The function result shall not have assumed 10 character length. If the operator is an intrinsic-operator (R310), the number of function arguments shall 11be consistent with the intrinsic uses of that operator, and the types, kind type parameters, or ranks of 12the dummy arguments shall differ from those required for the intrinsic operation (7.1.2). 13A defined operation is treated as a reference to the function. For a unary defined operation, the operand 14corresponds to the function's dummy argument; for a binary operation, the left-hand operand corre- 15sponds to the first dummy argument of the function and the right-hand operand corresponds to the 16second dummy argument. NOTE 12.8 An example of the use of the OPERATOR generic specification is: INTERFACE OPERATOR ( * ) FUNCTION BOOLEAN_AND (B1, B2) LOGICAL, INTENT (IN) :: B1 (:), B2 (SIZE (B1)) LOGICAL :: BOOLEAN_AND (SIZE (B1)) END FUNCTION BOOLEAN_AND END INTERFACE OPERATOR ( * ) This allows, for example SENSOR (1:N) * ACTION (1:N) as an alternative to the function call BOOLEAN_AND (SENSOR (1:N), ACTION (1:N)) ! SENSOR and ACTION are ! of type LOGICAL 17A given defined operator may, as with generic names, apply to more than one function, in which case 18it is generic in exact analogy to generic procedure names. For intrinsic operator symbols, the generic 19properties include the intrinsic operations they represent. Because both forms of each relational operator 20have the same interpretation (7.2), extending one form (such as <=) has the effect of defining both forms 21(<= and .LE.). NOTE 12.9 In Fortran 90 and Fortran 95, it was not possible to define operations on pointers because pointer dummy arguments were disallowed from having an INTENT attribute. The restriction against INTENT for pointer dummy arguments is now lifted, so defined operations on pointers are now 262 MAY 2004 WORKING DRAFT J3/04-007 NOTE 12.9 (cont.) possible. However, the POINTER attribute cannot be used to resolve generic procedures (16.2.3), so it is not possible to define a generic operator that has one procedure for pointers and another procedure for nonpointers. 112.3.2.1.2 Defined assignments 2If ASSIGNMENT ( = ) is specified in a generic specification, all the procedures in the generic interface 3shall be subroutines that may be referenced as defined assignments (7.4.1.4). Defined assignment may, 4as with generic names, apply to more than one subroutine, in which case it is generic in exact analogy 5to generic procedure names. 6Each of these subroutines shall have exactly two dummy arguments. Each argument shall be nonoptional. 7The first argument shall have INTENT (OUT) or INTENT (INOUT) and the second argument shall 8have INTENT (IN). Either the second argument shall be an array whose rank differs from that of the 9first argument, the declared types and kind type parameters of the arguments shall not conform as 10specified in Table 7.8, or the first argument shall be of derived type. A defined assignment is treated 11as a reference to the subroutine, with the left-hand side as the first argument and the right-hand side 12enclosed in parentheses as the second argument. The ASSIGNMENT generic specification specifies that 13assignment is extended or redefined. NOTE 12.10 An example of the use of the ASSIGNMENT generic specification is: INTERFACE ASSIGNMENT ( = ) SUBROUTINE LOGICAL_TO_NUMERIC (N, B) INTEGER, INTENT (OUT) :: N LOGICAL, INTENT (IN) :: B END SUBROUTINE LOGICAL_TO_NUMERIC SUBROUTINE CHAR_TO_STRING (S, C) USE STRING_MODULE ! Contains definition of type STRING TYPE (STRING), INTENT (OUT) :: S ! A variable-length string CHARACTER (*), INTENT (IN) :: C END SUBROUTINE CHAR_TO_STRING END INTERFACE ASSIGNMENT ( = ) Example assignments are: KOUNT = SENSOR (J) ! CALL LOGICAL_TO_NUMERIC (KOUNT, (SENSOR (J))) NOTE = '89AB' ! CALL CHAR_TO_STRING (NOTE, ('89AB')) 1412.3.2.1.3 User-defined derived-type input/output procedure interfaces 15All of the procedures specified in an interface block for a user-defined derived-type input/output proce- 16dure shall be subroutines that have interfaces as described in 9.5.3.7.2. 1712.3.2.2 EXTERNAL statement 18An EXTERNAL statement specifies the EXTERNAL attribute (5.1.2.6) for a list of names. 19R1210 external-stmt is EXTERNAL [ :: ] external-name-list 263 J3/04-007 WORKING DRAFT MAY 2004 1Each external-name shall be the name of an external procedure, a dummy argument, a procedure pointer, 2or a block data program unit. In an external subprogram, an EXTERNAL statement shall not specify 3the name of a procedure defined by the subprogram. 4The appearance of the name of a block data program unit in an EXTERNAL statement confirms that 5the block data program unit is a part of the program. NOTE 12.11 For explanatory information on potential portability problems with external procedures, see section C.9.1. NOTE 12.12 An example of an EXTERNAL statement is: EXTERNAL FOCUS 612.3.2.3 Procedure declaration statement 7A procedure declaration statement declares procedure pointers, dummy procedures, and external pro- 8cedures. It specifies the EXTERNAL attribute (5.1.2.6) for all procedure entities in the proc-decl-list. 9R1211 procedure-declaration-stmt is PROCEDURE ( [ proc-interface ] ) 10 [ [ , proc-attr-spec ] ... :: ] proc-decl-list 11R1212 proc-interface is interface-name 12 or declaration-type-spec 13R1213 proc-attr-spec is access-spec 14 or proc-language-binding-spec 15 or INTENT ( intent-spec ) 16 or OPTIONAL 17 or POINTER 18 or SAVE 19R1214 proc-decl is procedure-entity-name[ => null-init ] 20R1215 interface-name is name 21C1212 (R1215) The name shall be the name of an abstract interface or of a procedure that has an 22 explicit interface. If name is declared by a procedure-declaration-stmt it shall be previously 23 declared. If name denotes an intrinsic procedure it shall be one that is listed in 13.6 and not 24 marked with a bullet (·). 25C1213 (R1215) The name shall not be the same as a keyword that specifies an intrinsic type. 26C1214 If a procedure entity has the INTENT attribute or SAVE attribute, it shall also have the 27 POINTER attribute. 28C1215 (R1211) If a proc-interface describes an elemental procedure, each procedure-entity-name shall 29 specify an external procedure. 30C1216 (R1214) If => appears in proc-decl, the procedure entity shall have the POINTER attribute. 31C1217 (R1211) If proc-language-binding-spec with a NAME= is specified, then proc-decl-list shall con- 32 tain exactly one proc-decl, which shall neither have the POINTER attribute nor be a dummy 33 procedure. 34C1218 (R1211) If proc-language-binding-spec is specified, the proc-interface shall appear, it shall be an 35 interface-name, and interface-name shall be declared with a proc-language-binding-spec. 264 MAY 2004 WORKING DRAFT J3/04-007 1If proc-interface appears and consists of interface-name, it specifies an explicit specific interface (12.3.2.1) 2for the declared procedures or procedure pointers. The abstract interface (12.3) is that specified by the 3interface named by interface-name. 4If proc-interface appears and consists of declaration-type-spec, it specifies that the declared procedures 5or procedure pointers are functions having implicit interfaces and the specified result type. If a type is 6specified for an external function, its function definition (12.5.2.1) shall specify the same result type and 7type parameters. 8If proc-interface does not appear, the procedure declaration statement does not specify whether the 9declared procedures or procedure pointers are subroutines or functions. 10If a proc-attr-spec other than a proc-language-binding-spec appears, it specifies that the declared pro- 11cedures or procedure pointers have that attribute. These attributes are described in 5.1.2. If a proc- 12language-binding-spec with NAME= appears, it specifies a binding label or its absence, as described in 1315.4.1. A proc-language-binding-spec without a NAME= is allowed, but is redundant with the proc- 14interface required by C1218. 15If => null-init appears in a proc-decl in a procedure-declaration-stmt, it specifies that the initial associ- 16ation status of the corresponding procedure entity is disassociated. It also implies the SAVE attribute, 17which may be reaffirmed by explicit use of the SAVE attribute in the procedure-declaration-stmt or by 18a SAVE statement." NOTE 12.13 In contrast to the EXTERNAL statement, it is not possible to use the PROCEDURE statement to identify a BLOCK DATA subprogram. NOTE 12.14 The following code illustrates PROCEDURE statements. Note 7.43 illustrates the use of the P and BESSEL defined by this code. ABSTRACT INTERFACE FUNCTION REAL_FUNC (X) REAL, INTENT (IN) :: X REAL :: REAL_FUNC END FUNCTION REAL_FUNC END INTERFACE INTERFACE SUBROUTINE SUB (X) REAL, INTENT (IN) :: X END SUBROUTINE SUB END INTERFACE !-- Some external or dummy procedures with explicit interface. PROCEDURE (REAL_FUNC) :: BESSEL, GAMMA PROCEDURE (SUB) :: PRINT_REAL !-- Some procedure pointers with explicit interface, !-- one initialized to NULL(). PROCEDURE (REAL_FUNC), POINTER :: P, R => NULL() PROCEDURE (REAL_FUNC), POINTER :: PTR_TO_GAMMA !-- A derived type with a procedure pointer component ... TYPE STRUCT_TYPE PROCEDURE (REAL_FUNC), POINTER :: COMPONENT 265 J3/04-007 WORKING DRAFT MAY 2004 NOTE 12.14 (cont.) END TYPE STRUCT_TYPE !-- ... and a variable of that type. TYPE(STRUCT_TYPE) :: STRUCT !-- An external or dummy function with implicit interface PROCEDURE (REAL) :: PSI 112.3.2.4 INTRINSIC statement 2An INTRINSIC statement specifies a list of names that have the INTRINSIC attribute (5.1.2.8). 3R1216 intrinsic-stmt is INTRINSIC [ :: ] intrinsic-procedure-name-list 4C1219 (R1216) Each intrinsic-procedure-name shall be the name of an intrinsic procedure. NOTE 12.15 A name shall not be explicitly specified to have both the EXTERNAL and INTRINSIC attributes in the same scoping unit. 512.3.2.5 Implicit interface specification 6In a scoping unit where the interface of a function is implicit, the type and type parameters of the 7function result are specified by an implicit or explicit type specification of the function name. The type, 8type parameters, and shape of dummy arguments of a procedure referenced from a scoping unit where 9the interface of the procedure is implicit shall be such that the actual arguments are consistent with the 10characteristics of the dummy arguments. 1112.4 Procedure reference 12The form of a procedure reference is dependent on the interface of the procedure or procedure pointer, 13but is independent of the means by which the procedure is defined. The forms of procedure references 14are: 15R1217 function-reference is procedure-designator ( [ actual-arg-spec-list ] ) 16C1220 (R1217) The procedure-designator shall designate a function. 17C1221 (R1217) The actual-arg-spec-list shall not contain an alt-return-spec. 18R1218 call-stmt is CALL procedure-designator [ ( [ actual-arg-spec-list ] ) ] 19C1222 (R1218) The procedure-designator shall designate a subroutine. 20R1219 procedure-designator is procedure-name 21 or proc-component-ref 22 or data-ref % binding-name 23C1223 (R1219) A procedure-name shall be the name of a procedure or procedure pointer. 24C1224 (R1219) A binding-name shall be a binding name (4.5.4) of the declared type of data-ref . 25Resolving references to type-bound procedures is described in 12.4.5. 26A function may also be referenced as a defined operation (12.3.2.1.1). A subroutine may also be referenced 27as a defined assignment (12.3.2.1.2). 266 MAY 2004 WORKING DRAFT J3/04-007 1R1220 actual-arg-spec is [ keyword = ] actual-arg 2R1221 actual-arg is expr 3 or variable 4 or procedure-name 5 or proc-component-ref 6 or alt-return-spec 7 R1222 alt-return-spec is * label 8C1225 (R1220) The keyword = shall not appear if the interface of the procedure is implicit in the 9 scoping unit. 10C1226 (R1220) The keyword = shall not be omitted from an actual-arg-spec unless it has been omitted 11 from each preceding actual-arg-spec in the argument list. 12C1227 (R1220) Each keyword shall be the name of a dummy argument in the explicit interface of the 13 procedure. 14C1228 (R1221) A nonintrinsic elemental procedure shall not be used as an actual argument. 15C1229 (R1221) A procedure-name shall be the name of an external procedure, a dummy procedure, a 16 module procedure, a procedure pointer, or a specific intrinsic function that is listed in 13.6 and 17 not marked with a bullet(·). NOTE 12.16 This standard does not allow internal procedures to be used as actual arguments, in part to simplify the problem of ensuring that internal procedures with recursive hosts access entities from the correct instance (12.5.2.3) of the host. If, as an extension, a processor allows internal procedures to be used as actual arguments, the correct instance in this case is the instance in which the procedure is supplied as an actual argument, even if the corresponding dummy argument is eventually invoked from a different instance. 18C1230 (R1221) In a reference to a pure procedure, a procedure-name actual-arg shall be the name of a 19 pure procedure (12.6). NOTE 12.17 This constraint ensures that the purity of a procedure cannot be undermined by allowing it to call a nonpure procedure. 20C1231 (R1222) The label used in the alt-return-spec shall be the statement label of a branch target statement that 21 appears in the same scoping unit as the call-stmt. NOTE 12.18 Successive commas shall not be used to omit optional arguments. NOTE 12.19 Examples of procedure reference using procedure pointers: P => BESSEL WRITE (*, *) P(2.5) !-- BESSEL(2.5) S => PRINT_REAL CALL S(3.14) 267 J3/04-007 WORKING DRAFT MAY 2004 112.4.1 Actual arguments, dummy arguments, and argument association 2In either a subroutine reference or a function reference, the actual argument list identifies the corre- 3spondence between the actual arguments supplied and the dummy arguments of the procedure. This 4correspondence may be established either by keyword or by position. If an argument keyword appears, 5the actual argument is associated with the dummy argument whose name is the same as the argument 6keyword (using the dummy argument names from the interface accessible in the scoping unit containing 7the procedure reference). In the absence of an argument keyword, an actual argument is associated 8with the dummy argument occupying the corresponding position in the reduced dummy argument list; 9that is, the first actual argument is associated with the first dummy argument in the reduced list, the 10second actual argument is associated with the second dummy argument in the reduced list, etc. The 11reduced dummy argument list is either the full dummy argument list or, if there is a passed-object 12dummy argument (4.5.3.3), the dummy argument list with the passed object dummy argument omitted. 13Exactly one actual argument shall be associated with each nonoptional dummy argument. At most one 14actual argument may be associated with each optional dummy argument. Each actual argument shall 15be associated with a dummy argument. NOTE 12.20 For example, the procedure defined by SUBROUTINE SOLVE (FUNCT, SOLUTION, METHOD, STRATEGY, PRINT) INTERFACE FUNCTION FUNCT (X) REAL FUNCT, X END FUNCTION FUNCT END INTERFACE REAL SOLUTION INTEGER, OPTIONAL :: METHOD, STRATEGY, PRINT ... may be invoked with CALL SOLVE (FUN, SOL, PRINT = 6) provided its interface is explicit; if the interface is specified by an interface block, the name of the last argument shall be PRINT. 1612.4.1.1 The passed-object dummy argument and argument association 17In a reference to a type-bound procedure that has a passed-object dummy argument (4.5.3.3), the data- 18ref of the function-reference or call-stmt is associated, as an actual argument, with the passed-object 19dummy argument. 2012.4.1.2 Actual arguments associated with dummy data objects 21If a dummy argument is neither allocatable nor a pointer, it shall be type compatible (5.1.1.2) with 22the associated actual argument. If a dummy argument is allocatable or a pointer, the associated actual 23argument shall be polymorphic if and only if the dummy argument is polymorphic, and the declared 24type of the actual argument shall be the same as the declared type of the dummy argument. NOTE 12.21 The dynamic type of a polymorphic allocatable or pointer dummy argument may change as a result of execution of an allocate statement or pointer assignment in the subprogram. Because of this the corresponding actual argument needs to be polymorphic and have a declared type that 268 MAY 2004 WORKING DRAFT J3/04-007 NOTE 12.21 (cont.) is the same as the declared type of the dummy argument or an extension of that type. However, type compatibility requires that the declared type of the dummy argument be the same as, or an extension of, the type of the actual argument. Therefore, the dummy and actual arguments need to have the same declared type. Dynamic type information is not maintained for a nonpolymorphic allocatable or pointer dummy argument. However, allocating or pointer assigning such a dummy argument would require main- tenance of this information if the corresponding actual argument is polymorphic. Therefore, the corresponding actual argument needs to be nonpolymorphic. 1The type parameter values of the actual argument shall agree with the corresponding ones of the dummy 2argument that are not assumed or deferred, except for the case of the character length parameter of 3an actual argument of type default character associated with a dummy argument that is not assumed 4shape. 5If a scalar dummy argument is of type default character, the length len of the dummy argument shall 6be less than or equal to the length of the actual argument. The dummy argument becomes associated 7with the leftmost len characters of the actual argument. If an array dummy argument is of type default 8character and is not assumed shape, it becomes associated with the leftmost characters of the actual 9argument element sequence (12.4.1.5) and it shall not extend beyond the end of that sequence. 10The values of assumed type parameters of a dummy argument are assumed from the corresponding type 11parameters of the associated actual argument. 12An actual argument associated with a dummy argument that is allocatable or a pointer shall have 13deferred the same type parameters as the dummy argument. 14If the dummy argument is a pointer, the actual argument shall be a pointer and the nondeferred type 15parameters and ranks shall agree. If a dummy argument is allocatable, the actual argument shall be 16allocatable and the nondeferred type parameters and ranks shall agree. It is permissible for the actual 17argument to have an allocation status of unallocated. 18At the invocation of the procedure, the pointer association status of an actual argument associated with 19a pointer dummy argument becomes undefined if the dummy argument has INTENT(OUT). 20Except in references to intrinsic inquiry functions, if the dummy argument is not a pointer and the 21corresponding actual argument is a pointer, the actual argument shall be associated with a target and 22the dummy argument becomes argument associated with that target. 23Except in references to intrinsic inquiry functions, if the dummy argument is not allocatable and the 24actual argument is allocatable, the actual argument shall be allocated. 25If the dummy argument has the VALUE attribute it becomes associated with a definable anonymous 26data object whose initial value is that of the actual argument. Subsequent changes to the value or 27definition status of the dummy argument do not affect the actual argument. NOTE 12.22 Fortran argument association is usually similar to call by reference and call by value-result. If the VALUE attribute is specified, the effect is as if the actual argument is assigned to a temporary, and the temporary is then argument associated with the dummy argument. The actual mechanism by which this happens is determined by the processor. 28If the dummy argument does not have the TARGET or POINTER attribute, any pointers associated 29with the actual argument do not become associated with the corresponding dummy argument on in- 269 J3/04-007 WORKING DRAFT MAY 2004 1vocation of the procedure. If such a dummy argument is associated with an actual argument that is 2a dummy argument with the TARGET attribute, whether any pointers associated with the original 3actual argument become associated with the dummy argument with the TARGET attribute is processor 4dependent. 5If the dummy argument has the TARGET attribute, does not have the VALUE attribute, and is either 6a scalar or an assumed-shape array, and the corresponding actual argument has the TARGET attribute 7but is not an array section with a vector subscript then 8 (1) Any pointers associated with the actual argument become associated with the corresponding 9 dummy argument on invocation of the procedure and 10 (2) When execution of the procedure completes, any pointers that do not become undefined 11 (16.4.2.1.3) and are associated with the dummy argument remain associated with the actual 12 argument. 13If the dummy argument has the TARGET attribute and is an explicit-shape array or is an assumed-size 14array, and the corresponding actual argument has the TARGET attribute but is not an array section 15with a vector subscript then 16 (1) On invocation of the procedure, whether any pointers associated with the actual argument 17 become associated with the corresponding dummy argument is processor dependent and 18 (2) When execution of the procedure completes, the pointer association status of any pointer 19 that is pointer associated with the dummy argument is processor dependent. 20If the dummy argument has the TARGET attribute and the corresponding actual argument does not 21have the TARGET attribute or is an array section with a vector subscript, any pointers associated with 22the dummy argument become undefined when execution of the procedure completes. 23If the dummy argument has the TARGET attribute and the VALUE attribute, any pointers associated 24with the dummy argument become undefined when execution of the procedure completes. 25If the actual argument is scalar, the corresponding dummy argument shall be scalar unless the actual 26argument is of type default character, of type character with the C character kind (15.1), or is an element 27or substring of an element of an array that is not an assumed-shape or pointer array. If the procedure 28is nonelemental and is referenced by a generic name or as a defined operator or defined assignment, the 29ranks of the actual arguments and corresponding dummy arguments shall agree. 30If a dummy argument is an assumed-shape array, the rank of the actual argument shall be the same as 31the rank of the dummy argument; the actual argument shall not be an assumed-size array (including an 32array element designator or an array element substring designator). 33Except when a procedure reference is elemental (12.7), each element of an array actual argument or of 34a sequence in a sequence association (12.4.1.5) is associated with the element of the dummy array that 35has the same position in array element order (6.2.2.2). NOTE 12.23 For type default character sequence associations, the interpretation of element is provided in 12.4.1.5. 36A scalar dummy argument of a nonelemental procedure may be associated only with a scalar actual 37argument. 38If a nonpointer dummy argument has INTENT (OUT) or INTENT (INOUT), the actual argument shall 39be definable. If a dummy argument has INTENT (OUT), the corresponding actual argument becomes 40undefined at the time the association is established, except for components of an object of derived type 41for which default initialization has been specified. If the dummy argument is not polymorphic and the 270 MAY 2004 WORKING DRAFT J3/04-007 1type of the actual argument is an extension type of the type of the dummy argument, only the part of 2the actual argument that is of the same type as the dummy argument becomes undefined. 3If the actual argument is an array section having a vector subscript, the dummy argument is not defin- 4able and shall not have the INTENT (OUT), INTENT (INOUT), VOLATILE, or ASYNCHRONOUS 5attributes. NOTE 12.24 Argument intent specifications serve several purposes. See Note 5.14. NOTE 12.25 For more explanatory information on argument association and evaluation, see section C.9.5. For more explanatory information on pointers and targets as dummy arguments, see section C.9.6. 6C1232 (R1221) If an actual argument is an array section or an assumed-shape array, and the corre- 7 sponding dummy argument has either the VOLATILE or ASYNCHRONOUS attribute, that 8 dummy argument shall be an assumed-shape array. 9C1233 (R1221) If an actual argument is a pointer array, and the corresponding dummy argument 10 has either the VOLATILE or ASYNCHRONOUS attribute, that dummy argument shall be an 11 assumed-shape array or a pointer array. NOTE 12.26 The constraints on actual arguments that correspond to a dummy argument with either the ASYN- CHRONOUS or VOLATILE attribute are designed to avoid forcing a processor to use the so-called copy-in/copy-out argument passing mechanism. Making a copy of actual arguments whose values are likely to change due to an asynchronous I/O operation completing or in some unpredictable manner will cause those new values to be lost when a called procedure returns and the copy-out overwrites the actual argument. 1212.4.1.3 Actual arguments associated with dummy procedure entities 13If a dummy argument is a procedure pointer, the associated actual argument shall be a procedure pointer, 14a reference to a function that returns a procedure pointer, or a reference to the NULL intrinsic function. 15If a dummy argument is a dummy procedure without the POINTER attribute, the associated actual 16argument shall be the specific name of an external, module, dummy, or intrinsic procedure, an associated 17procedure pointer, or a reference to a function that returns an associated procedure pointer. The only 18intrinsic procedures permitted are those listed in 13.6 and not marked with a bullet (·). If the specific 19name is also a generic name, only the specific procedure is associated with the dummy argument. 20If an external procedure name or a dummy procedure name is used as an actual argument, its interface 21shall be explicit or it shall be explicitly declared to have the EXTERNAL attribute. 22If the interface of the dummy argument is explicit, the characteristics listed in 12.2 shall be the same 23for the associated actual argument and the corresponding dummy argument, except that a pure actual 24argument may be associated with a dummy argument that is not pure and an elemental intrinsic actual 25procedure may be associated with a dummy procedure (which is prohibited from being elemental). 26If the interface of the dummy argument is implicit and either the name of the dummy argument is 27explicitly typed or it is referenced as a function, the dummy argument shall not be referenced as a 28subroutine and the actual argument shall be a function, function procedure pointer, or dummy procedure. 29If the interface of the dummy argument is implicit and a reference to it appears as a subroutine reference, 271 J3/04-007 WORKING DRAFT MAY 2004 1the actual argument shall be a subroutine, subroutine procedure pointer, or dummy procedure. 212.4.1.4 Actual arguments associated with alternate return indicators 3 If a dummy argument is an asterisk (12.5.2.2), the associated actual argument shall be an alternate return specifier (12.4). 412.4.1.5 Sequence association 5An actual argument represents an element sequence if it is an array expression, an array element 6designator, a scalar of type default character, or a scalar of type character with the C character kind 7(15.1.1). If the actual argument is an array expression, the element sequence consists of the elements 8in array element order. If the actual argument is an array element designator, the element sequence 9consists of that array element and each element that follows it in array element order. 10If the actual argument is of type default character or of type character with the C character kind, and is 11an array expression, array element, or array element substring designator, the element sequence consists 12of the storage units beginning with the first storage unit of the actual argument and continuing to the 13end of the array. The storage units of an array element substring designator are viewed as array elements 14consisting of consecutive groups of storage units having the character length of the dummy array. 15If the actual argument is of type default character or of type character with the C character kind, and 16is a scalar that is not an array element or array element substring designator, the element sequence 17consists of the storage units of the actual argument. NOTE 12.27 Some of the elements in the element sequence may consist of storage units from different elements of the original array. 18An actual argument that represents an element sequence and corresponds to a dummy argument that is 19an array is sequence associated with the dummy argument if the dummy argument is an explicit-shape 20or assumed-size array. The rank and shape of the actual argument need not agree with the rank and 21shape of the dummy argument, but the number of elements in the dummy argument shall not exceed 22the number of elements in the element sequence of the actual argument. If the dummy argument is 23assumed-size, the number of elements in the dummy argument is exactly the number of elements in the 24element sequence. 2512.4.1.6 Restrictions on dummy arguments not present 26A dummy argument or an entity that is host associated with a dummy argument is not present if the 27dummy argument 28 (1) is not associated with an actual argument, or 29 (2) is associated with an actual argument that is not present. 30Otherwise, it is present. A dummy argument that is not optional shall be present. An optional dummy 31argument that is not present is subject to the following restrictions: 32 (1) If it is a data object, it shall not be referenced or be defined. If it is of a type for which 33 default initialization is specified for some component, the initialization has no effect. 34 (2) It shall not be used as the data-target or proc-target of a pointer assignment. 35 (3) If it is a procedure or procedure pointer, it shall not be invoked. 36 (4) It shall not be supplied as an actual argument corresponding to a nonoptional dummy 37 argument other than as the argument of the PRESENT intrinsic function or as an argument 38 of a function reference that meets the requirements of (6) or (8) in 7.1.7. 272 MAY 2004 WORKING DRAFT J3/04-007 1 (5) A designator with it as the base object and with at least one component selector, array 2 section selector, array element selector, or substring selector shall not be supplied as an 3 actual argument. 4 (6) If it is an array, it shall not be supplied as an actual argument to an elemental procedure 5 unless an array of the same rank is supplied as an actual argument corresponding to a 6 nonoptional dummy argument of that elemental procedure. 7 (7) If it is a pointer, it shall not be allocated, deallocated, nullified, pointer-assigned, or supplied 8 as an actual argument corresponding to an optional nonpointer dummy argument. 9 (8) If it is allocatable, it shall not be allocated, deallocated, or supplied as an actual argument 10 corresponding to an optional nonallocatable dummy argument. 11 (9) If it has length type parameters, they shall not be the subject of an inquiry. 12 (10) It shall not be used as the selector in a SELECT TYPE or ASSOCIATE construct. 13Except as noted in the list above, it may be supplied as an actual argument corresponding to an optional 14dummy argument, which is then also considered not to be associated with an actual argument. 1512.4.1.7 Restrictions on entities associated with dummy arguments 16While an entity is associated with a dummy argument, the following restrictions hold: 17 (1) Action that affects the allocation status of the entity or a subobject thereof shall be taken 18 through the dummy argument. Action that affects the value of the entity or any subobject 19 of it shall be taken only through the dummy argument unless 20 (a) the dummy argument has the POINTER attribute or 21 (b) the dummy argument has the TARGET attribute, the dummy argument does not 22 have INTENT (IN), the dummy argument is a scalar object or an assumed-shape 23 array, and the actual argument is a target other than an array section with a vector 24 subscript. NOTE 12.28 In SUBROUTINE OUTER REAL, POINTER :: A (:) ... ALLOCATE (A (1:N)) ... CALL INNER (A) ... CONTAINS SUBROUTINE INNER (B) REAL :: B (:) ... END SUBROUTINE INNER SUBROUTINE SET (C, D) REAL, INTENT (OUT) :: C REAL, INTENT (IN) :: D C = D END SUBROUTINE SET END SUBROUTINE OUTER an assignment statement such as 273 J3/04-007 WORKING DRAFT MAY 2004 NOTE 12.28 (cont.) A (1) = 1.0 would not be permitted during the execution of INNER because this would be changing A without using B, but statements such as B (1) = 1.0 or CALL SET (B (1), 1.0) would be allowed. Similarly, DEALLOCATE (A) would not be allowed because this affects the allocation of B without using B. In this case, DEALLOCATE (B) also would not be permitted. If B were declared with the POINTER attribute, either of the statements DEALLOCATE (A) and DEALLOCATE (B) would be permitted, but not both. NOTE 12.29 If there is a partial or complete overlap between the actual arguments associated with two different dummy arguments of the same procedure and the dummy arguments have neither the POINTER nor TARGET attribute, the overlapped portions shall not be defined, redefined, or become unde- fined during the execution of the procedure. For example, in CALL SUB (A (1:5), A (3:9)) A (3:5) shall not be defined, redefined, or become undefined through the first dummy argument because it is part of the argument associated with the second dummy argument and shall not be defined, redefined, or become undefined through the second dummy argument because it is part of the argument associated with the first dummy argument. A (1:2) remains definable through the first dummy argument and A (6:9) remains definable through the second dummy argument. NOTE 12.30 This restriction applies equally to pointer targets. In REAL, DIMENSION (10), TARGET :: A REAL, DIMENSION (:), POINTER :: B, C B => A (1:5) C => A (3:9) 274 MAY 2004 WORKING DRAFT J3/04-007 NOTE 12.30 (cont.) CALL SUB (B, C) ! The dummy arguments of SUB are neither pointers nor targets. B (3:5) cannot be defined because it is part of the argument associated with the second dummy argument. C (1:3) cannot be defined because it is part of the argument associated with the first dummy argument. A (1:2) [which is B (1:2)] remains definable through the first dummy argument and A (6:9) [which is C (4:7)] remains definable through the second dummy argument. NOTE 12.31 Because a nonpointer dummy argument declared with INTENT(IN) shall not be used to change the associated actual argument, the associated actual argument remains constant throughout the execution of the procedure. 1 (2) If the allocation status of the entity or a subobject thereof is affected through the dummy 2 argument, then at any time during the execution of the procedure, either before or after 3 the allocation or deallocation, it may be referenced only through the dummy argument. If 4 the value the entity or any subobject of it is affected through the dummy argument, then 5 at any time during the execution of the procedure, either before or after the definition, it 6 may be referenced only through that dummy argument unless 7 (a) the dummy argument has the POINTER attribute or 8 (b) the dummy argument has the TARGET attribute, the dummy argument does not 9 have INTENT (IN), the dummy argument is a scalar object or an assumed-shape 10 array, and the actual argument is a target other than an array section with a vector 11 subscript. NOTE 12.32 In MODULE DATA REAL :: W, X, Y, Z END MODULE DATA PROGRAM MAIN USE DATA ... CALL INIT (X) ... END PROGRAM MAIN SUBROUTINE INIT (V) USE DATA ... READ (*, *) V ... END SUBROUTINE INIT variable X shall not be directly referenced at any time during the execution of INIT because it is being defined through the dummy argument V. X may be (indirectly) referenced through V. W, Y, and Z may be directly referenced. X may, of course, be directly referenced once execution of INIT is complete. 275 J3/04-007 WORKING DRAFT MAY 2004 NOTE 12.33 The restrictions on entities associated with dummy arguments are intended to facilitate a variety of optimizations in the translation of the subprogram, including implementations of argument association in which the value of an actual argument that is neither a pointer nor a target is maintained in a register or in local storage. 112.4.2 Function reference 2A function is invoked during expression evaluation by a function-reference or by a defined operation 3(7.1.3). When it is invoked, all actual argument expressions are evaluated, then the arguments are 4associated, and then the function is executed. When execution of the function is complete, the value 5of the function result is available for use in the expression that caused the function to be invoked. The 6characteristics of the function result (12.2.2) are determined by the interface of the function. A reference 7to an elemental function (12.7) is an elemental reference if one or more actual arguments are arrays and 8all array arguments have the same shape. 912.4.3 Subroutine reference 10A subroutine is invoked by execution of a CALL statement, execution of a defined assignment statement 11(7.4.1.4), user-defined derived-type input/output(9.5.3.7.1), or finalization(4.5.5). When a subroutine is 12invoked, all actual argument expressions are evaluated, then the arguments are associated, and then the 13subroutine is executed. When the actions specified by the subroutine are completed, the execution of 14the CALL statement, the execution of the defined assignment statement, or the processing of an input 15or output list item is also completed. If a CALL statement includes one or more alternate return specifiers among 16 its arguments, control may be transferred to one of the statements indicated, depending on the action specified by the 17 subroutine. A reference to an elemental subroutine (12.7) is an elemental reference if there is at least one 18actual argument corresponding to an INTENT(OUT) or INTENT(INOUT) dummy argument, all such 19actual arguments are arrays, and all actual arguments are conformable. 2012.4.4 Resolving named procedure references 21The rules for interpreting a procedure reference depend on whether the procedure name in the reference 22is established by the available declarations and specifications to be generic in the scoping unit containing 23the reference, is established to be only specific in the scoping unit containing the reference, or is not 24established. 25 (1) A procedure name is established to be generic in a scoping unit 26 (a) if that scoping unit contains an interface block with that name; 27 (b) if that scoping unit contains an INTRINSIC attribute specification for that name and 28 it is the name of a generic intrinsic procedure; 29 (c) if that scoping unit contains a USE statement that makes that procedure name ac- 30 cessible and the corresponding name in the module is established to be generic; or 31 (d) if that scoping unit contains no declarations of that name, that scoping unit has a 32 host scoping unit, and that name is established to be generic in the host scoping unit. 33 (2) A procedure name is established to be only specific in a scoping unit if it is established to 34 be specific and not established to be generic. It is established to be specific 35 (a) if that scoping unit contains a module subprogram, internal subprogram, or statement 36 function that defines a procedure with that name; 37 (b) if that scoping unit contains an INTRINSIC attribute specification for that name and 38 if it is the name of a specific intrinsic procedure; 39 (c) if that scoping unit contains an explicit EXTERNAL attribute specification (5.1.2.6) 40 for that name; 276 MAY 2004 WORKING DRAFT J3/04-007 1 (d) if that scoping unit contains a USE statement that makes that procedure name ac- 2 cessible and the corresponding name in the module is established to be specific; or 3 (e) if that scoping unit contains no declarations of that name, that scoping unit has a 4 host scoping unit, and that name is established to be specific in the host scoping unit. 5 (3) A procedure name is not established in a scoping unit if it is neither established to be generic 6 nor established to be specific. 712.4.4.1 Resolving procedure references to names established to be generic 8 (1) If the reference is consistent with a nonelemental reference to one of the specific interfaces of 9 a generic interface that has that name and either is in the scoping unit in which the reference 10 appears or is made accessible by a USE statement in the scoping unit, the reference is to 11 the specific procedure in the interface block that provides that interface. The rules in 16.2.3 12 ensure that there can be at most one such specific procedure. 13 (2) If (1) does not apply, if the reference is consistent with an elemental reference to one of the 14 specific interfaces of a generic interface that has that name and either is in the scoping unit 15 in which the reference appears or is made accessible by a USE statement in the scoping unit, 16 the reference is to the specific elemental procedure in the interface block that provides that 17 interface. The rules in 16.2.3 ensure that there can be at most one such specific elemental 18 procedure. NOTE 12.34 These rules allow particular instances of a generic function to be used for particular array ranks and a general elemental version to be used for other ranks. Given an interface block such as: INTERFACE RANF ELEMENTAL FUNCTION SCALAR_RANF(X) REAL, INTENT(IN) :: X END FUNCTION SCALAR_RANF FUNCTION VECTOR_RANDOM(X) REAL X(:) REAL VECTOR_RANDOM(SIZE(X)) END FUNCTION VECTOR_RANDOM END INTERFACE RANF and a declaration such as: REAL A(10,10), AA(10,10) then the statement A = RANF(AA) is an elemental reference to SCALAR RANF. The statement A = RANF(AA(6:10,2)) is a nonelemental reference to VECTOR RANDOM. 19 (3) If (1) and (2) do not apply, if the scoping unit contains either an INTRINSIC attribute 20 specification for that name or a USE statement that makes that name accessible from a 21 module in which the corresponding name is specified to have the INTRINSIC attribute, and 22 if the reference is consistent with the interface of that intrinsic procedure, the reference is 23 to that intrinsic procedure. 277 J3/04-007 WORKING DRAFT MAY 2004 NOTE 12.35 In the USE statement case, it is possible, because of the renaming facility, for the name in the reference to be different from the name of the intrinsic procedure. 1 (4) If (1), (2), and (3) do not apply, if the scoping unit has a host scoping unit, if the name 2 is established to be generic in that host scoping unit, and if there is agreement between 3 the scoping unit and the host scoping unit as to whether the name is a function name or 4 a subroutine name, the name is resolved by applying the rules in this section to the host 5 scoping unit. 612.4.4.2 Resolving procedure references to names established to be only specific 7 (1) If the scoping unit contains an interface body or EXTERNAL attribute specification for the 8 name, if the scoping unit is a subprogram, and if the name is the name of a dummy argument 9 of that subprogram, the dummy argument is a dummy procedure and the reference is to 10 that dummy procedure. That is, the procedure invoked by executing that reference is the 11 procedure supplied as the actual argument corresponding to that dummy procedure. 12 (2) If the scoping unit contains an interface body or EXTERNAL attribute specification for the 13 name and if (1) does not apply, the reference is to an external procedure with that name. 14 (3) If the scoping unit contains a module subprogram, internal subprogram, or statement function 15 that defines a procedure with the name, the reference is to the procedure so defined. 16 (4) If the scoping unit contains an INTRINSIC attribute specification for the name, the reference 17 is to the intrinsic with that name. 18 (5) If the scoping unit contains a USE statement that makes a procedure accessible by the 19 name, the reference is to that procedure. NOTE 12.36 Because of the renaming facility of the USE statement, the name in the reference may be different from the original name of the procedure. 20 (6) If none of the above apply, the scoping unit shall have a host scoping unit, and the reference 21 is resolved by applying the rules in this section to the host scoping unit. 2212.4.4.3 Resolving procedure references to names not established 23 (1) If the scoping unit is a subprogram and if the name is the name of a dummy argument 24 of that subprogram, the dummy argument is a dummy procedure and the reference is to 25 that dummy procedure. That is, the procedure invoked by executing that reference is the 26 procedure supplied as the actual argument corresponding to that dummy procedure. 27 (2) If (1) does not apply, if the name is the name of an intrinsic procedure, and if there is 28 agreement between the reference and the status of the intrinsic procedure as being a function 29 or subroutine, the reference is to that intrinsic procedure. 30 (3) If (1) and (2) do not apply, the reference is to an external procedure with that name. 3112.4.5 Resolving type-bound procedure references 32If the binding-name in a procedure-designator (R1219) is that of a specific type-bound procedure, the 33procedure referenced is the one bound to that name in the dynamic type of the data-ref . 34If the binding-name in a procedure-designator is that of a generic type bound procedure, the generic 35binding with that name in the declared type of the data-ref is used to select a specific binding: 36 (1) If the reference is consistent with one of the specific bindings of that generic binding, that 37 specific binding is selected. 38 (2) Otherwise, the reference shall be consistent with an elemental reference to one of the specific 39 bindings of that generic binding; that specific binding is selected. 278 MAY 2004 WORKING DRAFT J3/04-007 1The reference is to the procedure bound to the same name as the selected specific binding in the dynamic 2type of the data-ref . 312.5 Procedure definition 412.5.1 Intrinsic procedure definition 5Intrinsic procedures are defined as an inherent part of the processor. A standard-conforming processor 6shall include the intrinsic procedures described in Section 13, but may include others. However, a 7standard-conforming program shall not make use of intrinsic procedures other than those described in 8Section 13. 912.5.2 Procedures defined by subprograms 10When a procedure defined by a subprogram is invoked, an instance (12.5.2.3) of the subprogram is 11created and executed. Execution begins with the first executable construct following the FUNCTION, 12SUBROUTINE, or ENTRY statement specifying the name of the procedure invoked. 1312.5.2.1 Function subprogram 14A function subprogram is a subprogram that has a FUNCTION statement as its first statement. 15R1223 function-subprogram is function-stmt 16 [ specification-part ] 17 [ execution-part ] 18 [ internal-subprogram-part ] 19 end-function-stmt 20R1224 function-stmt is [ prefix ] FUNCTION function-name 21 ( [ dummy-arg-name-list ] ) [ suffix ] 22C1234 (R1224) If RESULT is specified, result-name shall not be the same as function-name and shall 23 not be the same as the entry-name in any ENTRY statement in the subprogram. 24C1235 (R1224) If RESULT is specified, the function-name shall not appear in any specification state- 25 ment in the scoping unit of the function subprogram. 26R1225 proc-language-binding-spec is language-binding-spec 27C1236 (R1225) A proc-language-binding-spec with a NAME= specifier shall not be specified in the 28 function-stmt or subroutine-stmt of an interface body for an abstract interface or a dummy 29 procedure. 30C1237 (R1225) A proc-language-binding-spec shall not be specified for an internal procedure. 31C1238 (R1225) If proc-language-binding-spec is specified for a procedure, each of the procedure's dummy 32 arguments shall be a nonoptional interoperable variable (15.2.4, 15.2.5) or a nonoptional interop- 33 erable procedure (15.2.6). If proc-language-binding-spec is specified for a function, the function 34 result shall be an interoperable scalar variable. 35R1226 dummy-arg-name is name 36C1239 (R1226) A dummy-arg-name shall be the name of a dummy argument. 37R1227 prefix is prefix-spec [ prefix-spec ] ... 38R1228 prefix-spec is declaration-type-spec 279 J3/04-007 WORKING DRAFT MAY 2004 1 or RECURSIVE 2 or PURE 3 or ELEMENTAL 4C1240 (R1227) A prefix shall contain at most one of each prefix-spec. 5C1241 (R1227) A prefix shall not specify both ELEMENTAL and RECURSIVE. 6C1242 (R1227) A prefix shall not specify ELEMENTAL if proc-language-binding-spec appears in the 7 function-stmt or subroutine-stmt. 8R1229 suffix is proc-language-binding-spec [ RESULT ( result-name ) ] 9 or RESULT ( result-name ) [ proc-language-binding-spec ] 10R1230 end-function-stmt is END [ FUNCTION [ function-name ] ] 11C1243 (R1230) FUNCTION shall appear in the end-function-stmt of an internal or module function. 12C1244 (R1223) An internal function subprogram shall not contain an ENTRY statement. 13C1245 (R1223) An internal function subprogram shall not contain an internal-subprogram-part. 14C1246 (R1230) If a function-name appears in the end-function-stmt, it shall be identical to the function- 15 name specified in the function-stmt. 16The name of the function is function-name. 17The type and type parameters (if any) of the result of the function defined by a function subprogram 18may be specified by a type specification in the FUNCTION statement or by the name of the result 19variable appearing in a type declaration statement in the declaration part of the function subprogram. 20They shall not be specified both ways. If they are not specified either way, they are determined by 21the implicit typing rules in force within the function subprogram. If the function result is an array, 22allocatable, or a pointer, this shall be specified by specifications of the name of the result variable within 23the function body. The specifications of the function result attributes, the specification of dummy 24argument attributes, and the information in the procedure heading collectively define the characteristics 25of the function (12.2). 26The prefix-spec RECURSIVE shall appear if the function directly or indirectly invokes itself or a function 27defined by an ENTRY statement in the same subprogram. Similarly, RECURSIVE shall appear if a 28function defined by an ENTRY statement in the subprogram directly or indirectly invokes itself, another 29function defined by an ENTRY statement in that subprogram, or the function defined by the FUNCTION 30statement. 31If RESULT is specified, the name of the result variable of the function is result-name and all occurrences 32of the function name in execution-part statements in the scoping unit refer to the function itself. If 33RESULT is not specified, the result variable is function-name and all occurrences of the function name 34in execution-part statements in the scoping unit are references to the result variable. The characteristics 35(12.2.2) of the function result are those of the result variable. On completion of execution of the function, 36the value returned is that of its result variable. If the function result is a pointer, the shape of the value 37returned by the function is determined by the shape of the result variable when the execution of the 38function is completed. If the result variable is not a pointer, its value shall be defined by the function. 39If the function result is a pointer, the function shall either associate a target with the result variable 40pointer or cause the association status of this pointer to become defined as disassociated. NOTE 12.37 The result variable is similar to any other variable local to a function subprogram. Its existence begins when execution of the function is initiated and ends when execution of the function is 280 MAY 2004 WORKING DRAFT J3/04-007 NOTE 12.37 (cont.) terminated. However, because the final value of this variable is used subsequently in the evaluation of the expression that invoked the function, an implementation may wish to defer releasing the storage occupied by that variable until after its value has been used in expression evaluation. 1If the prefix-spec PURE or ELEMENTAL appears, the subprogram is a pure subprogram and shall meet 2the additional constraints of 12.6. 3If the prefix-spec ELEMENTAL appears, the subprogram is an elemental subprogram and shall meet 4the additional constraints of 12.7.1. NOTE 12.38 An example of a recursive function is: RECURSIVE FUNCTION CUMM_SUM (ARRAY) RESULT (C_SUM) REAL, INTENT (IN), DIMENSION (:) :: ARRAY REAL, DIMENSION (SIZE (ARRAY)) ::C_SUM INTEGER N N = SIZE (ARRAY) IF (N <= 1) THEN C_SUM = ARRAY ELSE N = N / 2 C_SUM (:N) = CUMM_SUM (ARRAY (:N)) C_SUM (N+1:) = C_SUM (N) + CUMM_SUM (ARRAY (N+1:)) END IF END FUNCTION CUMM_SUM NOTE 12.39 The following is an example of the declaration of an interface body with the BIND attribute, and a reference to the procedure declared. USE, INTRINSIC :: ISO_C_BINDING INTERFACE FUNCTION JOE (I, J, R) BIND(C,NAME="FrEd") USE, INTRINSIC :: ISO_C_BINDING INTEGER(C_INT) :: JOE INTEGER(C_INT), VALUE :: I, J REAL(C_FLOAT), VALUE :: R END FUNCTION JOE END INTERFACE INT = JOE(1_C_INT, 3_C_INT, 4.0_C_FLOAT) END PROGRAM The invocation of the function JOE results in a reference to a function with a binding label "FrEd". FrEd may be a C function described by the C prototype int FrEd(int n, int m, float x); 281 J3/04-007 WORKING DRAFT MAY 2004 112.5.2.2 Subroutine subprogram 2A subroutine subprogram is a subprogram that has a SUBROUTINE statement as its first statement. 3R1231 subroutine-subprogram is subroutine-stmt 4 [ specification-part ] 5 [ execution-part ] 6 [ internal-subprogram-part ] 7 end-subroutine-stmt 8R1232 subroutine-stmt is [ prefix ] SUBROUTINE subroutine-name 9 [ ( [ dummy-arg-list ] ) [ proc-language-binding-spec ] ] 10C1247 (R1232) The prefix of a subroutine-stmt shall not contain a declaration-type-spec. 11R1233 dummy-arg is dummy-arg-name 12 or * 13R1234 end-subroutine-stmt is END [ SUBROUTINE [ subroutine-name ] ] 14C1248 (R1234) SUBROUTINE shall appear in the end-subroutine-stmt of an internal or module sub- 15 routine. 16C1249 (R1231) An internal subroutine subprogram shall not contain an ENTRY statement. 17C1250 (R1231) An internal subroutine subprogram shall not contain an internal-subprogram-part. 18C1251 (R1234) If a subroutine-name appears in the end-subroutine-stmt, it shall be identical to the 19 subroutine-name specified in the subroutine-stmt. 20The name of the subroutine is subroutine-name. 21The prefix-spec RECURSIVE shall appear if the subroutine directly or indirectly invokes itself or a 22subroutine defined by an ENTRY statement in the same subprogram. Similarly, RECURSIVE shall 23appear if a subroutine defined by an ENTRY statement in the subprogram directly or indirectly invokes 24itself, another subroutine defined by an ENTRY statement in that subprogram, or the subroutine defined 25by the SUBROUTINE statement. 26If the prefix-spec PURE or ELEMENTAL appears, the subprogram is a pure subprogram and shall meet 27the additional constraints of 12.6. 28If the prefix-spec ELEMENTAL appears, the subprogram is an elemental subprogram and shall meet 29the additional constraints of 12.7.1. 3012.5.2.3 Instances of a subprogram 31When a function or subroutine defined by a subprogram is invoked, an instance of that subprogram is 32created. When a statement function is invoked, an instance of that statement function is created. 33Each instance has an independent sequence of execution and an independent set of dummy arguments 34and local unsaved data objects. If an internal procedure or statement function in the subprogram is invoked 35directly from an instance of the subprogram or from an internal subprogram or statement function that 36has access to the entities of that instance, the created instance of the internal subprogram or statement 37 function also has access to the entities of that instance of the host subprogram. 38All other entities are shared by all instances of the subprogram. 282 MAY 2004 WORKING DRAFT J3/04-007 NOTE 12.40 The value of a saved data object appearing in one instance may have been defined in a previous instance or by initialization in a DATA statement or type declaration statement. 112.5.2.4 ENTRY statement 2An ENTRY statement permits a procedure reference to begin with a particular executable statement 3within the function or subroutine subprogram in which the ENTRY statement appears. 4R1235 entry-stmt is ENTRY entry-name [ ( [ dummy-arg-list ] ) [ suffix ] ] 5C1252 (R1235) If RESULT is specified, the entry-name shall not appear in any specification or type- 6 declaration statement in the scoping unit of the function program. 7C1253 (R1235) An entry-stmt shall appear only in an external-subprogram or module-subprogram. An 8 entry-stmt shall not appear within an executable-construct. 9C1254 (R1235) RESULT shall appear only if the entry-stmt is in a function subprogram. 10C1255 (R1235) Within the subprogram containing the entry-stmt, the entry-name shall not appear 11 as a dummy argument in the FUNCTION or SUBROUTINE statement or in another ENTRY 12 statement nor shall it appear in an EXTERNAL, INTRINSIC, or PROCEDURE statement. 13C1256 (R1235) A dummy-arg shall not be an alternate return indicator if the ENTRY statement is in a function 14 subprogram. 15C1257 (R1235) If RESULT is specified, result-name shall not be the same as the function-name in the 16 FUNCTION statement and shall not be the same as the entry-name in any ENTRY statement 17 in the subprogram. 18Optionally, a subprogram may have one or more ENTRY statements. 19If the ENTRY statement is in a function subprogram, an additional function is defined by that subpro- 20gram. The name of the function is entry-name and the name of its result variable is result-name or 21is entry-name if no result-name is provided. The characteristics of the function result are specified by 22specifications of the result variable. The dummy arguments of the function are those specified in the 23ENTRY statement. If the characteristics of the result of the function named in the ENTRY statement 24are the same as the characteristics of the result of the function named in the FUNCTION statement, 25their result variables identify the same variable, although their names need not be the same. Otherwise, 26they are storage associated and shall all be nonpointer, nonallocatable scalars of type default integer, 27default real, double precision real, default complex, or default logical. 28If the ENTRY statement is in a subroutine subprogram, an additional subroutine is defined by that 29subprogram. The name of the subroutine is entry-name. The dummy arguments of the subroutine are 30those specified in the ENTRY statement. 31The order, number, types, kind type parameters, and names of the dummy arguments in an ENTRY 32statement may differ from the order, number, types, kind type parameters, and names of the dummy 33arguments in the FUNCTION or SUBROUTINE statement in the containing subprogram. 34Because an ENTRY statement defines an additional function or an additional subroutine, it is referenced 35in the same manner as any other function or subroutine (12.4). 36In a subprogram, a name that appears as a dummy argument in an ENTRY statement shall not appear 37in an executable statement preceding that ENTRY statement, unless it also appears in a FUNCTION, 38SUBROUTINE, or ENTRY statement that precedes the executable statement. 283 J3/04-007 WORKING DRAFT MAY 2004 1 In a subprogram, a name that appears as a dummy argument in an ENTRY statement shall not appear in the expression 2 of a statement function unless the name is also a dummy argument of the statement function, appears in a FUNCTION 3 or SUBROUTINE statement, or appears in an ENTRY statement that precedes the statement function statement. 4If a dummy argument appears in an executable statement, the execution of the executable statement is 5permitted during the execution of a reference to the function or subroutine only if the dummy argument 6appears in the dummy argument list of the procedure name referenced. 7If a dummy argument is used in a specification expression to specify an array bound or character length 8of an object, the appearance of the object in a statement that is executed during a procedure reference 9is permitted only if the dummy argument appears in the dummy argument list of the procedure name 10referenced and it is present (12.4.1.6). 11A scoping unit containing a reference to a procedure defined by an ENTRY statement may have access to 12an interface body for the procedure. The procedure header for the interface body shall be a FUNCTION 13statement for an entry in a function subprogram and shall be a SUBROUTINE statement for an entry 14in a subroutine subprogram. 15The keyword RECURSIVE is not used in an ENTRY statement. Instead, the presence or absence of 16RECURSIVE in the initial SUBROUTINE or FUNCTION statement controls whether the procedure 17defined by an ENTRY statement is permitted to reference itself. 18The keyword PURE is not used in an ENTRY statement. Instead, the procedure defined by an ENTRY 19statement is pure if and only if PURE or ELEMENTAL is specified in the SUBROUTINE or FUNCTION 20statement. 21The keyword ELEMENTAL is not used in an ENTRY statement. Instead, the procedure defined by 22an ENTRY statement is elemental if and only if ELEMENTAL is specified in the SUBROUTINE or 23FUNCTION statement. 2412.5.2.5 RETURN statement 25R1236 return-stmt is RETURN [ scalar-int-expr ] 26C1258 (R1236) The return-stmt shall be in the scoping unit of a function or subroutine subprogram. 27C1259 (R1236) The scalar-int-expr is allowed only in the scoping unit of a subroutine subprogram. 28Execution of the RETURN statement completes execution of the instance of the subprogram in which 29it appears. If the expression appears and has a value n between 1 and the number of asterisks in the dummy argument 30 list, the CALL statement that invoked the subroutine transfers control to the statement identified by the nth alternate 31 return specifier in the actual argument list. If the expression is omitted or has a value outside the required range, there is 32 no transfer of control to an alternate return. 33Execution of an end-function-stmt or end-subroutine-stmt is equivalent to executing a RETURN state- 34ment with no expression. 3512.5.2.6 CONTAINS statement 36R1237 contains-stmt is CONTAINS 37The CONTAINS statement separates the body of a main program, module, or subprogram from any 38internal or module subprograms it may contain, or it introduces the type-bound procedure part of a 39derived-type definition (4.5.1). The CONTAINS statement is not executable. 284 MAY 2004 WORKING DRAFT J3/04-007 1 12.5.3 Definition and invocation of procedures by means other than Fortran 2 A procedure may be defined by means other than Fortran. The interface of a procedure defined by 3 means other than Fortran may be specified by an interface body or procedure declaration statement. If 4 the interface of such a procedure does not have a proc-language-binding-spec, the means by which the 5 procedure is defined are processor dependent. A reference to such a procedure is made as though it were 6 defined by an external subprogram. 7 If the interface of a procedure has a proc-language-binding-spec, the procedure is interoperable (15.4). 8 Interoperation with C functions is described in 15.4. NOTE 12.41 For explanatory information on definition of procedures by means other than Fortran, see section C.9.2. 912.5.4 Statement function 10 A statement function is a function defined by a single statement. 11 R1238 stmt-function-stmt is function-name ( [ dummy-arg-name-list ] ) = scalar-expr 12C1260 (R1238) The primaries of the scalar-expr shall be constants (literal and named), references to variables, references 13 to functions and function dummy procedures, and intrinsic operations. If scalar-expr contains a reference to a 14 function or a function dummy procedure, the reference shall not require an explicit interface, the function shall 15 not require an explicit interface unless it is an intrinsic, the function shall not be a transformational intrinsic, 16 and the result shall be scalar. If an argument to a function or a function dummy procedure is an array, it shall 17 be an array name. If a reference to a statement function appears in scalar-expr, its definition shall have been 18 provided earlier in the scoping unit and shall not be the name of the statement function being defined. 19C1261 (R1238) Named constants in scalar-expr shall have been declared earlier in the scoping unit or made accessible 20 by use or host association. If array elements appear in scalar-expr, the array shall have been declared as an array 21 earlier in the scoping unit or made accessible by use or host association. 22C1262 (R1238) If a dummy-arg-name, variable, function reference, or dummy function reference is typed by the implicit 23 typing rules, its appearance in any subsequent type declaration statement shall confirm this implied type and 24 the values of any implied type parameters. 25C1263 (R1238) The function-name and each dummy-arg-name shall be specified, explicitly or implicitly, to be scalar. 26C1264 (R1238) A given dummy-arg-name shall not appear more than once in any dummy-arg-name-list. 27C1265 (R1238) Each variable reference in scalar-expr may be either a reference to a dummy argument of the statement 28 function or a reference to a variable accessible in the same scoping unit as the statement function statement. 29 The definition of a statement function with the same name as an accessible entity from the host shall be preceded by the 30 declaration of its type in a type declaration statement. 31 The dummy arguments have a scope of the statement function statement. Each dummy argument has the same type and 32 type parameters as the entity of the same name in the scoping unit containing the statement function. 33 A statement function shall not be supplied as a procedure argument. 34 The value of a statement function reference is obtained by evaluating the expression using the values of the actual arguments 35 for the values of the corresponding dummy arguments and, if necessary, converting the result to the declared type and 36 type attributes of the function. 285 J3/04-007 WORKING DRAFT MAY 2004 1 A function reference in the scalar expression shall not cause a dummy argument of the statement function to become 2 redefined or undefined. 312.6 Pure procedures 4A pure procedure is 5 (1) A pure intrinsic function (13.1), 6 (2) A pure intrinsic subroutine (13.1), 7 (3) Defined by a pure subprogram, or 8 (4) A statement function that references only pure functions. 9A pure subprogram is a subprogram that has the prefix-spec PURE or ELEMENTAL. The following 10additional constraints apply to pure subprograms. 11C1266 The specification-part of a pure function subprogram shall specify that all its nonpointer dummy 12 data objects have INTENT(IN). 13C1267 The specification-part of a pure subroutine subprogram shall specify the intents of all its non- 14 pointer dummy data objects. 15C1268 A local variable declared in the specification-part or internal-subprogram-part of a pure subpro- 16 gram shall not have the SAVE attribute. NOTE 12.42 Variable initialization in a type-declaration-stmt or a data-stmt implies the SAVE attribute; there- fore, such initialization is also disallowed. 17C1269 The specification-part of a pure subprogram shall specify that all its dummy procedures are 18 pure. 19C1270 If a procedure that is neither an intrinsic procedure nor a statement function is used in a context 20 that requires it to be pure, then its interface shall be explicit in the scope of that use. The 21 interface shall specify that the procedure is pure. 22C1271 All internal subprograms in a pure subprogram shall be pure. 23C1272 In a pure subprogram any designator with a base object that is in common or accessed by 24 host or use association, is a dummy argument of a pure function, is a dummy argument with 25 INTENT (IN) of a pure subroutine, or an object that is storage associated with any such variable, 26 shall not be used in the following contexts: 27 (1) In a variable definition context(16.5.7); 28 (2) As the data-target in a pointer-assignment-stmt; 29 (3) As the expr corresponding to a component with the POINTER attribute in a structure- 30 constructor. 31 (4) As the expr of an intrinsic assignment statement in which the variable is of a derived type 32 if the derived type has a pointer component at any level of component selection; or NOTE 12.43 This requires that processors be able to determine if entities with the PRIVATE attribute or with private components have a pointer component. 33 (5) As an actual argument associated with a dummy argument with INTENT (OUT) or IN- 34 TENT (INOUT) or with the POINTER attribute. 286 MAY 2004 WORKING DRAFT J3/04-007 1C1273 Any procedure referenced in a pure subprogram, including one referenced via a defined operation, 2 assignment, or finalization, shall be pure. 3C1274 A pure subprogram shall not contain a print-stmt, open-stmt, close-stmt, backspace-stmt, endfile- 4 stmt, rewind-stmt, flush-stmt, wait-stmt, or inquire-stmt. 5C1275 A pure subprogram shall not contain a read-stmt or write-stmt whose io-unit is a file-unit- 6 number or *. 7C1276 A pure subprogram shall not contain a stop-stmt. NOTE 12.44 The above constraints are designed to guarantee that a pure procedure is free from side effects (modifications of data visible outside the procedure), which means that it is safe to reference it in constructs such as a FORALL assignment-stmt where there is no explicit order of evaluation. The constraints on pure subprograms may appear complicated, but it is not necessary for a pro- grammer to be intimately familiar with them. From the programmer's point of view, these con- straints can be summarized as follows: a pure subprogram shall not contain any operation that could conceivably result in an assignment or pointer assignment to a common variable, a variable accessed by use or host association, or an INTENT (IN) dummy argument; nor shall a pure sub- program contain any operation that could conceivably perform any external file input/output or STOP operation. Note the use of the word conceivably; it is not sufficient for a pure subprogram merely to be side-effect free in practice. For example, a function that contains an assignment to a global variable but in a block that is not executed in any invocation of the function is nevertheless not a pure function. The exclusion of functions of this nature is required if strict compile-time checking is to be used. It is expected that most library procedures will conform to the constraints required of pure pro- cedures, and so can be declared pure and referenced in FORALL statements and constructs and within user-defined pure procedures. NOTE 12.45 Pure subroutines are included to allow subroutine calls from pure procedures in a safe way, and to allow forall-assignment-stmts to be defined assignments. The constraints for pure subroutines are based on the same principles as for pure functions, except that side effects to INTENT (OUT), INTENT (INOUT), and pointer dummy arguments are permitted. 812.7 Elemental procedures 912.7.1 Elemental procedure declaration and interface 10An elemental procedure is an elemental intrinsic procedure or a procedure that is defined by an 11elemental subprogram. 12An elemental subprogram has the prefix-spec ELEMENTAL. An elemental subprogram is a pure sub- 13program. The PURE prefix-spec need not appear; it is implied by the ELEMENTAL prefix-spec. The 14following additional constraints apply to elemental subprograms. 15C1277 All dummy arguments of an elemental procedure shall be scalar dummy data objects and shall 16 not have the POINTER or ALLOCATABLE attribute. 17C1278 The result variable of an elemental function shall be scalar and shall not have the POINTER or 287 J3/04-007 WORKING DRAFT MAY 2004 1 ALLOCATABLE attribute. 2C1279 In the scoping unit of an elemental subprogram, an object designator with a dummy argument 3 as the base object shall not appear in a specification-expr except as the argument to one of the 4 intrinsic functions BIT SIZE, KIND, LEN, or the numeric inquiry functions (13.5.6). NOTE 12.46 An elemental subprogram is a pure subprogram and all of the constraints for pure subprograms also apply. NOTE 12.47 The restriction on dummy arguments in specification expressions is imposed primarily to facilitate optimization. An example of usage that is not permitted is ELEMENTAL REAL FUNCTION F (A, N) REAL, INTENT (IN) :: A INTEGER, INTENT (IN) :: N REAL :: WORK_ARRAY(N) ! Invalid ... END FUNCTION F An example of usage that is permitted is ELEMENTAL REAL FUNCTION F (A) REAL, INTENT (IN) :: A REAL (SELECTED_REAL_KIND (PRECISION (A)*2)) :: WORK ... END FUNCTION F 512.7.2 Elemental function actual arguments and results 6If a generic name or a specific name is used to reference an elemental function, the shape of the result is 7the same as the shape of the actual argument with the greatest rank. If there are no actual arguments 8or the actual arguments are all scalar, the result is scalar. For those elemental functions that have more 9than one argument, all actual arguments shall be conformable. In the array case, the values of the 10elements, if any, of the result are the same as would have been obtained if the scalar function had been 11applied separately, in any order, to corresponding elements of each array actual argument. NOTE 12.48 An example of an elemental reference to the intrinsic function MAX: if X and Y are arrays of shape (M, N), MAX (X, 0.0, Y) is an array expression of shape (M, N) whose elements have values MAX (X(I, J), 0.0, Y(I, J)), I = 1, 2, ..., M, J = 1,2, ..., N 288 MAY 2004 WORKING DRAFT J3/04-007 112.7.3 Elemental subroutine actual arguments 2An elemental subroutine is one that has only scalar dummy arguments, but may have array actual 3arguments. In a reference to an elemental subroutine, either all actual arguments shall be scalar, or 4all actual arguments associated with INTENT (OUT) and INTENT (INOUT) dummy arguments shall 5be arrays of the same shape and the remaining actual arguments shall be conformable with them. In 6the case that the actual arguments associated with INTENT (OUT) and INTENT (INOUT) dummy 7arguments are arrays, the values of the elements, if any, of the results are the same as would be obtained 8if the subroutine had been applied separately, in any order, to corresponding elements of each array 9actual argument. 10In a reference to the intrinsic subroutine MVBITS, the actual arguments corresponding to the TO and 11FROM dummy arguments may be the same variable and may be associated scalar variables or associated 12array variables all of whose corresponding elements are associated. Apart from this, the actual arguments 13in a reference to an elemental subroutine must satisfy the restrictions of 12.4.1.7. 289 J3/04-007 WORKING DRAFT MAY 2004 290 MAY 2004 WORKING DRAFT J3/04-007 1Section 13: Intrinsic procedures and modules 2There are four classes of intrinsic procedures: inquiry functions, elemental functions, transformational 3functions, and subroutines. Some intrinsic subroutines are elemental. 4There are three sets of standard intrinsic modules: a Fortran environment module (13.8.2), modules to 5support exception handling and IEEE arithmetic, and a module to support interoperability with the C 6programming language. The later two sets of modules are described in sections 14 and 15, respectively. 713.1 Classes of intrinsic procedures 8An inquiry function is one whose result depends on the properties of one or more of its arguments 9instead of their values; in fact, these argument values may be undefined. Unless the description of 10an inquiry function states otherwise, these arguments are permitted to be unallocated allocatables or 11pointers that are not associated. An elemental intrinsic function is one that is specified for scalar 12arguments, but may be applied to array arguments as described in 12.7. All other intrinsic functions 13are transformational functions; they almost all have one or more array arguments or an array result. 14All standard intrinsic functions are pure. 15The subroutine MOVE ALLOC and the elemental subroutine MVBITS are pure. No other standard 16intrinsic subroutine is pure. NOTE 13.1 As with user-written elemental subroutines, an elemental intrinsic subroutine is pure. The effects of MOVE ALLOC are limited to its arguments. The remaining nonelemental intrinsic subroutines all have side effects (or reflect system side effects) and thus are not pure. 17Generic names of standard intrinsic procedures are listed in 13.5. In most cases, generic functions 18accept arguments of more than one type and the type of the result is the same as the type of the 19arguments. Specific names of standard intrinsic functions with corresponding generic names are listed 20in 13.6. 21If an intrinsic procedure is used as an actual argument to a procedure, its specific name shall be used 22and it may be referenced in the called procedure only with scalar arguments. If an intrinsic procedure 23does not have a specific name, it shall not be used as an actual argument (12.4.1.3). 24Elemental intrinsic procedures behave as described in 12.7. 2513.2 Arguments to intrinsic procedures 26All intrinsic procedures may be invoked with either positional arguments or argument keywords (12.4). 27The descriptions in 13.5 through 13.7 give the argument keyword names and positional sequence for 28standard intrinsic procedures. 29Many of the intrinsic procedures have optional arguments. These arguments are identified by the notation 30"optional" in the argument descriptions. In addition, the names of the optional arguments are enclosed 31in square brackets in description headings and in lists of procedures. The valid forms of reference for 32procedures with optional arguments are described in 12.4.1. 291 J3/04-007 WORKING DRAFT MAY 2004 NOTE 13.2 The text CMPLX (X [, Y, KIND]) indicates that Y and KIND are both optional arguments. Valid reference forms include CMPLX(x), CMPLX(x, y), CMPLX(x, KIND=kind), CMPLX(x, y, kind), and CMPLX(KIND=kind, X=x, Y=y). NOTE 13.3 Some intrinsic procedures impose additional requirements on their optional arguments. For exam- ple, SELECTED REAL KIND requires that at least one of its optional arguments be present, and RANDOM SEED requires that at most one of its optional arguments be present. 1The dummy arguments of the specific intrinsic procedures in 13.6 have INTENT(IN). The dummy 2arguments of the generic intrinsic procedures in 13.7 have INTENT(IN) if the intent is not stated 3explicitly. 4The actual argument associated with an intrinsic function dummy argument named KIND shall be a 5scalar integer initialization expression and its value shall specify a representation method for the function 6result that exists on the processor. 7Intrinsic subroutines that assign values to arguments of type character do so in accordance with the 8rules of intrinsic assignment (7.4.1.3). 913.2.1 The shape of array arguments 10Unless otherwise specified, the inquiry intrinsic functions accept array arguments for which the shape 11need not be defined. The shape of array arguments to transformational and elemental intrinsic functions 12shall be defined. 1313.2.2 Mask arguments 14Some array intrinsic functions have an optional MASK argument of type logical that is used by the 15function to select the elements of one or more arguments to be operated on by the function. Any 16element not selected by the mask need not be defined at the time the function is invoked. 17The MASK affects only the value of the function, and does not affect the evaluation, prior to invoking 18the function, of arguments that are array expressions. 1913.3 Bit model 20The bit manipulation procedures are ten elemental functions and one elemental subroutine. Logical 21operations on bits are provided by the elemental functions IOR, IAND, NOT, and IEOR; shift operations 22are provided by the elemental functions ISHFT and ISHFTC; bit subfields may be referenced by the 23elemental function IBITS and by the elemental subroutine MVBITS; single-bit processing is provided 24by the elemental functions BTEST, IBSET, and IBCLR. 25For the purposes of these procedures, a bit is defined to be a binary digit w located at position k of a 26nonnegative integer scalar object based on a model nonnegative integer defined by z-1 j = wk × 2k k=0 27and for which wk may have the value 0 or 1. An example of a model number compatible with the 28examples used in 13.4 would have z = 32, thereby defining a 32-bit integer. 292 MAY 2004 WORKING DRAFT J3/04-007 1An inquiry function BIT SIZE is available to determine the parameter z of the model. 2Effectively, this model defines an integer object to consist of z bits in sequence numbered from right 3to left from 0 to z - 1. This model is valid only in the context of the use of such an object as the 4argument or result of one of the bit manipulation procedures. In all other contexts, the model defined 5for an integer in 13.4 applies. In particular, whereas the models are identical for wz-1 = 0, they do not 6correspond for wz -1 = 1 and the interpretation of bits in such objects is processor dependent. 713.4 Numeric models 8The numeric manipulation and inquiry functions are described in terms of a model for the representation 9and behavior of numbers on a processor. The model has parameters that are determined so as to make 10the model best fit the machine on which the program is executed. 11The model set for integer i is defined by q-1 i = s × wk × rk k=0 12where r is an integer exceeding one, q is a positive integer, each wk is a nonnegative integer less than r, 13and s is +1 or -1. 14The model set for real x is defined by 0 or p x = s × be × fk × b-k , k=1 15where b and p are integers exceeding one; each fk is a nonnegative integer less than b, with f1 nonzero; s 16is +1 or -1; and e is an integer that lies between some integer maximum emax and some integer minimum 17emin inclusively. For x = 0, its exponent e and digits fk are defined to be zero. The integer parameters 18r and q determine the set of model integers and the integer parameters b, p, emin, and emax determine 19the set of model floating point numbers. The parameters of the integer and real models are available 20for each integer and real type implemented by the processor. The parameters characterize the set of 21available numbers in the definition of the model. The floating-point manipulation functions (13.5.10) 22and numeric inquiry functions (13.5.6) provide values of some parameters and other values related to 23the models. NOTE 13.4 Examples of these functions in 13.7 use the models 30 i = s × wk × 2k k=0 and 24 1 x = 0 or s × 2e × + fk × 2-k , - 126 e 127 2 k=2 293 J3/04-007 WORKING DRAFT MAY 2004 113.5 Standard generic intrinsic procedures 2For all of the standard intrinsic procedures, the arguments shown are the names that shall be used for 3argument keywords if the keyword form is used for actual arguments. NOTE 13.5 For example, a reference to CMPLX may be written in the form CMPLX (A, B, M) or in the form CMPLX (Y = B, KIND = M, X = A). NOTE 13.6 Many of the argument keywords have names that are indicative of their usage. For example: KIND Describes the kind type parameter of the result STRING, STRING A An arbitrary character string BACK Controls the direction of string scan (forward or backward) MASK A mask that may be applied to the arguments DIM A selected dimension of an array argument 413.5.1 Numeric functions 5 ABS (A) Absolute value 6 AIMAG (Z) Imaginary part of a complex number 7 AINT (A [, KIND]) Truncation to whole number 8 ANINT (A [, KIND]) Nearest whole number 9 CEILING (A [, KIND]) Least integer greater than or equal to number 10 CMPLX (X [, Y, KIND]) Conversion to complex type 11 CONJG (Z) Conjugate of a complex number 12 DBLE (A) Conversion to double precision real type 13 DIM (X, Y) Positive difference 14 DPROD (X, Y) Double precision real product 15 FLOOR (A [, KIND]) Greatest integer less than or equal to number 16 INT (A [, KIND]) Conversion to integer type 17 MAX (A1, A2 [, A3,...]) Maximum value 18 MIN (A1, A2 [, A3,...]) Minimum value 19 MOD (A, P) Remainder function 20 MODULO (A, P) Modulo function 21 NINT (A [, KIND]) Nearest integer 22 REAL (A [, KIND]) Conversion to real type 23 SIGN (A, B) Transfer of sign 2413.5.2 Mathematical functions 25 ACOS (X) Arccosine 26 ASIN (X) Arcsine 27 ATAN (X) Arctangent 28 ATAN2 (Y, X) Arctangent 29 COS (X) Cosine 30 COSH (X) Hyperbolic cosine 31 EXP (X) Exponential 32 LOG (X) Natural logarithm 33 LOG10 (X) Common logarithm (base 10) 34 SIN (X) Sine 294 MAY 2004 WORKING DRAFT J3/04-007 1 SINH (X) Hyperbolic sine 2 SQRT (X) Square root 3 TAN (X) Tangent 4 TANH (X) Hyperbolic tangent 513.5.3 Character functions 6 ACHAR (I [, KIND]) Character in given position in ASCII collating 7 sequence 8 ADJUSTL (STRING) Adjust left 9 ADJUSTR (STRING) Adjust right 10 CHAR (I [, KIND]) Character in given position in processor collating 11 sequence 12 IACHAR (C [, KIND]) Position of a character in ASCII collating 13 sequence 14 ICHAR (C [, KIND]) Position of a character in processor collating 15 sequence INDEX (STRING, SUBSTRING [, BACK, Starting position of a substring 16 KIND]) 17 LEN TRIM (STRING [, KIND]) Length without trailing blank characters 18 LGE (STRING A, STRING B) Lexically greater than or equal 19 LGT (STRING A, STRING B) Lexically greater than 20 LLE (STRING A, STRING B) Lexically less than or equal 21 LLT (STRING A, STRING B) Lexically less than 22 MAX (A1, A2 [, A3,...]) Maximum value 23 MIN (A1, A2 [, A3,...]) Minimum value 24 REPEAT (STRING, NCOPIES) Repeated concatenation 25 SCAN (STRING, SET [, BACK, KIND]) Scan a string for a character in a set 26 TRIM (STRING) Remove trailing blank characters 27 VERIFY (STRING, SET [, BACK, KIND]) Verify the set of characters in a string 2813.5.4 Kind functions 29 KIND (X) Kind type parameter value 30 SELECTED CHAR KIND (NAME) Character kind type parameter value, given 31 character set name 32 SELECTED INT KIND (R) Integer kind type parameter value, given range 33 SELECTED REAL KIND ([P, R]) Real kind type parameter value, given precision 34 and range 3513.5.5 Miscellaneous type conversion functions 36 LOGICAL (L [, KIND]) Convert between objects of type logical with 37 different kind type parameters 38 TRANSFER (SOURCE, MOLD [, SIZE]) Treat first argument as if of type of second 39 argument 4013.5.6 Numeric inquiry functions 41 DIGITS (X) Number of significant digits of the model 42 EPSILON (X) Number that is almost negligible compared to 43 one 44 HUGE (X) Largest number of the model 45 MAXEXPONENT (X) Maximum exponent of the model 295 J3/04-007 WORKING DRAFT MAY 2004 1 MINEXPONENT (X) Minimum exponent of the model 2 PRECISION (X) Decimal precision 3 RADIX (X) Base of the model 4 RANGE (X) Decimal exponent range 5 TINY (X) Smallest positive number of the model 613.5.7 Array inquiry functions 7 LBOUND (ARRAY [, DIM, KIND]) Lower dimension bounds of an array 8 SHAPE (SOURCE [, KIND]) Shape of an array or scalar 9 SIZE (ARRAY [, DIM, KIND]) Total number of elements in an array 10 UBOUND (ARRAY [, DIM, KIND]) Upper dimension bounds of an array 1113.5.8 Other inquiry functions ALLOCATED (ARRAY) or Allocation status 12 ALLOCATED (SCALAR) 13 ASSOCIATED (POINTER [, TARGET]) Association status inquiry or comparison 14 BIT SIZE (I) Number of bits of the model 15 EXTENDS TYPE OF (A, MOLD) Same dynamic type or an extension 16 LEN (STRING [, KIND]) Length of a character entity 17 NEW LINE (A) Newline character 18 PRESENT (A) Argument presence 19 SAME TYPE AS (A, B) Same dynamic type 2013.5.9 Bit manipulation procedures 21 BTEST (I, POS) Bit testing 22 IAND (I, J) Bitwise AND 23 IBCLR (I, POS) Clear bit 24 IBITS (I, POS, LEN) Bit extraction 25 IBSET (I, POS) Set bit 26 IEOR (I, J) Exclusive OR 27 IOR (I, J) Inclusive OR 28 ISHFT (I, SHIFT) Logical shift 29 ISHFTC (I, SHIFT [, SIZE]) Circular shift MVBITS (FROM, FROMPOS, LEN, TO, Copies bits from one integer to another 30 TOPOS) 31 NOT (I) Bitwise complement 3213.5.10 Floating-point manipulation functions 33 EXPONENT (X) Exponent part of a model number 34 FRACTION (X) Fractional part of a number 35 NEAREST (X, S) Nearest different processor number in given 36 direction 37 RRSPACING (X) Reciprocal of the relative spacing of model 38 numbers near given number 39 SCALE (X, I) Multiply a real by its base to an integer power 40 SET EXPONENT (X, I) Set exponent part of a number 41 SPACING (X) Absolute spacing of model numbers near given 42 number 296 MAY 2004 WORKING DRAFT J3/04-007 113.5.11 Vector and matrix multiply functions DOT PRODUCT (VECTOR A, Dot product of two rank-one arrays 2 VECTOR B) 3 MATMUL (MATRIX A, MATRIX B) Matrix multiplication 413.5.12 Array reduction functions 5 ALL (MASK [, DIM]) True if all values are true 6 ANY (MASK [, DIM]) True if any value is true 7 COUNT (MASK [, DIM, KIND]) Number of true elements in an array MAXVAL (ARRAY, DIM [, MASK]) or Maximum value in an array 8 MAXVAL (ARRAY [, MASK]) MINVAL (ARRAY, DIM [, MASK]) or Minimum value in an array 9 MINVAL (ARRAY [, MASK]) PRODUCT (ARRAY, DIM [, MASK]) or Product of array elements 10 PRODUCT (ARRAY [, MASK]) SUM (ARRAY, DIM [, MASK]) or Sum of array elements 11 SUM (ARRAY [, MASK]) 1213.5.13 Array construction functions 13 CSHIFT (ARRAY, SHIFT [, DIM]) Circular shift EOSHIFT (ARRAY, SHIFT [, BOUNDARY, End-off shift 14 DIM]) 15 MERGE (TSOURCE, FSOURCE, MASK) Merge under mask 16 PACK (ARRAY, MASK [, VECTOR]) Pack an array into an array of rank one under a 17 mask RESHAPE (SOURCE, SHAPE[, PAD, Reshape an array 18 ORDER]) 19 SPREAD (SOURCE, DIM, NCOPIES) Replicates array by adding a dimension 20 TRANSPOSE (MATRIX) Transpose of an array of rank two 21 UNPACK (VECTOR, MASK, FIELD) Unpack an array of rank one into an array under 22 a mask 2313.5.14 Array location functions MAXLOC (ARRAY, DIM [, MASK, KIND]) Location of a maximum value in an array or MAXLOC (ARRAY [, MASK, 24 KIND]) MINLOC (ARRAY, DIM [, MASK, KIND]) Location of a minimum value in an array or MINLOC (ARRAY [, MASK, KIND]) 25 2613.5.15 Null function 27 NULL ([MOLD]) Returns disassociated or unallocated result 2813.5.16 Allocation transfer procedure 29 MOVE ALLOC (FROM, TO) Moves an allocation from one allocatable object 30 to another 3113.5.17 Random number subroutines 32 RANDOM NUMBER (HARVEST) Returns pseudorandom number 297 J3/04-007 WORKING DRAFT MAY 2004 1 RANDOM SEED ([SIZE, PUT, GET]) Initializes or restarts the pseudorandom number 2 generator 313.5.18 System environment procedures 4 COMMAND ARGUMENT COUNT () Number of command arguments 5 CPU TIME (TIME) Obtain processor time DATE AND TIME ([DATE, TIME, ZONE, Obtain date and time 6 VALUES]) GET COMMAND ([COMMAND, Returns entire command 7 LENGTH, STATUS]) GET COMMAND ARGUMENT (NUMBER Returns a command argument 8 [, VALUE, LENGTH, STATUS]) GET ENVIRONMENT VARIABLE (NAME Obtain the value of an environment variable [, VALUE, LENGTH, STATUS, 9 TRIM NAME]) 10 IS IOSTAT END (I) Test for end-of-file value 11 IS IOSTAT EOR (I) Test for end-of-record value SYSTEM CLOCK ([COUNT, Obtain data from the system clock 12 COUNT RATE, COUNT MAX]) 1313.6 Specific names for standard intrinsic functions 14Except for AMAX0, AMIN0, MAX1, and MIN1, the result type of the specific function is the same as the 15result type of the corresponding generic function would be if it were invoked with the same arguments 16as the specific function. Specific Name Generic Name Argument Type ABS ABS default real ACOS ACOS default real AIMAG AIMAG default complex AINT AINT default real ALOG LOG default real ALOG10 LOG10 default real · AMAX0 (...) REAL (MAX (...)) default integer · AMAX1 MAX default real · AMIN0 (...) REAL (MIN (...)) default integer · AMIN1 MIN default real AMOD MOD default real ANINT ANINT default real ASIN ASIN default real ATAN ATAN default real ATAN2 ATAN2 default real CABS ABS default complex CCOS COS default complex CEXP EXP default complex · CHAR CHAR default integer CLOG LOG default complex CONJG CONJG default complex COS COS default real COSH COSH default real CSIN SIN default complex CSQRT SQRT default complex 298 MAY 2004 WORKING DRAFT J3/04-007 Specific Name Generic Name Argument Type DABS ABS double precision real DACOS ACOS double precision real DASIN ASIN double precision real DATAN ATAN double precision real DATAN2 ATAN2 double precision real DCOS COS double precision real DCOSH COSH double precision real DDIM DIM double precision real DEXP EXP double precision real DIM DIM default real DINT AINT double precision real DLOG LOG double precision real DLOG10 LOG10 double precision real · DMAX1 MAX double precision real · DMIN1 MIN double precision real DMOD MOD double precision real DNINT ANINT double precision real DPROD DPROD default real DSIGN SIGN double precision real DSIN SIN double precision real DSINH SINH double precision real DSQRT SQRT double precision real DTAN TAN double precision real DTANH TANH double precision real EXP EXP default real · FLOAT REAL default integer IABS ABS default integer · ICHAR ICHAR default character IDIM DIM default integer · IDINT INT double precision real IDNINT NINT double precision real · IFIX INT default real INDEX INDEX default character · INT INT default real ISIGN SIGN default integer LEN LEN default character · LGE LGE default character · LGT LGT default character · LLE LLE default character · LLT LLT default character · MAX0 MAX default integer · MAX1 (...) INT (MAX (...)) default real · MIN0 MIN default integer · MIN1 (...) INT (MIN (...)) default real MOD MOD default integer NINT NINT default real · REAL REAL default integer SIGN SIGN default real SIN SIN default real SINH SINH default real · SNGL REAL double precision real SQRT SQRT default real 299 J3/04-007 WORKING DRAFT MAY 2004 Specific Name Generic Name Argument Type TAN TAN default real TANH TANH default real 1A specific intrinsic function marked with a bullet (·) shall not be used as an actual argument or as a 2target in a procedure pointer assignment statement. 313.7 Specifications of the standard intrinsic procedures 4Detailed specifications of the standard generic intrinsic procedures are provided here in alphabetical 5order. 6The types and type parameters of standard intrinsic procedure arguments and function results are de- 7termined by these specifications. The "Argument(s)" paragraphs specify requirements on the actual 8arguments of the procedures. The result characteristics are sometimes specified in terms of the charac- 9teristics of dummy arguments. A program is prohibited from invoking an intrinsic procedure under cir- 10cumstances where a value to be returned in a subroutine argument or function result is outside the range 11of values representable by objects of the specified type and type parameters, unless the intrinsic module 12IEEE ARITHMETIC (section 14) is accessible and there is support for an infinite or a NaN result, as 13appropriate. If an infinite result is returned, the flag IEEE OVERFLOW or IEEE DIVIDE BY ZERO 14shall signal; if a NaN result is returned, the flag IEEE INVALID shall signal. If all results are normal, 15these flags shall have the same status as when the intrinsic procedure was invoked. 1613.7.1 ABS (A) 17 Description. Absolute value. 18 Class. Elemental function. 19 Argument. A shall be of type integer, real, or complex. 20 Result Characteristics. The same as A except that if A is complex, the result is real. 21 Result Value. If A is of type integer or real, the value of the result is |A|; if A is complex with 22 value (x,y), the result is equal to a processor-dependent approximation to x2 + y2. 23 Example. ABS ((3.0, 4.0)) has the value 5.0 (approximately). 2413.7.2 ACHAR (I [, KIND]) 25 Description. Returns the character in a specified position of the ASCII collating sequence. It 26 is the inverse of the IACHAR function. 27 Class. Elemental function. 28 Arguments. 29 I shall be of type integer. 30 KIND (optional) shall be a scalar integer initialization expression. 31 Result Characteristics. Character of length one. If KIND is present, the kind type parameter 32 is that specified by the value of KIND; otherwise, the kind type parameter is that of default 33 character type. 300 MAY 2004 WORKING DRAFT J3/04-007 1 Result Value. If I has a value in the range 0 I 127, the result is the character in 2 position I of the ASCII collating sequence, provided the processor is capable of representing 3 that character in the character type of the result; otherwise, the result is processor dependent. 4 ACHAR (IACHAR (C)) shall have the value C for any character C capable of representation in 5 the default character type. 6 Example. ACHAR (88) has the value 'X'. 713.7.3 ACOS (X) 8 Description. Arccosine (inverse cosine) function. 9 Class. Elemental function. 10 Argument. X shall be of type real with a value that satisfies the inequality |X| 1. 11 Result Characteristics. Same as X. 12 Result Value. The result has a value equal to a processor-dependent approximation to arc- 13 cos(X), expressed in radians. It lies in the range 0 ACOS(X) . 14 Example. ACOS (0.54030231) has the value 1.0 (approximately). 1513.7.4 ADJUSTL (STRING) 16 Description. Adjust to the left, removing leading blanks and inserting trailing blanks. 17 Class. Elemental function. 18 Argument. STRING shall be of type character. 19 Result Characteristics. Character of the same length and kind type parameter as STRING. 20 Result Value. The value of the result is the same as STRING except that any leading blanks 21 have been deleted and the same number of trailing blanks have been inserted. 22 Example. ADJUSTL (' WORD') has the value 'WORD '. 2313.7.5 ADJUSTR (STRING) 24 Description. Adjust to the right, removing trailing blanks and inserting leading blanks. 25 Class. Elemental function. 26 Argument. STRING shall be of type character. 27 Result Characteristics. Character of the same length and kind type parameter as STRING. 28 Result Value. The value of the result is the same as STRING except that any trailing blanks 29 have been deleted and the same number of leading blanks have been inserted. 30 Example. ADJUSTR ('WORD ') has the value ' WORD'. 3113.7.6 AIMAG (Z) 32 Description. Imaginary part of a complex number. 33 Class. Elemental function. 301 J3/04-007 WORKING DRAFT MAY 2004 1 Argument. Z shall be of type complex. 2 Result Characteristics. Real with the same kind type parameter as Z. 3 Result Value. If Z has the value (x,y), the result has the value y. 4 Example. AIMAG ((2.0, 3.0)) has the value 3.0. 513.7.7 AINT (A [, KIND]) 6 Description. Truncation to a whole number. 7 Class. Elemental function. 8 Arguments. 9 A shall be of type real. 10 KIND (optional) shall be a scalar integer initialization expression. 11 Result Characteristics. The result is of type real. If KIND is present, the kind type parameter 12 is that specified by the value of KIND; otherwise, the kind type parameter is that of A. 13 Result Value. If |A| < 1, AINT (A) has the value 0; if |A| 1, AINT (A) has a value equal 14 to the integer whose magnitude is the largest integer that does not exceed the magnitude of A 15 and whose sign is the same as the sign of A. 16 Examples. AINT (2.783) has the value 2.0. AINT (­2.783) has the value ­2.0. 1713.7.8 ALL (MASK [, DIM]) 18 Description. Determine whether all values are true in MASK along dimension DIM. 19 Class. Transformational function. 20 Arguments. 21 MASK shall be of type logical. It shall not be scalar. DIM (optional) shall be scalar and of type integer with value in the range 1 DIM n, where n is the rank of MASK. The corresponding actual argument shall not 22 be an optional dummy argument. 23 Result Characteristics. The result is of type logical with the same kind type parameter as 24 MASK. It is scalar if DIM is absent; otherwise, the result has rank n - 1 and shape (d1, d2, 25 ..., dDIM , dDIM+1, ..., dn) where (d1, d2, ..., dn) is the shape of MASK. -1 26 Result Value. 27 Case (i): The result of ALL (MASK) has the value true if all elements of MASK are true 28 or if MASK has size zero, and the result has value false if any element of MASK 29 is false. 30 Case (ii): If MASK has rank one, ALL(MASK,DIM) is equal to ALL(MASK). Otherwise, 31 the value of element (s1, s2, ..., sDIM , sDIM+1, ..., sn) of ALL (MASK, DIM) -1 32 is equal to ALL (MASK (s1, s2, ..., sDIM , :, sDIM+1, ..., sn)). -1 33 Examples. 34 Case (i): The value of ALL ((/ .TRUE., .FALSE., .TRUE. /)) is false. 302 MAY 2004 WORKING DRAFT J3/04-007 1 3 5 0 3 5 Case (ii): If B is the array and C is the array then ALL (B /= C, 1 2 4 6 7 4 8 2 DIM = 1) is [true, false, false] and ALL (B /= C, DIM = 2) is [false, false]. 313.7.9 ALLOCATED (ARRAY) or ALLOCATED (SCALAR) 4 Description. Indicate whether an allocatable variable is allocated. 5 Class. Inquiry function. 6 Arguments. 7 ARRAY shall be an allocatable array. 8 SCALAR shall be an allocatable scalar. 9 Result Characteristics. Default logical scalar. 10 Result Value. The result has the value true if the argument (ARRAY or SCALAR) is allocated 11 and has the value false if the argument is unallocated. 1213.7.10 ANINT (A [, KIND]) 13 Description. Nearest whole number. 14 Class. Elemental function. 15 Arguments. 16 A shall be of type real. 17 KIND (optional) shall be a scalar integer initialization expression. 18 Result Characteristics. The result is of type real. If KIND is present, the kind type parameter 19 is that specified by the value of KIND; otherwise, the kind type parameter is that of A. 20 Result Value. The result is the integer nearest A, or if there are two integers equally near A, 21 the result is whichever such integer has the greater magnitude. 22 Examples. ANINT (2.783) has the value 3.0. ANINT (­2.783) has the value ­3.0. 2313.7.11 ANY (MASK [, DIM]) 24 Description. Determine whether any value is true in MASK along dimension DIM. 25 Class. Transformational function. 26 Arguments. 27 MASK shall be of type logical. It shall not be scalar. DIM (optional) shall be scalar and of type integer with a value in the range 1 DIM n, where n is the rank of MASK. The corresponding actual argument shall not 28 be an optional dummy argument. 29 Result Characteristics. The result is of type logical with the same kind type parameter as 30 MASK. It is scalar if DIM is absent; otherwise, the result has rank n - 1 and shape (d1, d2, 31 ..., dDIM , dDIM+1, ..., dn) where (d1, d2, ..., dn) is the shape of MASK. -1 303 J3/04-007 WORKING DRAFT MAY 2004 1 Result Value. 2 Case (i): The result of ANY (MASK) has the value true if any element of MASK is true 3 and has the value false if no elements are true or if MASK has size zero. 4 Case (ii): If MASK has rank one, ANY(MASK,DIM) is equal to ANY(MASK). Otherwise, 5 the value of element (s1, s2, ..., sDIM , sDIM+1, ..., sn) of ANY(MASK, DIM) -1 6 is equal to ANY(MASK (s1, s2, ..., sDIM , :, sDIM+1, ..., sn)). -1 7 Examples. 8 Case (i): The value of ANY ((/ .TRUE., .FALSE., .TRUE. /)) is true. 1 3 5 0 3 5 Case (ii): If B is the array and C is the array then ANY(B /= C, 9 2 4 6 7 4 8 10 DIM = 1) is [true, false, true] and ANY(B /= C, DIM = 2) is [true, true]. 1113.7.12 ASIN (X) 12 Description. Arcsine (inverse sine) function. 13 Class. Elemental function. 14 Argument. X shall be of type real. Its value shall satisfy the inequality |X| 1. 15 Result Characteristics. Same as X. 16 Result Value. The result has a value equal to a processor-dependent approximation to arc- 17 sin(X), expressed in radians. It lies in the range -/2 ASIN(X) /2. 18 Example. ASIN (0.84147098) has the value 1.0 (approximately). 1913.7.13 ASSOCIATED (POINTER [, TARGET]) 20 Description. Returns the association status of its pointer argument or indicates whether the 21 pointer is associated with the target. 22 Class. Inquiry function. 23 Arguments. POINTER shall be a pointer. It may be of any type or may be a procedure pointer. Its 24 pointer association status shall not be undefined. TARGET shall be allowable as the data-target or proc-target in a pointer assignment (optional) statement (7.4.2) in which POINTER is data-pointer-object or proc-pointer- object. If TARGET is a pointer then its pointer association status shall not 25 be undefined. 26 Result Characteristics. Default logical scalar. 27 Result Value. 28 Case (i): If TARGET is absent, the result is true if POINTER is associated with a target 29 and false if it is not. 30 Case (ii): If TARGET is present and is a procedure, the result is true if POINTER is 31 associated with TARGET. 32 Case (iii): If TARGET is present and is a procedure pointer, the result is true if POINTER 33 and TARGET are associated with the same procedure. If either POINTER or 34 TARGET is disassociated, the result is false. 304 MAY 2004 WORKING DRAFT J3/04-007 1 Case (iv): If TARGET is present and is a scalar target, the result is true if TARGET is not a 2 zero-sized storage sequence and the target associated with POINTER occupies the 3 same storage units as TARGET. Otherwise, the result is false. If the POINTER 4 is disassociated, the result is false. 5 Case (v): If TARGET is present and is an array target, the result is true if the target 6 associated with POINTER and TARGET have the same shape, are neither of 7 size zero nor arrays whose elements are zero-sized storage sequences, and occupy 8 the same storage units in array element order. Otherwise, the result is false. If 9 POINTER is disassociated, the result is false. 10 Case (vi): If TARGET is present and is a scalar pointer, the result is true if the target 11 associated with POINTER and the target associated with TARGET are not zero- 12 sized storage sequences and they occupy the same storage units. Otherwise, the 13 result is false. If either POINTER or TARGET is disassociated, the result is 14 false. 15 Case (vii): If TARGET is present and is an array pointer, the result is true if the target 16 associated with POINTER and the target associated with TARGET have the 17 same shape, are neither of size zero nor arrays whose elements are zero-sized 18 storage sequences, and occupy the same storage units in array element order. 19 Otherwise, the result is false. If either POINTER or TARGET is disassociated, 20 the result is false. 21 Examples. ASSOCIATED (CURRENT, HEAD) is true if CURRENT is associated with the 22 target HEAD. After the execution of 23 A PART => A (:N) 24 ASSOCIATED (A PART, A) is true if N is equal to UBOUND (A, DIM = 1). After the 25 execution of 26 NULLIFY (CUR); NULLIFY (TOP) 27 ASSOCIATED (CUR, TOP) is false. 2813.7.14 ATAN (X) 29 Description. Arctangent (inverse tangent) function. 30 Class. Elemental function. 31 Argument. X shall be of type real. 32 Result Characteristics. Same as X. 33 Result Value. The result has a value equal to a processor-dependent approximation to arc- 34 tan(X), expressed in radians, that lies in the range -/2 ATAN(X) /2. 35 Example. ATAN (1.5574077) has the value 1.0 (approximately). 3613.7.15 ATAN2 (Y, X) 37 Description. Arctangent (inverse tangent) function. The result is the principal value of the 38 argument of the nonzero complex number (X, Y). 39 Class. Elemental function. 40 Arguments. 305 J3/04-007 WORKING DRAFT MAY 2004 1 Y shall be of type real. X shall be of the same type and kind type parameter as Y. If Y has the value 2 zero, X shall not have the value zero. 3 Result Characteristics. Same as X. 4 Result Value. The result has a value equal to a processor-dependent approximation to the 5 principal value of the argument of the complex number (X, Y), expressed in radians. It lies in 6 the range - ATAN2(Y,X) and is equal to a processor-dependent approximation to a 7 value of arctan(Y/X) if X = 0. If Y > 0, the result is positive. If Y = 0 and X > 0, the result 8 is Y. If Y = 0 and X < 0, then the result is if Y is positive real zero or the processor cannot 9 distinguish between positive and negative real zero, and - if Y is negative real zero. If Y < 0, 10 the result is negative. If X = 0, the absolute value of the result is /2. 11 Examples. ATAN2 (1.5574077, 1.0) has the value 1.0 (approximately). If Y has the value 1 1 -1 1 and X has the value , the value of ATAN2 (Y, X) is approximately 12 -1 -1 -1 1 3 4 4 . 13 -3 4 -4 1413.7.16 BIT SIZE (I) 15 Description. Returns the number of bits z defined by the model of 13.3. 16 Class. Inquiry function. 17 Argument. I shall be of type integer. It may be a scalar or an array. 18 Result Characteristics. Scalar integer with the same kind type parameter as I. 19 Result Value. The result has the value of the number of bits z of the model integer defined 20 for bit manipulation contexts in 13.3. 21 Example. BIT SIZE (1) has the value 32 if z of the model is 32. 2213.7.17 BTEST (I, POS) 23 Description. Tests a bit of an integer value. 24 Class. Elemental function. 25 Arguments. 26 I shall be of type integer. 27 POS shall be of type integer. It shall be nonnegative and be less than BIT SIZE (I). 28 Result Characteristics. Default logical. 29 Result Value. The result has the value true if bit POS of I has the value 1 and has the value 30 false if bit POS of I has the value 0. The model for the interpretation of an integer value as a 31 sequence of bits is in 13.3. 1 2 Examples. BTEST (8, 3) has the value true. If A has the value , the value of 32 3 4 306 MAY 2004 WORKING DRAFT J3/04-007 false false true false BTEST (A, 2) is and the value of BTEST (2, A) is . 1 false true false false 213.7.18 CEILING (A [, KIND]) 3 Description. Returns the least integer greater than or equal to its argument. 4 Class. Elemental function. 5 Arguments. 6 A shall be of type real. 7 KIND (optional) shall be a scalar integer initialization expression. 8 Result Characteristics. Integer. If KIND is present, the kind type parameter is that specified 9 by the value of KIND; otherwise, the kind type parameter is that of default integer type. 10 Result Value. The result has a value equal to the least integer greater than or equal to A. 11 Examples. CEILING (3.7) has the value 4. CEILING (­3.7) has the value ­3. 1213.7.19 CHAR (I [, KIND]) 13 Description. Returns the character in a given position of the processor collating sequence 14 associated with the specified kind type parameter. It is the inverse of the ICHAR function. 15 Class. Elemental function. 16 Arguments. I shall be of type integer with a value in the range 0 I n-1, where n is the number of characters in the collating sequence associated with the specified 17 kind type parameter. 18 KIND (optional) shall be a scalar integer initialization expression. 19 Result Characteristics. Character of length one. If KIND is present, the kind type parameter 20 is that specified by the value of KIND; otherwise, the kind type parameter is that of default 21 character type. 22 Result Value. The result is the character in position I of the collating sequence associated 23 with the specified kind type parameter. ICHAR (CHAR (I, KIND (C))) shall have the value I 24 for 0 I n - 1 and CHAR (ICHAR (C), KIND (C)) shall have the value C for any character 25 C capable of representation in the processor. 26 Example. CHAR (88) has the value 'X' on a processor using the ASCII collating sequence. 2713.7.20 CMPLX (X [, Y, KIND]) 28 Description. Convert to complex type. 29 Class. Elemental function. 30 Arguments. 31 X shall be of type integer, real, or complex, or a boz-literal-constant. 307 J3/04-007 WORKING DRAFT MAY 2004 Y (optional) shall be of type integer or real, or a boz-literal-constant. If X is of type complex, Y shall not be present, nor shall Y be associated with an optional 1 dummy argument. 2 KIND (optional) shall be a scalar integer initialization expression. 3 Result Characteristics. The result is of type complex. If KIND is present, the kind type 4 parameter is that specified by the value of KIND; otherwise, the kind type parameter is that of 5 default real type. 6 Result Value. If Y is absent and X is not complex, it is as if Y were present with the value 7 zero. If X is complex, it is as if X were real with the value REAL (X, KIND) and Y were present 8 with the value AIMAG (X, KIND). CMPLX (X, Y, KIND) has the complex value whose real 9 part is REAL (X, KIND) and whose imaginary part is REAL (Y, KIND). 10 Example. CMPLX (­3) has the value (­3.0, 0.0). 1113.7.21 COMMAND ARGUMENT COUNT () 12 Description. Returns the number of command arguments. 13 Class. Inquiry function. 14 Arguments. None. 15 Result Characteristics. Scalar default integer. 16 Result Value. The result value is equal to the number of command arguments available. 17 If there are no command arguments available or if the processor does not support command 18 arguments, then the result value is 0. If the processor has a concept of a command name, the 19 command name does not count as one of the command arguments. 20 Example. See 13.7.42. 2113.7.22 CONJG (Z) 22 Description. Conjugate of a complex number. 23 Class. Elemental function. 24 Argument. Z shall be of type complex. 25 Result Characteristics. Same as Z. 26 Result Value. If Z has the value (x,y), the result has the value (x,-y). 27 Example. CONJG ((2.0, 3.0)) has the value (2.0, ­3.0). 2813.7.23 COS (X) 29 Description. Cosine function. 30 Class. Elemental function. 31 Argument. X shall be of type real or complex. 32 Result Characteristics. Same as X. 33 Result Value. The result has a value equal to a processor-dependent approximation to cos(X). 308 MAY 2004 WORKING DRAFT J3/04-007 1 If X is of type real, it is regarded as a value in radians. If X is of type complex, its real part is 2 regarded as a value in radians. 3 Example. COS (1.0) has the value 0.54030231 (approximately). 413.7.24 COSH (X) 5 Description. Hyperbolic cosine function. 6 Class. Elemental function. 7 Argument. X shall be of type real. 8 Result Characteristics. Same as X. 9 Result Value. The result has a value equal to a processor-dependent approximation to cosh(X). 10 Example. COSH (1.0) has the value 1.5430806 (approximately). 1113.7.25 COUNT (MASK [, DIM, KIND]) 12 Description. Count the number of true elements of MASK along dimension DIM. 13 Class. Transformational function. 14 Arguments. 15 MASK shall be of type logical. It shall not be scalar. DIM (optional) shall be scalar and of type integer with a value in the range 1 DIM n, where n is the rank of MASK. The corresponding actual argument shall not 16 be an optional dummy argument. 17 KIND (optional) shall be a scalar integer initialization expression. 18 Result Characteristics. Integer. If KIND is present, the kind type parameter is that spec- 19 ified by the value of KIND; otherwise the kind type parameter is that of default integer type. 20 The result is scalar if DIM is absent; otherwise, the result has rank n - 1 and shape (d1, d2, 21 ..., dDIM , dDIM+1, ..., dn) where (d1, d2, ..., dn) is the shape of MASK. -1 22 Result Value. 23 Case (i): The result of COUNT (MASK) has a value equal to the number of true elements 24 of MASK or has the value zero if MASK has size zero. 25 Case (ii): If MASK has rank one, COUNT (MASK, DIM) has a value equal to that of 26 COUNT (MASK). Otherwise, the value of element (s1, s2, ..., sDIM , sDIM+1, -1 27 ..., sn) of COUNT (MASK, DIM) is equal to COUNT (MASK (s1, s2, ..., sDIM , -1 28 :, sDIM+1, ..., sn)). 29 Examples. 30 Case (i): The value of COUNT ((/ .TRUE., .FALSE., .TRUE. /)) is 2. 1 3 5 0 3 5 Case (ii): If B is the array and C is the array , COUNT (B /= C, 31 2 4 6 7 4 8 32 DIM = 1) is [2, 0, 1] and COUNT (B /= C, DIM = 2) is [1, 2]. 3313.7.26 CPU TIME (TIME) 34 Description. Returns the processor time. 309 J3/04-007 WORKING DRAFT MAY 2004 1 Class. Subroutine. 2 Argument. TIME shall be scalar and of type real. It is an INTENT(OUT) argument that is 3 assigned a processor-dependent approximation to the processor time in seconds. If the processor 4 cannot return a meaningful time, a processor-dependent negative value is returned. 5 Example. 6 REAL T1, T2 7 ... 8 CALL CPU TIME(T1) 9 ... ! Code to be timed. 10 CALL CPU TIME(T2) 11 WRITE (*,*) 'Time taken by code was ', T2-T1, ' seconds' 12 writes the processor time taken by a piece of code. NOTE 13.7 A processor for which a single result is inadequate (for example, a parallel processor) might choose to provide an additional version for which time is an array. The exact definition of time is left imprecise because of the variability in what different processors are able to provide. The primary purpose is to compare different algorithms on the same processor or discover which parts of a calculation are the most expensive. The start time is left imprecise because the purpose is to time sections of code, as in the example. Most computer systems have multiple concepts of time. One common concept is that of time expended by the processor for a given program. This might or might not include system overhead, and has no obvious connection to elapsed "wall clock" time. 1313.7.27 CSHIFT (ARRAY, SHIFT [, DIM]) 14 Description. Perform a circular shift on an array expression of rank one or perform circular 15 shifts on all the complete rank one sections along a given dimension of an array expression of 16 rank two or greater. Elements shifted out at one end of a section are shifted in at the other end. 17 Different sections may be shifted by different amounts and in different directions. 18 Class. Transformational function. 19 Arguments. 20 ARRAY may be of any type. It shall not be scalar. SHIFT shall be of type integer and shall be scalar if ARRAY has rank one; otherwise, it shall be scalar or of rank n - 1 and of shape (d1, d2, ..., dDIM , dDIM+1, -1 21 ..., dn) where (d1, d2, ..., dn) is the shape of ARRAY. DIM (optional) shall be a scalar and of type integer with a value in the range 1 DIM n, where n is the rank of ARRAY. If DIM is omitted, it is as if it were present 22 with the value 1. 23 Result Characteristics. The result is of the type and type parameters of ARRAY, and has 24 the shape of ARRAY. 310 MAY 2004 WORKING DRAFT J3/04-007 1 Result Value. 2 Case (i): If ARRAY has rank one, element i of the result is ARRAY (1 + MODULO (i + 3 SHIFT ­ 1, SIZE (ARRAY))). 4 Case (ii): If ARRAY has rank greater than one, section (s1, s2, ..., sDIM , :, sDIM+1, ...., -1 5 sn) of the result has a value equal to CSHIFT (ARRAY (s1, s2, ..., sDIM , :, -1 6 sDIM+1, ...., sn), sh, 1), where sh is SHIFT or SHIFT (s1, s2, ..., sDIM , sDIM+1, -1 7 ..., sn). 8 Examples. 9 Case (i): If V is the array [1, 2, 3, 4, 5, 6], the effect of shifting V circularly to the left by 10 two positions is achieved by CSHIFT (V, SHIFT = 2) which has the value [3, 4, 11 5, 6, 1, 2]; CSHIFT (V, SHIFT = ­2) achieves a circular shift to the right by two 12 positions and has the value [5, 6, 1, 2, 3, 4]. 13 Case (ii): The rows of an array of rank two may all be shifted by the same amount or by 1 2 3 different amounts. If M is the array 4 5 6 the value of , 14 7 8 9 3 1 2 CSHIFT (M, SHIFT = ­1, DIM = 2) is 6 4 5 and the value of , 15 9 7 8 3 1 2 CSHIFT (M, SHIFT = (/ ­1, 1, 0 /), DIM = 2) is 5 6 4 . 16 7 8 9 1713.7.28 DATE AND TIME ([DATE, TIME, ZONE, VALUES]) 18 Description. Returns data about the real-time clock and date in a form compatible with the 19 representations defined in ISO 8601:1988. 20 Class. Subroutine. 21 Arguments. DATE (optional) shall be scalar and of type default character. It is an INTENT (OUT) ar- gument. It is assigned a value of the form CCYYMMDD, where CC is the century, YY is the year within the century, MM is the month within the year, and DD is the day within the month. If there is no date available, DATE is 22 assigned all blanks. TIME (optional) shall be scalar and of type default character. It is an INTENT (OUT) argu- ment. It is assigned a value of the form hhmmss.sss, where hh is the hour of the day, mm is the minutes of the hour, and ss.sss is the seconds and milliseconds of the minute. If there is no clock available, TIME is assigned 23 all blanks. ZONE (optional) shall be scalar and of type default character. It is an INTENT (OUT) argu- ment. It is assigned a value of the form +hhmm or -hhmm, where hh and mm are the time difference with respect to Coordinated Universal Time (UTC) in hours and minutes, respectively. If this information is not available, ZONE 24 is assigned all blanks. VALUES shall be of type default integer and of rank one. It is an INTENT (OUT) (optional) argument. Its size shall be at least 8. The values returned in VALUES are 25 as follows: 311 J3/04-007 WORKING DRAFT MAY 2004 VALUES (1) the year, including the century (for example, 1990), or ­HUGE (0) if there is 1 no date available; 2 VALUES (2) the month of the year, or ­HUGE (0) if there is no date available; 3 VALUES (3) the day of the month, or ­HUGE (0) if there is no date available; VALUES (4) the time difference with respect to Coordinated Universal Time (UTC) in 4 minutes, or ­HUGE (0) if this information is not available; 5 VALUES (5) the hour of the day, in the range of 0 to 23, or ­HUGE (0) if there is no clock; VALUES (6) the minutes of the hour, in the range 0 to 59, or ­HUGE (0) if there is no 6 clock; VALUES (7) the seconds of the minute, in the range 0 to 60, or ­HUGE (0) if there is no 7 clock; VALUES (8) the milliseconds of the second, in the range 0 to 999, or ­HUGE (0) if there 8 is no clock. 9 Example. 10 INTEGER DATE_TIME (8) 11 CHARACTER (LEN = 10) BIG_BEN (3) 12 CALL DATE_AND_TIME (BIG_BEN (1), BIG_BEN (2), & 13 BIG_BEN (3), DATE_TIME) 14 If run in Geneva, Switzerland on April 12, 1985 at 15:27:35.5 with a system configured for the 15 local time zone, this sample would have assigned the value 19850412 to BIG BEN (1), the value 16 152735.500 to BIG BEN (2), the value +0100 to BIG BEN (3), and the value (/ 1985, 4, 12, 17 60, 15, 27, 35, 500 /) to DATE TIME. NOTE 13.8 UTC is defined by ISO 8601:1988. 1813.7.29 DBLE (A) 19 Description. Convert to double precision real type. 20 Class. Elemental function. 21 Argument. A shall be of type integer, real, or complex, or a boz-literal-constant. 22 Result Characteristics. Double precision real. 23 Result Value. The result has the value REAL (A, KIND (0.0D0)). 24 Example. DBLE (­3) has the value ­3.0D0. 2513.7.30 DIGITS (X) 26 Description. Returns the number of significant digits of the model representing numbers of 27 the same type and kind type parameter as the argument. 28 Class. Inquiry function. 312 MAY 2004 WORKING DRAFT J3/04-007 1 Argument. X shall be of type integer or real. It may be a scalar or an array. 2 Result Characteristics. Default integer scalar. 3 Result Value. The result has the value q if X is of type integer and p if X is of type real, 4 where q and p are as defined in 13.4 for the model representing numbers of the same type and 5 kind type parameter as X. 6 Example. DIGITS (X) has the value 24 for real X whose model is as in Note 13.4. 713.7.31 DIM (X, Y) 8 Description. The difference X­Y if it is positive; otherwise zero. 9 Class. Elemental function. 10 Arguments. 11 X shall be of type integer or real. 12 Y shall be of the same type and kind type parameter as X. 13 Result Characteristics. Same as X. 14 Result Value. The value of the result is X­Y if X>Y and zero otherwise. 15 Example. DIM (­3.0, 2.0) has the value 0.0. 1613.7.32 DOT PRODUCT (VECTOR A, VECTOR B) 17 Description. Performs dot-product multiplication of numeric or logical vectors. 18 Class. Transformational function. 19 Arguments. VECTOR A shall be of numeric type (integer, real, or complex) or of logical type. It shall 20 be a rank-one array. VECTOR B shall be of numeric type if VECTOR A is of numeric type or of type logical if VECTOR A is of type logical. It shall be a rank-one array. It shall be of 21 the same size as VECTOR A. 22 Result Characteristics. If the arguments are of numeric type, the type and kind type pa- 23 rameter of the result are those of the expression VECTOR A * VECTOR B determined by the 24 types of the arguments according to 7.1.4.2. If the arguments are of type logical, the result is 25 of type logical with the kind type parameter of the expression VECTOR A .AND. VECTOR B 26 according to 7.1.4.2. The result is scalar. 27 Result Value. 28 Case (i): If VECTOR A is of type integer or real, the result has the value SUM (VEC- 29 TOR A*VECTOR B). If the vectors have size zero, the result has the value zero. 30 Case (ii): If VECTOR A is of type complex, the result has the value SUM (CONJG (VEC- 31 TOR A)*VECTOR B). If the vectors have size zero, the result has the value 32 zero. 33 Case (iii): If VECTOR A is of type logical, the result has the value ANY (VECTOR A 34 .AND. VECTOR B). If the vectors have size zero, the result has the value false. 313 J3/04-007 WORKING DRAFT MAY 2004 1 Example. DOT PRODUCT ((/ 1, 2, 3 /), (/ 2, 3, 4 /)) has the value 20. 213.7.33 DPROD (X, Y) 3 Description. Double precision real product. 4 Class. Elemental function. 5 Arguments. 6 X shall be of type default real. 7 Y shall be of type default real. 8 Result Characteristics. Double precision real. 9 Result Value. The result has a value equal to a processor-dependent approximation to the 10 product of X and Y. 11 Example. DPROD (­3.0, 2.0) has the value ­6.0D0. 1213.7.34 EOSHIFT (ARRAY, SHIFT [, BOUNDARY, DIM]) 13 Description. Perform an end-off shift on an array expression of rank one or perform end-off 14 shifts on all the complete rank-one sections along a given dimension of an array expression of 15 rank two or greater. Elements are shifted off at one end of a section and copies of a boundary 16 value are shifted in at the other end. Different sections may have different boundary values and 17 may be shifted by different amounts and in different directions. 18 Class. Transformational function. 19 Arguments. 20 ARRAY may be of any type. It shall not be scalar. SHIFT shall be of type integer and shall be scalar if ARRAY has rank one; otherwise, it shall be scalar or of rank n - 1 and of shape (d1, d2, ..., dDIM , dDIM+1, -1 21 ..., dn) where (d1, d2, ..., dn) is the shape of ARRAY. BOUNDARY shall be of the same type and type parameters as ARRAY and shall be scalar (optional) if ARRAY has rank one; otherwise, it shall be either scalar or of rank n - 1 and of shape (d1, d2, ..., dDIM , dDIM+1, ..., dn). BOUNDARY may be -1 omitted for the types in the following table and, in this case, it is as if it were present with the scalar value shown. Type of ARRAY Value of BOUNDARY Integer 0 Real 0.0 Complex (0.0, 0.0) Logical false 22 Character (len) len blanks DIM (optional) shall be scalar and of type integer with a value in the range 1 DIM n, where n is the rank of ARRAY. If DIM is omitted, it is as if it were present 23 with the value 1. 24 Result Characteristics. The result has the type, type parameters, and shape of ARRAY. 314 MAY 2004 WORKING DRAFT J3/04-007 1 Result Value. Element (s1, s2, ..., sn) of the result has the value ARRAY (s1, s2, ..., sDIM , -1 2 sDIM + sh, sDIM+1, ..., sn) where sh is SHIFT or SHIFT (s1, s2, ..., sDIM , sDIM+1, ..., sn) -1 3 provided the inequality LBOUND (ARRAY, DIM) sDIM + sh UBOUND (ARRAY, DIM) 4 holds and is otherwise BOUNDARY or BOUNDARY (s1, s2, ..., sDIM , sDIM+1, ..., sn). -1 5 Examples. 6 Case (i): If V is the array [1, 2, 3, 4, 5, 6], the effect of shifting V end-off to the left by 3 7 positions is achieved by EOSHIFT (V, SHIFT = 3), which has the value [4, 5, 8 6, 0, 0, 0]; EOSHIFT (V, SHIFT = ­2, BOUNDARY = 99) achieves an end-off 9 shift to the right by 2 positions with the boundary value of 99 and has the value 10 [99, 99, 1, 2, 3, 4]. 11 Case (ii): The rows of an array of rank two may all be shifted by the same amount or by 12 different amounts and the boundary elements can be the same or different. If M is A B C the array D E F then the value of EOSHIFT (M, SHIFT = ­1, BOUND- , 13 G H I * A B ARY = '*', DIM = 2) is * D E and the value of EOSHIFT (M, SHIFT = , 14 G H * A B (/ ­1, 1, 0 /), BOUNDARY = (/ '*', '/', '?' /), DIM = 2) is E F / . 15 G H I 1613.7.35 EPSILON (X) 17 Description. Returns a positive model number that is almost negligible compared to unity of 18 the model representing numbers of the same type and kind type parameter as the argument. 19 Class. Inquiry function. 20 Argument. X shall be of type real. It may be a scalar or an array. 21 Result Characteristics. Scalar of the same type and kind type parameter as X. -p 22 Result Value. The result has the value b1 where b and p are as defined in 13.4 for the model 23 representing numbers of the same type and kind type parameter as X. 24 Example. EPSILON (X) has the value 2-23 for real X whose model is as in Note 13.4. 2513.7.36 EXP (X) 26 Description. Exponential. 27 Class. Elemental function. 28 Argument. X shall be of type real or complex. 29 Result Characteristics. Same as X. 30 Result Value. The result has a value equal to a processor-dependent approximation to eX. If 31 X is of type complex, its imaginary part is regarded as a value in radians. 32 Example. EXP (1.0) has the value 2.7182818 (approximately). 3313.7.37 EXPONENT (X) 315 J3/04-007 WORKING DRAFT MAY 2004 1 Description. Returns the exponent part of the argument when represented as a model number. 2 Class. Elemental function. 3 Argument. X shall be of type real. 4 Result Characteristics. Default integer. 5 Result Value. The result has a value equal to the exponent e of the model representation 6 (13.4) for the value of X, provided X is nonzero and e is within the range for default integers. If 7 X has the value zero, the result has the value zero. If X is an IEEE infinity or NaN, the result 8 has the value HUGE(0). 9 Examples. EXPONENT (1.0) has the value 1 and EXPONENT (4.1) has the value 3 for 10 reals whose model is as in Note 13.4. 1113.7.38 EXTENDS TYPE OF (A, MOLD) 12 Description. Inquires whether the dynamic type of A is an extension type (4.5.6) of the 13 dynamic type of MOLD. 14 Class. Inquiry function. 15 Arguments. A shall be an object of extensible type. If it is a pointer, it shall not have an 16 undefined association status. MOLD shall be an object of extensible type. If it is a pointer, it shall not have an 17 undefined association status. 18 Result Characteristics. Default logical scalar. 19 Result Value. If MOLD is unlimited polymorphic and is either a disassociated pointer or 20 unallocated allocatable, the result is true; otherwise if A is unlimited polymorphic and is either 21 a disassociated pointer or unallocated allocatable, the result is false; otherwise the result is true 22 if and only if the dynamic type of A is an extension type of the dynamic type of MOLD. NOTE 13.9 The dynamic type of a disassociated pointer or unallocated allocatable is its declared type. 2313.7.39 FLOOR (A [, KIND]) 24 Description. Returns the greatest integer less than or equal to its argument. 25 Class. Elemental function. 26 Arguments. 27 A shall be of type real. 28 KIND (optional) shall be a scalar integer initialization expression. 29 Result Characteristics. Integer. If KIND is present, the kind type parameter is that specified 30 by the value of KIND; otherwise, the kind type parameter is that of default integer type. 31 Result Value. The result has a value equal to the greatest integer less than or equal to A. 316 MAY 2004 WORKING DRAFT J3/04-007 1 Examples. FLOOR (3.7) has the value 3. FLOOR (­3.7) has the value ­4. 213.7.40 FRACTION (X) 3 Description. Returns the fractional part of the model representation of the argument value. 4 Class. Elemental function. 5 Argument. X shall be of type real. 6 Result Characteristics. Same as X. 7 Result Value. The result has the value X × b-e, where b and e are as defined in 13.4 for the 8 model representation of X. If X has the value zero, the result has the value zero. If X is an IEEE 9 infinity, the result is that infinity. If X is an IEEE NaN, the result is that NaN. 10 Example. FRACTION (3.0) has the value 0.75 for reals whose model is as in Note 13.4. 1113.7.41 GET COMMAND ([COMMAND, LENGTH, STATUS]) 12 Description. Returns the entire command by which the program was invoked. 13 Class. Subroutine. 14 Arguments. COMMAND shall be scalar and of type default character. It is an INTENT(OUT) argu- (optional) ment. It is assigned the entire command by which the program was invoked. 15 If the command cannot be determined, COMMAND is assigned all blanks. LENGTH shall be scalar and of type default integer. It is an INTENT(OUT) argument. (optional) It is assigned the significant length of the command by which the program was invoked. The significant length may include trailing blanks if the pro- cessor allows commands with significant trailing blanks. This length does not consider any possible truncation or padding in assigning the command to the COMMAND argument; in fact the COMMAND argument need not even be present. If the command length cannot be determined, a length of 0 16 is assigned. STATUS shall be scalar and of type default integer. It is an INTENT(OUT) argument. (optional) It is assigned the value -1 if the COMMAND argument is present and has a length less than the significant length of the command. It is assigned a processor-dependent positive value if the command retrieval fails. Otherwise 17 it is assigned the value 0. 13.7.42 GET COMMAND ARGUMENT (NUMBER [, VALUE, LENGTH, STA- 18 TUS]) 19 Description. Returns a command argument. 20 Class. Subroutine. 21 Arguments. 22 NUMBER shall be scalar and of type default integer. It is an INTENT(IN) argument. 317 J3/04-007 WORKING DRAFT MAY 2004 It specifies the number of the command argument that the other arguments give information about. Useful values of NUMBER are those between 0 and the argument count returned by the COMMAND ARGUMENT COUNT intrinsic. Other values are allowed, but will result in error status return (see 1 below). Command argument 0 is defined to be the command name by which the program was invoked if the processor has such a concept. It is allowed to call the GET COMMAND ARGUMENT procedure for command argument number 0, even if the processor does not define command names or other 2 command arguments. The remaining command arguments are numbered consecutively from 1 to 3 the argument count in an order determined by the processor. VALUE shall be scalar and of type default character. It is an INTENT(OUT) ar- (optional) gument. It is assigned the value of the command argument specified by NUMBER. If the command argument value cannot be determined, VALUE 4 is assigned all blanks. LENGTH shall be scalar and of type default integer. It is an INTENT(OUT) argument. (optional) It is assigned the significant length of the command argument specified by NUMBER. The significant length may include trailing blanks if the processor allows command arguments with significant trailing blanks. This length does not consider any possible truncation or padding in assigning the command argument value to the VALUE argument; in fact the VALUE argument need not even be present. If the command argument length cannot be determined, 5 a length of 0 is assigned. STATUS shall be scalar and of type default integer. It is an INTENT(OUT) argument. (optional) It is assigned the value -1 if the VALUE argument is present and has a length less than the significant length of the command argument specified by NUMBER. It is assigned a processor-dependent positive value if the argument 6 retrieval fails. Otherwise it is assigned the value 0. NOTE 13.10 One possible reason for failure is that NUMBER is negative or greater than COMMAND ARGU- MENT COUNT(). 7 Example. 8 Program echo 9 integer :: i 10 character :: command*32, arg*128 11 call get_command_argument(0, command) 12 write (*,*) "Command name is: ", command 13 do i = 1 , command_argument_count() 14 call get_command_argument(i, arg) 15 write (*,*) "Argument ", i, " is ", arg 16 end do 17 end program echo 318 MAY 2004 WORKING DRAFT J3/04-007 13.7.43 GET ENVIRONMENT VARIABLE (NAME [, VALUE, LENGTH, STA- 1 TUS, TRIM NAME]) 2 Description. Gets the value of an environment variable. 3 Class. Subroutine. 4 Arguments. NAME shall be a scalar and of type default character. It is an INTENT(IN) argu- 5 ment. The interpretation of case is processor dependent VALUE shall be a scalar of type default character. It is an INTENT(OUT) argu- (optional) ment. It is assigned the value of the environment variable specified by NAME. VALUE is assigned all blanks if the environment variable does not exist or does not have a value or if the processor does not support environment vari- 6 ables. LENGTH shall be a scalar of type default integer. It is an INTENT(OUT) argument. (optional) If the specified environment variable exists and has a value, LENGTH is set 7 to the length of that value. Otherwise LENGTH is set to 0. STATUS shall be scalar and of type default integer. It is an INTENT(OUT) argument. (optional) If the environment variable exists and either has no value or its value is successfully assigned to VALUE, STATUS is set to zero. STATUS is set to -1 if the VALUE argument is present and has a length less than the significant length of the environment variable. It is assigned the value 1 if the specified environment variable does not exist, or 2 if the processor does not support environment variables. Processor-dependent values greater than 2 may be 8 returned for other error conditions. TRIM NAME shall be a scalar of type logical. It is an INTENT(IN) argument. If (optional) TRIM NAME is present with the value false then trailing blanks in NAME are considered significant if the processor supports trailing blanks in environ- ment variable names. Otherwise trailing blanks in NAME are not considered 9 part of the environment variable's name. 1013.7.44 HUGE (X) 11 Description. Returns the largest number of the model representing numbers of the same type 12 and kind type parameter as the argument. 13 Class. Inquiry function. 14 Argument. X shall be of type integer or real. It may be a scalar or an array. 15 Result Characteristics. Scalar of the same type and kind type parameter as X. 16 Result Value. The result has the value rq -1 if X is of type integer and (1-b-p)bemax if X is 17 of type real, where r, q, b, p, and emax are as defined in 13.4 for the model representing numbers 18 of the same type and kind type parameter as X. 19 Example. HUGE (X) has the value (1 - 2-24) × 2127 for real X whose model is as in Note 20 13.4. 2113.7.45 IACHAR (C [, KIND]) 22 Description. Returns the position of a character in the ASCII collating sequence. This is the 319 J3/04-007 WORKING DRAFT MAY 2004 1 inverse of the ACHAR function. 2 Class. Elemental function. 3 Arguments. 4 C shall be of type character and of length one. 5 KIND (optional) shall be a scalar integer initialization expression. 6 Result Characteristics. Integer. If KIND is present, the kind type parameter is that specified 7 by the value of KIND; otherwise, the kind type parameter is that of default integer type. 8 Result Value. If C is in the collating sequence defined by the codes specified in ISO/IEC 9 646:1991 (International Reference Version), the result is the position of C in that sequence and 10 satisfies the inequality (0 IACHAR(C) 127). A processor-dependent value is returned if C 11 is not in the ASCII collating sequence. The results are consistent with the LGE, LGT, LLE, 12 and LLT lexical comparison functions. For example, if LLE (C, D) is true, IACHAR (C) <= 13 IACHAR (D) is true where C and D are any two characters representable by the processor. 14 Example. IACHAR ('X') has the value 88. 1513.7.46 IAND (I, J) 16 Description. Performs a bitwise AND. 17 Class. Elemental function. 18 Arguments. 19 I shall be of type integer. 20 J shall be of type integer with the same kind type parameter as I. 21 Result Characteristics. Same as I. 22 Result Value. The result has the value obtained by combining I and J bit-by-bit according to 23 the following truth table: I J IAND (I, J) 1 1 1 1 0 0 0 1 0 0 0 0 24 The model for the interpretation of an integer value as a sequence of bits is in 13.3. 25 Example. IAND (1, 3) has the value 1. 2613.7.47 IBCLR (I, POS) 27 Description. Clears one bit to zero. 28 Class. Elemental function. 29 Arguments. 30 I shall be of type integer. 320 MAY 2004 WORKING DRAFT J3/04-007 1 POS shall be of type integer. It shall be nonnegative and less than BIT SIZE (I). 2 Result Characteristics. Same as I. 3 Result Value. The result has the value of the sequence of bits of I, except that bit POS is 4 zero. The model for the interpretation of an integer value as a sequence of bits is in 13.3. 5 Examples. IBCLR (14, 1) has the result 12. If V has the value [1, 2, 3, 4], the value of 6 IBCLR (POS = V, I = 31) is [29, 27, 23, 15]. 713.7.48 IBITS (I, POS, LEN) 8 Description. Extracts a sequence of bits. 9 Class. Elemental function. 10 Arguments. 11 I shall be of type integer. POS shall be of type integer. It shall be nonnegative and POS + LEN shall be 12 less than or equal to BIT SIZE (I). 13 LEN shall be of type integer and nonnegative. 14 Result Characteristics. Same as I. 15 Result Value. The result has the value of the sequence of LEN bits in I beginning at bit POS, 16 right-adjusted and with all other bits zero. The model for the interpretation of an integer value 17 as a sequence of bits is in 13.3. 18 Example. IBITS (14, 1, 3) has the value 7. 1913.7.49 IBSET (I, POS) 20 Description. Sets one bit to one. 21 Class. Elemental function. 22 Arguments. 23 I shall be of type integer. 24 POS shall be of type integer. It shall be nonnegative and less than BIT SIZE (I). 25 Result Characteristics. Same as I. 26 Result Value. The result has the value of the sequence of bits of I, except that bit POS is one. 27 The model for the interpretation of an integer value as a sequence of bits is in 13.3. 28 Examples. IBSET (12, 1) has the value 14. If V has the value [1, 2, 3, 4], the value of 29 IBSET (POS = V, I = 0) is [2, 4, 8, 16]. 3013.7.50 ICHAR (C [, KIND]) 31 Description. Returns the position of a character in the processor collating sequence associated 32 with the kind type parameter of the character. This is the inverse of the CHAR function. 33 Class. Elemental function. 321 J3/04-007 WORKING DRAFT MAY 2004 1 Arguments. C shall be of type character and of length one. Its value shall be that of a 2 character capable of representation in the processor. 3 KIND (optional) shall be a scalar integer initialization expression. 4 Result Characteristics. Integer. If KIND is present, the kind type parameter is that specified 5 by the value of KIND; otherwise, the kind type parameter is that of default integer type. 6 Result Value. The result is the position of C in the processor collating sequence associated 7 with the kind type parameter of C and is in the range 0 ICHAR(C) n - 1, where n is 8 the number of characters in the collating sequence. For any characters C and D capable of 9 representation in the processor, C <= D is true if and only if ICHAR (C) <= ICHAR (D) is true 10 and C == D is true if and only if ICHAR (C) == ICHAR (D) is true. 11 Example. ICHAR ('X') has the value 88 on a processor using the ASCII collating sequence 12 for the default character type. 1313.7.51 IEOR (I, J) 14 Description. Performs a bitwise exclusive OR. 15 Class. Elemental function. 16 Arguments. 17 I shall be of type integer. 18 J shall be of type integer with the same kind type parameter as I. 19 Result Characteristics. Same as I. 20 Result Value. The result has the value obtained by combining I and J bit-by-bit according to 21 the following truth table: I J IEOR (I, J) 1 1 0 1 0 1 0 1 1 0 0 0 22 The model for the interpretation of an integer value as a sequence of bits is in 13.3. 23 Example. IEOR (1, 3) has the value 2. 2413.7.52 INDEX (STRING, SUBSTRING [, BACK, KIND]) 25 Description. Returns the starting position of a substring within a string. 26 Class. Elemental function. 27 Arguments. 28 STRING shall be of type character. 29 SUBSTRING shall be of type character with the same kind type parameter as STRING. 322 MAY 2004 WORKING DRAFT J3/04-007 1 BACK (optional) shall be of type logical. 2 KIND (optional) shall be a scalar integer initialization expression. 3 Result Characteristics. Integer. If KIND is present, the kind type parameter is that specified 4 by the value of KIND; otherwise the kind type parameter is that of default integer type. 5 Result Value. 6 Case (i): If BACK is absent or has the value false, the result is the minimum positive value 7 of I such that STRING (I : I + LEN (SUBSTRING) ­ 1) = SUBSTRING or zero if 8 there is no such value. Zero is returned if LEN (STRING) < LEN (SUBSTRING) 9 and one is returned if LEN (SUBSTRING) = 0. 10 Case (ii): If BACK is present with the value true, the result is the maximum value of 11 I less than or equal to LEN (STRING) ­ LEN (SUBSTRING) + 1 such that 12 STRING (I : I + LEN (SUBSTRING) ­ 1) = SUBSTRING or zero if there is 13 no such value. Zero is returned if LEN (STRING) < LEN (SUBSTRING) and 14 LEN (STRING) + 1 is returned if LEN (SUBSTRING) = 0. 15 Examples. INDEX ('FORTRAN', 'R') has the value 3. 16 INDEX ('FORTRAN', 'R', BACK = .TRUE.) has the value 5. 1713.7.53 INT (A [, KIND]) 18 Description. Convert to integer type. 19 Class. Elemental function. 20 Arguments. 21 A shall be of type integer, real, or complex, or a boz-literal-constant. 22 KIND (optional) shall be a scalar integer initialization expression. 23 Result Characteristics. Integer. If KIND is present, the kind type parameter is that specified 24 by the value of KIND; otherwise, the kind type parameter is that of default integer type. 25 Result Value. 26 Case (i): If A is of type integer, INT (A) = A. 27 Case (ii): If A is of type real, there are two cases: if |A| < 1, INT (A) has the value 0; if 28 |A| 1, INT (A) is the integer whose magnitude is the largest integer that does 29 not exceed the magnitude of A and whose sign is the same as the sign of A. 30 Case (iii): If A is of type complex, INT(A) = INT(REAL(A, KIND(A))). 31 Case (iv): If A is a boz-literal-constant, it is treated as if it were an int-literal-constant with 32 a kind-param that specifies the representation method with the largest decimal 33 exponent range supported by the processor. 34 Example. INT (­3.7) has the value ­3. 3513.7.54 IOR (I, J) 36 Description. Performs a bitwise inclusive OR. 37 Class. Elemental function. 38 Arguments. 323 J3/04-007 WORKING DRAFT MAY 2004 1 I shall be of type integer. 2 J shall be of type integer with the same kind type parameter as I. 3 Result Characteristics. Same as I. 4 Result Value. The result has the value obtained by combining I and J bit-by-bit according to 5 the following truth table: I J IOR (I, J) 1 1 1 1 0 1 0 1 1 0 0 0 6 The model for the interpretation of an integer value as a sequence of bits is in 13.3. 7 Example. IOR (5, 3) has the value 7. 813.7.55 ISHFT (I, SHIFT) 9 Description. Performs a logical shift. 10 Class. Elemental function. 11 Arguments. 12 I shall be of type integer. SHIFT shall be of type integer. The absolute value of SHIFT shall be less than or 13 equal to BIT SIZE (I). 14 Result Characteristics. Same as I. 15 Result Value. The result has the value obtained by shifting the bits of I by SHIFT positions. 16 If SHIFT is positive, the shift is to the left; if SHIFT is negative, the shift is to the right; 17 and if SHIFT is zero, no shift is performed. Bits shifted out from the left or from the right, as 18 appropriate, are lost. Zeros are shifted in from the opposite end. The model for the interpretation 19 of an integer value as a sequence of bits is in 13.3. 20 Example. ISHFT (3, 1) has the result 6. 2113.7.56 ISHFTC (I, SHIFT [, SIZE]) 22 Description. Performs a circular shift of the rightmost bits. 23 Class. Elemental function. 24 Arguments. 25 I shall be of type integer. SHIFT shall be of type integer. The absolute value of SHIFT shall be less than or 26 equal to SIZE. SIZE (optional) shall be of type integer. The value of SIZE shall be positive and shall not exceed BIT SIZE (I). If SIZE is absent, it is as if it were present with the 27 value of BIT SIZE (I). 324 MAY 2004 WORKING DRAFT J3/04-007 1 Result Characteristics. Same as I. 2 Result Value. The result has the value obtained by shifting the SIZE rightmost bits of I 3 circularly by SHIFT positions. If SHIFT is positive, the shift is to the left; if SHIFT is negative, 4 the shift is to the right; and if SHIFT is zero, no shift is performed. No bits are lost. The 5 unshifted bits are unaltered. The model for the interpretation of an integer value as a sequence 6 of bits is in 13.3. 7 Example. ISHFTC (3, 2, 3) has the value 5. 813.7.57 IS IOSTAT END (I) 9 Description. Determine whether a value indicates an end-of-file condition. 10 Class. Elemental function. 11 Argument. I shall be of type integer. 12 Result Characteristics. Default logical. 13 Result Value. The result has the value true if and only if I is a value for the scalar-int-variable 14 in an IOSTAT= specifier (9.10.4) that would indicate an end-of-file condition. 1513.7.58 IS IOSTAT EOR (I) 16 Description. Determine whether a value indicates an end-of-record condition. 17 Class. Elemental function. 18 Argument. I shall be of type integer. 19 Result Characteristics. Default logical. 20 Result Value. The result has the value true if and only if I is a value for the scalar-int-variable 21 in an IOSTAT= specifier (9.10.4) that would indicate an end-of-record condition. 2213.7.59 KIND (X) 23 Description. Returns the value of the kind type parameter of X. 24 Class. Inquiry function. 25 Argument. X may be of any intrinsic type. It may be a scalar or an array. 26 Result Characteristics. Default integer scalar. 27 Result Value. The result has a value equal to the kind type parameter value of X. 28 Example. KIND (0.0) has the kind type parameter value of default real. 2913.7.60 LBOUND (ARRAY [, DIM, KIND]) 30 Description. Returns all the lower bounds or a specified lower bound of an array. 31 Class. Inquiry function. 32 Arguments. ARRAY may be of any type. It shall not be scalar. It shall not be an unallocated 33 allocatable or a pointer that is not associated. 325 J3/04-007 WORKING DRAFT MAY 2004 DIM (optional) shall be scalar and of type integer with a value in the range 1 DIM n, where n is the rank of ARRAY. The corresponding actual argument shall not 1 be an optional dummy argument. 2 KIND (optional) shall be a scalar integer initialization expression. 3 Result Characteristics. Integer. If KIND is present, the kind type parameter is that specified 4 by the value of KIND; otherwise the kind type parameter is that of default integer type. The 5 result is scalar if DIM is present; otherwise, the result is an array of rank one and size n, where 6 n is the rank of ARRAY. 7 Result Value. 8 Case (i): If ARRAY is a whole array or array structure component and either ARRAY is an 9 assumed-size array of rank DIM or dimension DIM of ARRAY has nonzero extent, 10 LBOUND (ARRAY, DIM) has a value equal to the lower bound for subscript DIM 11 of ARRAY. Otherwise the result value is 1. 12 Case (ii): LBOUND (ARRAY) has a value whose ith component is equal to LBOUND (AR- 13 RAY, i), for i = 1, 2,..., n, where n is the rank of ARRAY. 14 Examples. If A is declared by the statement 15 REAL A (2:3, 7:10) 16 then LBOUND (A) is [2, 7] and LBOUND (A, DIM=2) is 7. 1713.7.61 LEN (STRING [, KIND]) 18 Description. Returns the length of a character entity. 19 Class. Inquiry function. 20 Arguments. STRING shall be of type character. It may be a scalar or an array. If it is an unallocated allocatable or a pointer that is not associated, its length type parameter shall 21 not be deferred. 22 KIND (optional) shall be a scalar integer initialization expression. 23 Result Characteristics. Integer scalar. If KIND is present, the kind type parameter is that 24 specified by the value of KIND; otherwise the kind type parameter is that of default integer 25 type. 26 Result Value. The result has a value equal to the number of characters in STRING if it is 27 scalar or in an element of STRING if it is an array. 28 Example. If C is declared by the statement 29 CHARACTER (11) C (100) 30 LEN (C) has the value 11. 3113.7.62 LEN TRIM (STRING [, KIND]) 32 Description. Returns the length of the character argument without counting trailing blank 33 characters. 34 Class. Elemental function. 326 MAY 2004 WORKING DRAFT J3/04-007 1 Arguments. 2 STRING shall be of type character. 3 KIND (optional) shall be a scalar integer initialization expression. 4 Result Characteristics. Integer. If KIND is present, the kind type parameter is that specified 5 by the value of KIND; otherwise the kind type parameter is that of default integer type. 6 Result Value. The result has a value equal to the number of characters remaining after any 7 trailing blanks in STRING are removed. If the argument contains no nonblank characters, the 8 result is zero. 9 Examples. LEN TRIM (' A B ') has the value 4 and LEN TRIM (' ') has the value 0. 1013.7.63 LGE (STRING A, STRING B) 11 Description. Test whether a string is lexically greater than or equal to another string, based 12 on the ASCII collating sequence. 13 Class. Elemental function. 14 Arguments. 15 STRING A shall be of type default character. 16 STRING B shall be of type default character. 17 Result Characteristics. Default logical. 18 Result Value. If the strings are of unequal length, the comparison is made as if the shorter 19 string were extended on the right with blanks to the length of the longer string. If either string 20 contains a character not in the ASCII character set, the result is processor dependent. The 21 result is true if the strings are equal or if STRING A follows STRING B in the ASCII collating 22 sequence; otherwise, the result is false. NOTE 13.11 The result is true if both STRING A and STRING B are of zero length. 23 Example. LGE ('ONE', 'TWO') has the value false. 2413.7.64 LGT (STRING A, STRING B) 25 Description. Test whether a string is lexically greater than another string, based on the ASCII 26 collating sequence. 27 Class. Elemental function. 28 Arguments. 29 STRING A shall be of type default character. 30 STRING B shall be of type default character. 31 Result Characteristics. Default logical. 32 Result Value. If the strings are of unequal length, the comparison is made as if the shorter 33 string were extended on the right with blanks to the length of the longer string. If either string 327 J3/04-007 WORKING DRAFT MAY 2004 1 contains a character not in the ASCII character set, the result is processor dependent. The 2 result is true if STRING A follows STRING B in the ASCII collating sequence; otherwise, the 3 result is false. NOTE 13.12 The result is false if both STRING A and STRING B are of zero length. 4 Example. LGT ('ONE', 'TWO') has the value false. 513.7.65 LLE (STRING A, STRING B) 6 Description. Test whether a string is lexically less than or equal to another string, based on 7 the ASCII collating sequence. 8 Class. Elemental function. 9 Arguments. 10 STRING A shall be of type default character. 11 STRING B shall be of type default character. 12 Result Characteristics. Default logical. 13 Result Value. If the strings are of unequal length, the comparison is made as if the shorter 14 string were extended on the right with blanks to the length of the longer string. If either 15 string contains a character not in the ASCII character set, the result is processor dependent. 16 The result is true if the strings are equal or if STRING A precedes STRING B in the ASCII 17 collating sequence; otherwise, the result is false. NOTE 13.13 The result is true if both STRING A and STRING B are of zero length. 18 Example. LLE ('ONE', 'TWO') has the value true. 1913.7.66 LLT (STRING A, STRING B) 20 Description. Test whether a string is lexically less than another string, based on the ASCII 21 collating sequence. 22 Class. Elemental function. 23 Arguments. 24 STRING A shall be of type default character. 25 STRING B shall be of type default character. 26 Result Characteristics. Default logical. 27 Result Value. If the strings are of unequal length, the comparison is made as if the shorter 28 string were extended on the right with blanks to the length of the longer string. If either string 29 contains a character not in the ASCII character set, the result is processor dependent. The 30 result is true if STRING A precedes STRING B in the ASCII collating sequence; otherwise, the 31 result is false. 328 MAY 2004 WORKING DRAFT J3/04-007 NOTE 13.14 The result is false if both STRING A and STRING B are of zero length. 1 Example. LLT ('ONE', 'TWO') has the value true. 213.7.67 LOG (X) 3 Description. Natural logarithm. 4 Class. Elemental function. 5 Argument. X shall be of type real or complex. If X is real, its value shall be greater than 6 zero. If X is complex, its value shall not be zero. 7 Result Characteristics. Same as X. 8 Result Value. The result has a value equal to a processor-dependent approximation to logeX. 9 A result of type complex is the principal value with imaginary part in the range - . 10 If the real part of X is less than zero and the imaginary part of X is zero, then the imaginary 11 part of the result is if the imaginary part of X is positive real zero or the processor cannot 12 distinguish between positive and negative real zero, and - if the imaginary part of X is negative 13 real zero. 14 Example. LOG (10.0) has the value 2.3025851 (approximately). 1513.7.68 LOG10 (X) 16 Description. Common logarithm. 17 Class. Elemental function. 18 Argument. X shall be of type real. The value of X shall be greater than zero. 19 Result Characteristics. Same as X. 20 Result Value. The result has a value equal to a processor-dependent approximation to log10X. 21 Example. LOG10 (10.0) has the value 1.0 (approximately). 2213.7.69 LOGICAL (L [, KIND]) 23 Description. Converts between kinds of logical. 24 Class. Elemental function. 25 Arguments. 26 L shall be of type logical. 27 KIND (optional) shall be a scalar integer initialization expression. 28 Result Characteristics. Logical. If KIND is present, the kind type parameter is that specified 29 by the value of KIND; otherwise, the kind type parameter is that of default logical. 30 Result Value. The value is that of L. 31 Example. LOGICAL (L .OR. .NOT. L) has the value true and is of type default logical, 329 J3/04-007 WORKING DRAFT MAY 2004 1 regardless of the kind type parameter of the logical variable L. 213.7.70 MATMUL (MATRIX A, MATRIX B) 3 Description. Performs matrix multiplication of numeric or logical matrices. 4 Class. Transformational function. 5 Arguments. MATRIX A shall be of numeric type (integer, real, or complex) or of logical type. It shall 6 be an array of rank one or two. MATRIX B shall be of numeric type if MATRIX A is of numeric type and of logical type if MATRIX A is of logical type. It shall be an array of rank one or two. If MATRIX A has rank one, MATRIX B shall have rank two. If MATRIX B has rank one, MATRIX A shall have rank two. The size of the first (or only) dimension of MATRIX B shall equal the size of the last (or only) dimension 7 of MATRIX A. 8 Result Characteristics. If the arguments are of numeric type, the type and kind type pa- 9 rameter of the result are determined by the types of the arguments as specified in 7.1.4.2 for 10 the * operator. If the arguments are of type logical, the result is of type logical with the kind 11 type parameter of the arguments as specified in 7.1.4.2 for the .AND. operator. The shape of 12 the result depends on the shapes of the arguments as follows: 13 Case (i): If MATRIX A has shape (n,m) and MATRIX B has shape (m,k), the result has 14 shape (n,k). 15 Case (ii): If MATRIX A has shape (m) and MATRIX B has shape (m,k), the result has 16 shape (k). 17 Case (iii): If MATRIX A has shape (n,m) and MATRIX B has shape (m), the result has 18 shape (n). 19 Result Value. 20 Case (i): Element (i,j) of the result has the value SUM (MATRIX A (i, :) * MATRIX B (:, 21 j)) if the arguments are of numeric type and has the value ANY (MATRIX A (i, 22 :) .AND. MATRIX B (:, j)) if the arguments are of logical type. 23 Case (ii): Element (j) of the result has the value SUM (MATRIX A (:) * MATRIX B (:, 24 j)) if the arguments are of numeric type and has the value ANY (MATRIX A (:) 25 .AND. MATRIX B (:, j)) if the arguments are of logical type. 26 Case (iii): Element (i) of the result has the value SUM (MATRIX A (i, :) * MATRIX B (:)) 27 if the arguments are of numeric type and has the value ANY (MATRIX A (i, :) 28 .AND. MATRIX B (:)) if the arguments are of logical type. 1 2 1 2 3 Examples. Let A and B be the matrices and 2 3 let X and Y be the ; 2 3 4 29 3 4 30 vectors [1, 2] and [1, 2, 3]. 31 Case (i): The result of MATMUL (A, B) is the matrix-matrix product AB with the value 14 20 . 32 20 29 33 Case (ii): The result of MATMUL (X, A) is the vector-matrix product XA with the value 34 [5, 8, 11]. 330 MAY 2004 WORKING DRAFT J3/04-007 1 Case (iii): The result of MATMUL (A, Y) is the matrix-vector product AY with the value 2 [14, 20]. 313.7.71 MAX (A1, A2 [, A3, ...]) 4 Description. Maximum value. 5 Class. Elemental function. 6 Arguments. The arguments shall all have the same type which shall be integer, real, or 7 character and they shall all have the same kind type parameter. 8 Result Characteristics. The type and kind type parameter of the result are the same as those 9 of the arguments. For arguments of character type, the length of the result is the length of the 10 longest argument. 11 Result Value. The value of the result is that of the largest argument. For arguments of 12 character type, the result is the value that would be selected by application of intrinsic relational 13 operators; that is, the collating sequence for characters with the kind type parameter of the 14 arguments is applied. If the selected argument is shorter than the longest argument, the result 15 is extended with blanks on the right to the length of the longest argument. 16 Examples. MAX (­9.0, 7.0, 2.0) has the value 7.0, MAX ("Z", "BB") has the value "Z ", and 17 MAX ((/"A", "Z"/), (/"BB", "Y "/)) has the value (/"BB", "Z "/). 1813.7.72 MAXEXPONENT (X) 19 Description. Returns the maximum exponent of the model representing numbers of the same 20 type and kind type parameter as the argument. 21 Class. Inquiry function. 22 Argument. X shall be of type real. It may be a scalar or an array. 23 Result Characteristics. Default integer scalar. 24 Result Value. The result has the value emax, as defined in 13.4 for the model representing 25 numbers of the same type and kind type parameter as X. 26 Example. MAXEXPONENT (X) has the value 127 for real X whose model is as in Note 13.4. 13.7.73 MAXLOC (ARRAY, DIM [, MASK, KIND]) or 27 MAXLOC (ARRAY [, MASK, KIND]) 28 Description. Determine the location of the first element of ARRAY along dimension DIM 29 having the maximum value of the elements identified by MASK. 30 Class. Transformational function. 31 Arguments. 32 ARRAY shall be of type integer, real, or character. It shall not be scalar.