PC File: 94-006-2.edt Archive: 94-006r2.edits -------------------------------------------------------------------------------- xvi 1 00000a 36 a Minor edits and corrections for Technical Corrigendum #1 xvi 1 00000a 36 b WG5 approved; ready for SC22 xvi 1 00000a 36 c 1. Introduction, Overview, Data Concepts, last sentence [xvi:1-2]; xvi 1 00000a 37 c Delete the sentence "The section concludes ... names." 2 4 000135 1710 a INTENT(IN) conformance 2 4 000135 1710 b X3J3 consideration in progress 2 4 000135 1710 c 1. Section 1.4 second paragraph, first sentence [2:4] 2 4 000135 1711 c change 'uses' 2 4 000135 1712 c to 'contains' 2 39 000135 1714 a INTENT(IN) conformance 2 39 000135 1714 b X3J3 consideration in progress 2 39 000135 1714 c 2. Section 1.4 sixth paragraph, first sentence [2:39] 2 39 000135 1715 c change 'use' 2 39 000135 1716 c to 'contain' 2 42 000146 2592 a Conformance 2 42 000146 2592 b X3J3 consideration in progress 2 42 000146 2592 c 1. In section 1.4, change the paragraph beginning "Note that" so that 2 42 000146 2593 c added data types are described in a manner parallel to added intrinsic 2 42 000146 2594 c procedures in the prior paragraph. [2:42] 2 42 000146 2595 c 2 42 000146 2596 c change "a nonstandard data type" 2 42 000146 2597 c to "additional intrinsic data types" 3 32 000061 2243 a G edit descriptor with "d" = 0 3 32 000061 2243 b WG5 approved; ready for SC22 3 32 000061 2243 c 3. In section 1.4.1, add item (5) as follows: [3:32] 3 32 000061 2244 c 3 32 000061 2245 c (5) A value of 0 for a list item in a formatted output statement 3 32 000061 2246 c will be formatted in a different form for some G edit 3 32 000061 2247 c descriptors. In addition, the Fortran 90 standard specifies how 3 32 000061 2248 c rounding of values will affect the output field form, but 3 32 000061 2249 c FORTRAN 77 did not address this issue: therefore, some 3 32 000061 2250 c FORTRAN 77 processors may produce a different output form than 3 32 000061 2251 c Fortran 90 processors for certain combinations of values and G 3 32 000061 2252 c edit descriptors. 3 32 000139 1996 a INTRINSIC, EXTERNAL attribute questions 3 32 000139 1996 b X3J3 consideration in progress 3 32 000139 1996 c 4. Section 1.4.1 [3:32+] 3 32 000139 1997 c 3 32 000139 1998 c Add (6) 'FORTRAN 77 permitted the specification of a type for an 3 32 000139 1999 c intrinsic function even when there was no function defined 3 32 000139 2000 c for that type. For example: 3 32 000139 2001 c INTRINSIC SIN 3 32 000139 2002 c LOGICAL SIN 3 32 000139 2003 c This International Standard specifies (5.1) that a type 3 32 000139 2004 c declaration for an intrinsic function may only confirm the type 3 32 000139 2005 c of an existing function. Thus a standard-conforming FORTRAN 77 3 32 000139 2006 c program specifying a type that is not defined for an intrinsic 3 32 000139 2007 c function does not conform to this International Standard. 5 9 000058 1216 a Ambiguous use of "keyword" 5 9 000058 1216 b X3J3 approved; ready for WG5 5 9 000058 1216 c 1. Page 5, section 1.5.3, (3) [5:9] 5 9 000058 1217 c delete "keyword actual arguments and" 5 9 000058 1218 c rationale: these are not specifiers and -spec is not used with them. 8 8 000101 116 a Specification statements 8 8 000101 116 b X3J3 consideration in progress 8 8 000101 116 c 1. Section 2.1, R207 [8:8] change 'specification-stmt' to 'declaration-stmt' 8 29 000101 118 a Specification statements 8 29 000101 118 b X3J3 consideration in progress 8 29 000101 118 c 2. Section 2.1, R214 [8:29] change 'specification-stmt' to 'declaration-stmt' 11 13 000101 120 a Specification statements 11 13 000101 120 b X3J3 consideration in progress 11 13 000101 120 c 3. Section 2.3.1, following 2nd paragraph [11:13+] insert new paragraph: 11 13 000101 121 c 11 13 000101 122 c Specification statements are all the statements that can appear in 11 13 000101 123 c the , except for the ENTRY and FORMAT statements. 11 13 000101 124 c 11 13 000101 125 c note to editor: "Specification statements", above, should be in bold. 11 30 000101 127 a Specification statements 11 30 000101 127 b X3J3 consideration in progress 11 30 000101 127 c 4. Figure 2.1, [11:30] change 'Specification' to 'Declaration' 12 31 000101 129 a Specification statements 12 31 000101 129 b X3J3 consideration in progress 12 31 000101 129 c 5. In note to Figure 2.1, [12:31] change 'Specification' to 'Declaration' 15 25 00000a 39 a Minor edits and corrections for Technical Corrigendum #1 15 25 00000a 39 b WG5 approved; ready for SC22 15 25 00000a 39 c 2. 2.4.6, third sentence [15:25]; Change "of" to "or". 16 3 000058 1220 a Ambiguous use of "keyword" 16 3 000058 1220 b X3J3 approved; ready for WG5 16 3 000058 1220 c 2. Page 16, section 2.5.2, first paragraph, first occurrence [16:3] 16 3 000058 1221 c change "statement keyword" 16 3 000058 1222 c --------- ------- 16 3 000058 1223 c to "statement keyword (often abbreviated to keyword)" 16 3 000058 1224 c --------- ------- ------- 16 3 000058 1225 c rationale: define "keyword", in a style similar to "object" 16 3 000058 1226 c in 2.4.3.1. 16 5 000004 216 a Blanks in format specifications in free form source 16 5 000004 216 b Returned by WG5 for X3J3 reconsideration 16 5 000004 216 c 1. Section 2.5.2 following the sentence "Keywords appear ... through 12." 16 5 000004 217 c [16:5] add the following: 16 5 000004 218 c 16 5 000004 219 c "Note that in addition to keywords, upper-case letters may also appear in 16 5 000004 220 c various other lexical tokens. Examples include operators such as .EQ., 16 5 000004 221 c edit descriptors such as BN or Iw[.m], and literal constants such as B' 16 5 000004 222 c digit[digit]...'." 16 5 000004 223 c 16 5 000004 224 c Note that the first edit depends on a change made in item 58 which moves 16 5 000004 225 c a line from section 3.2.1 to 2.5.2 16 5 000058 1228 a Ambiguous use of "keyword" 16 5 000058 1228 b X3J3 approved; ready for WG5 16 5 000058 1228 c 3. Page 16, section 2.5.2, first paragraph, end of [16:5] 16 5 000058 1229 c add "Keywords appear as upper-case words in the syntax rules 16 5 000058 1230 c in Sections 4 through 12". 16 6 000058 1232 a Ambiguous use of "keyword" 16 6 000058 1232 b X3J3 approved; ready for WG5 16 6 000058 1232 c 4. Page 16, section 2.5.2, second paragraph, first sentence [16:6] 16 6 000058 1233 c change "name." to "name (see 12.4.1)." 16 35 000146 2599 a Conformance 16 35 000146 2599 b X3J3 consideration in progress 16 35 000146 2599 c 2. In section 2.5.7 [16:35-36] 16 35 000146 2600 c 16 35 000146 2601 c change "International Standard" 16 35 000146 2602 c to "International Standard or by the processor" 19 35 000004 227 a Blanks in format specifications in free form source 19 35 000004 227 b Returned by WG5 for X3J3 reconsideration 19 35 000004 227 c 2. Section 3.2 last sentence [19:35-36] 19 35 000004 228 c following "... , labels" 19 35 000004 229 c insert ", edit descriptors" 19 35 000058 1235 a Ambiguous use of "keyword" 19 35 000058 1235 b X3J3 approved; ready for WG5 19 35 000058 1235 c 5. Page 19, section 3.2 [19:35] 19 35 000058 1236 c change "keywords" to "statement keywords (2.5.2)" 19 37 000058 1238 a Ambiguous use of "keyword" 19 37 000058 1238 b X3J3 approved; ready for WG5 19 37 000058 1238 c 6. Page 19, section 3.2.1 [19:37-38] 19 37 000058 1239 c delete 19 37 000058 1240 c rationale: 2.5.2 is now the complete definition. 21 33 000130 1362 a Multiple statements on line with END statement 21 33 000130 1362 b X3J3 approved; ready for WG5 21 33 000130 1362 c Replace the first sentence of 3.3 [21:33] with: 21 33 000130 1363 c 21 33 000130 1364 c A Fortran program unit is a sequence of one or more lines, 21 33 000130 1365 c organized as Fortran statements, comments, and INCLUDE lines. 22 6 000004 231 a Blanks in format specifications in free form source 22 6 000004 231 b Returned by WG5 for X3J3 reconsideration 22 6 000004 231 c 3. Section 3.3.1, second paragraph [22:6], 22 6 000004 232 c change "... character context." 22 6 000004 233 c to "... character context or in a format specification." 22 44 000121 809 a ";" As a Statement Separator 22 44 000121 809 b X3J3 consideration in progress 22 44 000121 809 c 1. Section 3.3.1.2 [22:44-45], change the first sentence to read as follows: 22 44 000121 810 c 22 44 000121 811 c "The character ``;'' terminates a statement, except when the ``;'' appears 22 44 000121 812 c in a character context or in a comment. This optional termination allows 22 44 000121 813 c another statement to begin following the ``;'' on the same line. A ``;'' 22 44 000121 814 c must not appear as the first nonblank character on a line." 23 1 000121 816 a ";" As a Statement Separator 23 1 000121 816 b X3J3 consideration in progress 23 1 000121 816 c 2. Section 3.3.1.2 [23:1-2], eliminate the last sentence of this section (it 23 1 000121 817 c becomes redundant with edit 1). 23 36 000121 819 a ";" As a Statement Separator 23 36 000121 819 b X3J3 consideration in progress 23 36 000121 819 c 3. Section 3.3.2.2 [23:36-37], change the first sentence to read as follows: 23 36 000121 820 c 23 36 000121 821 c "The character ``;'' terminates a statement, except when the ``;'' appears 23 36 000121 822 c in a character context or in a comment. This optional termination allows 23 36 000121 823 c another statement to begin following the ``;'' on the same line. A ``;'' 23 36 000121 824 c must not appear as the first nonblank character on a line." 23 39 000121 826 a ";" As a Statement Separator 23 39 000121 826 b X3J3 consideration in progress 23 39 000121 826 c 4. Section 3.3.2.2 [23:39-40], eliminate the last sentence of this section (it 23 39 000121 827 c becomes redundant with edit 3). 24 13 000044 1585 a END statement and fixed form source 24 13 000044 1585 b WG5 approved; ready for SC22 24 13 000044 1585 c In 3.3.2.4 replace the text 24 13 000044 1586 c 24 13 000044 1587 c "and no other statement in the program unit may have an initial line that 24 13 000044 1588 c appears to be a program unit END statement" 24 13 000044 1589 c with 24 13 000044 1590 c ". A statement whose initial line appears to be a program unit END 24 13 000044 1591 c statement must not be continued." [24:13] 27 2 00000c 59 a Minor edits and corrections 27 2 00000c 59 b X3J3 approved; ready for WG5 27 2 00000c 59 c 7. In 4.3.1 Numeric Types 27 2 00000c 60 c 27 2 00000c 61 c delete the last sentence "In this standard..." [27:2-3] 27 2 00000c 62 c 27 2 00000c 63 c Rationale: this is a not quite accurate restatement of R306 in section 3.2.3. 27 2 00000c 64 c ("unsigned" is not defined for boz numeric constants) 33 12 000146 2604 a Conformance 33 12 000146 2604 b X3J3 consideration in progress 33 12 000146 2604 c 3. In section 4.4.1, change the fifth constraint following R424 to: [33:12-13] 33 12 000146 2605 c 33 12 000146 2606 c Constraint: A derived type must not be the same as the name 33 12 000146 2607 c of any intrinsic type defined in this standard nor the 33 12 000146 2608 c same as any other accessible derived type . 33 36 000015 487 a Error in fourth constraint for R429 33 36 000015 487 b WG5 approved; ready for SC22 33 36 000015 487 c Replace the fourth constraint after R429 [33:36] with: 33 36 000015 488 c 33 36 000015 489 c The character length specified by the in a 33 36 000015 490 c or the in a 33 36 000015 491 c (5.1, 5.1.1.5) must be a constant specification expression (7.1.6.2). 34 10 000138 1919 a PRIVATE accessibility of a MODULE PROCEDURE 34 10 000138 1919 b X3J3 consideration in progress 34 10 000138 1919 c 1. In 4.4.1 "Derived Type Definition", fourth paragraph following the five 34 10 000138 1920 c constraints following R429 34 10 000138 1921 c 34 10 000138 1922 c change ", and any procedure" 34 10 000138 1923 c to ", any generic identifier for that module procedure, 34 10 000138 1924 c and any procedure" [34:10] 38 3 000030 762 a Length of character literals in array constructors 38 3 000030 762 b X3J3 approved; ready for WG5 38 3 000030 762 c 1. Delete the second constraint following R435. [38:3] 38 4 000030 764 a Length of character literals in array constructors 38 4 000030 764 b X3J3 approved; ready for WG5 38 4 000030 764 c 2. Add the following paragraph after the constraints in 4.5. [38:4] 38 4 000030 765 c 38 4 000030 766 c Each ac-value {in italics} expression in the 38 4 000030 767 c array-constructor {in italics} must have the same type and type parameters. 39 36 000066 2497 a Declaration of FUNCTION type 39 36 000066 2497 b WG5 approved; ready for SC22 39 36 000066 2497 c 1. Change R504 "{()}" to "". 39 36 000066 2498 c [39:36] 40 12 000066 2500 a Declaration of FUNCTION type 40 12 000066 2500 b WG5 approved; ready for SC22 40 12 000066 2500 c 2. Change "Constraint: An for a that 40 12 000066 2501 c does not have the POINTER attribute must be an 40 12 000066 2502 c " 40 12 000066 2503 c to "Constraint: An for an that 40 12 000066 2504 c is a function result that does not have the POINTER attribute 40 12 000066 2505 c must be an ". [40:12] 40 14 000066 2507 a Declaration of FUNCTION type 40 14 000066 2507 b WG5 approved; ready for SC22 40 14 000066 2507 c 3. Delete the constraint "An for a that 40 14 000066 2508 c does have the POINTER attribute must be a ". [40:14] 40 24 000087 2177 a PARAMETER statements and SAVE statements 40 24 000087 2177 b X3J3 approved; ready for WG5 40 24 000087 2177 c 1. Change the sixteenth constraint of section 5.1 to [40:24] 40 24 000087 2178 c 40 24 000087 2179 c The SAVE attribute must not be specified for an object that is in a common 40 24 000087 2180 c block, a dummy argument, a procedure, a function result, an automatic data 40 24 000087 2181 c object, or an object with the PARAMETER attribute. 40 35 000139 1986 a INTRINSIC, EXTERNAL attribute questions 40 35 000139 1986 b X3J3 consideration in progress 40 35 000139 1986 c 3. Section 5.1, second paragraph following the constraints [40:35-36] 40 35 000139 1987 c 40 35 000139 1988 c Replace 'An explicit type declaration statement is not required; 40 35 000139 1989 c however it is permitted. Specifying a type for a generic 40 35 000139 1990 c intrinsic function name in a ...' 40 35 000139 1991 c 40 35 000139 1992 c with 'An explicit type declaration statement confirming that type 40 35 000139 1993 c for either a specific or generic name is not required; however 40 35 000139 1994 c it is permitted. Such a ...' 40 38 000093 2625 a Scalar pointer function results 40 38 000093 2625 b X3J3 approved; ready for WG5 40 38 000093 2625 c 2. Insert the following paragraph after the second paragraph following 40 38 000093 2626 c the constraints in 5.1 [40:38+] 40 38 000093 2627 c 40 38 000093 2628 c A function result may be declared to have the pointer attribute. 40 39 000145 2536 a Expressions in of a FUNCTION statement 40 39 000145 2536 b X3J3 consideration in progress 40 39 000145 2536 c Section 5.1, in the first sentence of the paragraph that starts 40 39 000145 2537 c "The (7.1.6.2)" [40:39-41], 40 39 000145 2538 c 40 39 000145 2539 c replace "in an interface body (12.3.2.1) or in the specification part of a 40 39 000145 2540 c subprogram" 40 39 000145 2541 c 40 39 000145 2542 c with "contained in an interface body (12.3.2.1), is contained in the 40 39 000145 2543 c specification part of a subprogram, or is in the of a 40 39 000145 2544 c FUNCTION statement (12.5.2.2)" 41 8 000113 600 a Ordering of array specification and initialization 41 8 000113 600 b X3J3 approved; ready for WG5 41 8 000113 600 c Section 5.1, add the following to the end of the fifth paragraph 41 8 000113 601 c following the constraints [41:8]: 41 8 000113 602 c 41 8 000113 603 c "If the variable is an array, it must have its shape specified either in 41 8 000113 604 c the type declaration statement or a previous attribute specification 41 8 000113 605 c statement in the same scoping unit." 41 9 000087 2183 a PARAMETER statements and SAVE statements 41 9 000087 2183 b X3J3 approved; ready for WG5 41 9 000087 2183 c 2. In section 5.1, change the first sentence of the next to last 41 9 000087 2184 c paragraph before the examples [41:9]: 41 9 000087 2185 c 41 9 000087 2186 c The presence of = implies that is a 41 9 000087 2187 c saved object, except for an in a named common block or an 41 9 000087 2188 c with the PARAMETER attribute. 42 29 000016 516 a Character length specification 42 29 000016 516 b WG5 approved; ready for SC22 42 29 000016 516 c Replace the text following the constraints for R508 [42:29] with: 42 29 000016 517 c 42 29 000016 518 c The in a CHARACTER and the * 42 29 000016 519 c in an or in a of a type definition 42 29 000016 520 c specify character length. The * in an or 42 29 000016 521 c a specifies an individual length and overrides the 42 29 000016 522 c length specified in the , if any. If a * 42 29 000016 523 c is not specified in an or a , the 42 29 000016 524 c or specified in the 42 29 000016 525 c is the character length. If the length is not 42 29 000016 526 c specified in a or a * , the length is 1. 43 5 000070 1368 a Characteristics specified by interface bodies 43 5 000070 1368 b X3J3 consideration in progress 43 5 000070 1368 c In section 5.1.1.5 item (3), add to the end [43:5]: 43 5 000070 1369 c 43 5 000070 1370 c "Note that the interface for such a function cannot be specified in an 43 5 000070 1371 c interface body." 43 6 000172 1408 a Length specified for a character-valued statement function 43 6 000172 1408 b X3J3 approved; ready for WG5 43 6 000172 1408 c In 5.1.1.5 [43:6-7] change the paragraph following item (3) to: 43 6 000172 1409 c 43 6 000172 1410 c The length specified for a character-valued statement function 43 6 000172 1411 c or statement function dummy argument of type character must be a 43 6 000172 1412 c constant specification expression. 43 22 000032 1239 a Implicit declaration of a derived type 43 22 000032 1239 b WG5 approved; ready for SC22 43 22 000032 1239 c 1. In the first paragraph of 5.1.1.7, 43 22 000032 1240 c change "is specified" 43 22 000032 1241 c to "is declared explicitly". [43:22] 43 23 000112 545 a Sequence derived type external functions 43 23 000112 545 b X3J3 approved; ready for WG5 43 23 000112 545 c Add after the last sentence of the first paragraph of 5.1.1.7: [43:23] 43 23 000112 546 c 43 23 000112 547 c "If the data entity is a function result, the derived type can be specified 43 23 000112 548 c on the FUNCTION statement providing the derived type is defined within the 43 23 000112 549 c body of the function or is accessible there by use or host association." 46 30 000108 424 a Referencing disassociated pointers 46 30 000108 424 b X3J3 approved; ready for WG5 46 30 000108 424 c 1. Replace the first two lines of the seventh paragraph of 5.1.2.4.3, 46 30 000108 425 c "The size, bounds, and shape of the target ... association status." 46 30 000108 426 c [46:30-33] with: 46 30 000108 427 c 46 30 000108 428 c "The size, bounds, and shape of the target of a disassociated array 46 30 000108 429 c pointer are undefined. No part of such an array may be referenced 46 30 000108 430 c or defined; however, the array may appear as an argument to an 46 30 000108 431 c intrinsic inquiry function that is inquiring about argument presence, 46 30 000108 432 c a property of the type or type parameters, or association status." 46 41 000039 954 a Association of a pointer actual argument with a dummy argument 46 41 000039 954 b X3J3 approved; ready for WG5 46 41 000039 954 c 1. Delete the penultimate (tenth) paragraph of 5.1.2.4.3, "A pointer 46 41 000039 955 c dummy argument ... argument." [46:41-42] 46 43 000093 2623 a Scalar pointer function results 46 43 000093 2623 b X3J3 approved; ready for WG5 46 43 000093 2623 c 1. Delete the last paragraph of 5.1.2.4.3 [46:43]. 47 39 000087 2190 a PARAMETER statements and SAVE statements 47 39 000087 2190 b X3J3 approved; ready for WG5 47 39 000087 2190 c 3. Remove the penultimate sentence of 5.1.2.5, "The SAVE attribute ... result, 47 39 000087 2191 c or an automatic data object." [47:39] 48 26 000139 1982 a INTRINSIC, EXTERNAL attribute questions 48 26 000139 1982 b X3J3 consideration in progress 48 26 000139 1982 c 1. Section 5.1.2.10 Replace 'object name' with '' [48:26] 48 30 000139 1984 a INTRINSIC, EXTERNAL attribute questions 48 30 000139 1984 b X3J3 consideration in progress 48 30 000139 1984 c 2. Section 5.1.2.11 Replace 'object name' with '' [48:30] 49 26 000138 1926 a PRIVATE accessibility of a MODULE PROCEDURE 49 26 000138 1926 b X3J3 consideration in progress 49 26 000138 1926 c 2. In 5.2.3 delete the third constraint. [49:26-28] 49 31 000143 2270 a Use association and functions/subroutines/intrinsics 49 31 000143 2270 b X3J3 consideration in progress 49 31 000143 2270 c Add at the end of the first paragraph of 5.2.3 [49:31]: 49 31 000143 2271 c 49 31 000143 2272 c "If a procedure is accessible from a module, then within the scoping unit of 49 31 000143 2273 c the module one of the following must be true: 49 31 000143 2274 c (1) if it is an intrinsic procedure, it must be given the INTRINSIC 49 31 000143 2275 c attribute or be used as an intrinsic procedure 49 31 000143 2276 c (2) the procedure must have an explicit interface 49 31 000143 2277 c (3) the procedure must be given the EXTERNAL attribute and if it is a 49 31 000143 2278 c function it must be explicitly declared in a type declaration 49 31 000143 2279 c statement. 50 9 000087 2193 a PARAMETER statements and SAVE statements 50 9 000087 2193 b X3J3 approved; ready for WG5 50 9 000087 2193 c 4. Change the first constraint of section 5.2.4 to [50:9] 50 9 000087 2194 c 50 9 000087 2195 c An must not be the name of an object in a common block, a dummy 50 9 000087 2196 c argument name, a procedure name, a function result name, an automatic data 50 9 000087 2197 c object name, or the name of an object with the PARAMETER attribute. 52 20 000136 1776 a scalar-structure-component in data-implied-do 52 20 000136 1776 b X3J3 approved; ready for WG5 52 20 000136 1776 c In section 5.2.9, following the second constraint [52:20], insert the 52 20 000136 1777 c following constraint: 52 20 000136 1778 c 52 20 000136 1779 c Constraint: The must contain at least one 52 20 000136 1780 c that contains a . 52 25 000089 2307 a Errors in the DATA statement description 52 25 000089 2307 b X3J3 approved; ready for WG5 52 25 000089 2307 c 1. Add a new constraint after the second constraint following R537: [52:25] 52 25 000089 2308 c 52 25 000089 2309 c If a DATA statement constant value is a named constant or a structure 52 25 000089 2310 c constructor, the named constant or derived type must have been declared 52 25 000089 2311 c previously in the scoping unit or made accessible by use or host association. 52 44 000137 1843 a array-element in data-implied-do 52 44 000137 1843 b X3J3 consideration in progress 52 44 000137 1843 c In section 5.2.9, following the last paragraph [52:44+], add the following text: 52 44 000137 1844 c 52 44 000137 1845 c The of a must appear in at least 52 44 000137 1846 c one of each and 52 44 000137 1847 c contained within the range of the 52 44 000137 1848 c . 52 44 000137 1849 c 52 44 000137 1850 c Example: 52 44 000137 1851 c 52 44 000137 1852 c INTEGER ARRAY_1(5,5), ARRAY_2(5), ARRAY_3(10) 52 44 000137 1853 c DATA ((ARRAY_1(I, J+1), I = 1, 5), ARRAY_2(J+1), J = 0, 4) ... 52 44 000137 1854 c DATA ((ARRAY_3(I + J*1), I = 1, 2), J = 3, 4) ... 52 44 000137 1855 c 52 44 000137 1856 c TYPE SMALL 52 44 000137 1857 c INTEGER I(2) 52 44 000137 1858 c REAL R 52 44 000137 1859 c END TYPE 52 44 000137 1860 c 52 44 000137 1861 c TYPE(SMALL) GROUP(3) 52 44 000137 1862 c 52 44 000137 1863 c DATA ((GROUP(J)%I(K), K = 1, 2), J = 1, 3) ... 52 44 000137 1864 c 52 44 000137 1865 c Since ARRAY_1 is within the range of both I and J, its subscript list must 52 44 000137 1866 c contain references to both I and J, but since ARRAY_2 is only within the range 52 44 000137 1867 c of J, its subscript list need only reference J. 52 44 000137 1868 c 52 44 000137 1869 c The second DATA statement demonstrates that the DATA implied-DO variables need 52 44 000137 1870 c not be referenced in separate subscript expressions. 52 44 000137 1871 c 52 44 000137 1872 c The third DATA statement demonstrates that the implied-DO variables can be 52 44 000137 1873 c referenced in separate subscript lists of the same designator. In this case, 52 44 000137 1874 c note too that both J and K must be referenced in the designator since it falls 52 44 000137 1875 c within the range of both implied-DO variables. 53 4 000089 2313 a Errors in the DATA statement description 53 4 000089 2313 b X3J3 approved; ready for WG5 53 4 000089 2313 c 2. Delete the second sentence in the third paragraph following the 53 4 000089 2314 c constraints [53:4-5], "Each such value ...host association." 53 6 000089 2316 a Errors in the DATA statement description 53 6 000089 2316 b X3J3 approved; ready for WG5 53 6 000089 2316 c 3. In the third sentence [53:6], 53 6 000089 2317 c replace "following constant" 53 6 000089 2318 c with "following constant value". 53 11 000089 2320 a Errors in the DATA statement description 53 11 000089 2320 b X3J3 approved; ready for WG5 53 11 000089 2320 c 4. In the next paragraph, second sentence [53:11], 53 11 000089 2321 c change "constant" 53 11 000089 2322 c to "constant value". 53 17 000089 2324 a Errors in the DATA statement description 53 17 000089 2324 b X3J3 approved; ready for WG5 53 17 000089 2324 c 5. In the following paragraph, last sentence [53:17], 53 17 000089 2325 c change "constant" 53 17 000089 2326 c to "constant value". 53 18 000089 2328 a Errors in the DATA statement description 53 18 000089 2328 b X3J3 approved; ready for WG5 53 18 000089 2328 c 6. In the sixth paragraph [53:18-19], 53 18 000089 2329 c change "value of the constant" 53 18 000089 2330 c to "constant value" (twice) 53 43 000012 468 a Type of a named constant when there is implicit mapping 53 43 000012 468 b X3J3 approved; ready for WG5 53 43 000012 468 c 1. In section 5.2.10 change the second paragraph to: [53:43-47] 53 43 000012 469 c 53 43 000012 470 c "The named constant must have its type, type parameters, and shape 53 43 000012 471 c specified in a prior specification of the or 53 43 000012 472 c declared implicitly (5.3). If the named constant is typed by the implicit 53 43 000012 473 c typing rules, its appearance in any subsequent specification of the 53 43 000012 474 c must confirm this implied type and the values of any 53 43 000012 475 c implied type parameters." 54 30 000013 396 a Implicit mapping of an interface block 54 30 000013 396 b WG5 approved; ready for SC22 54 30 000013 396 c 1. In Section 5.3 in the second paragraph after the constraints [54:30], 54 30 000013 397 c in the phrase: "the default is the mapping ...", after "default": 54 30 000013 398 c 54 30 000013 399 c add "for a program unit or an interface body is default integer if 54 30 000013 400 c the letter is I,J, ... , or N and default real otherwise, and the 54 30 000013 401 c default for an internal or module procedure". 54 30 000013 402 c 54 30 000013 403 c Delete "A program ... O-Z)" 54 35 000012 477 a Type of a named constant when there is implicit mapping 54 35 000012 477 b X3J3 approved; ready for WG5 54 35 000012 477 c 2. In section 5.3 in line 3 of the paragraph that starts with "Any data 54 35 000012 478 c entity that is" after 'not null.' and before the Corrigendum 1 54 35 000012 479 c addition [54:35], add: 54 35 000012 480 c 54 35 000012 481 c "The mapping for the first letter of the data entity must either 54 35 000012 482 c have been established by a prior IMPLICIT statement or be the 54 35 000012 483 c default mapping for the letter." 54 35 000032 1243 a Implicit declaration of a derived type 54 35 000032 1243 b WG5 approved; ready for SC22 54 35 000032 1243 c 2. In paragraph 5 of 5.3 after "provided the mapping is not null.", 54 35 000032 1244 c insert the new sentence: "Note that the mapping can be to a derived 54 35 000032 1245 c type that is inaccessible in the local scope if the derived type is 54 35 000032 1246 c accessible to the host scope." [54:35] 55 2 000013 405 a Implicit mapping of an interface block 55 2 000013 405 b WG5 approved; ready for SC22 55 2 000013 405 c 2. In the example in section 5.3 for FUNCTION FUN [55:2] in the interface 55 2 000013 406 c block the comment should be changed from: 55 2 000013 407 c 55 2 000013 408 c ! All data entities must 55 2 000013 409 c ! be declared explicitly 55 2 000013 410 c 55 2 000013 411 c to 55 2 000013 412 c 55 2 000013 413 c ! Not all entities need be 55 2 000013 414 c ! declared explicitly 55 3 000013 416 a Implicit mapping of an interface block 55 3 000013 416 b WG5 approved; ready for SC22 55 3 000013 416 c 3. In the first example in section 5.3 [55:3], change "INTEGER FUN, I" 55 3 000013 417 c to be "INTEGER FUN". 56 22 000012 485 a Type of a named constant when there is implicit mapping 56 22 000012 485 b X3J3 approved; ready for WG5 56 22 000012 485 c 3. In section 5.4 in the penultimate paragraph [56:22-24]: 56 22 000012 486 c in line 3, delete "currently" 56 22 000012 487 c and in lines 4-5 replace "this implied type" 56 22 000012 488 c by "the implied type and type parameters". 56 24 000142 2193 a Namelist I/O 56 24 000142 2193 b X3J3 consideration in progress 56 24 000142 2193 c 1. In section 5.4, add the following paragraph after the fourth 56 24 000142 2194 c paragraph following the constraints [56:24+]: 56 24 000142 2195 c 56 24 000142 2196 c A derived type object must not appear as a if any 56 24 000142 2197 c component ultimately contained within the object is not accessible within 56 24 000142 2198 c the scoping unit containing the namelist input/output statement on which 56 24 000142 2199 c its containing is specified. An example is a structure 56 24 000142 2200 c accessed from a module within which its type is PUBLIC but its components 56 24 000142 2201 c are PRIVATE. 57 17 000160 815 a Variables with the TARGET attribute in EQUIVALENCE groups 57 17 000160 815 b X3J3 approved; ready for WG5 57 17 000160 815 c After the sixth constraint of section 5.5.1 add [57:17+] 57 17 000160 816 c 57 17 000160 817 c Constraint: An must not have the TARGET attribute. 59 11 000071 1436 a Use association and common block names 59 11 000071 1436 b X3J3 approved; ready for WG5 59 11 000071 1436 c 1. In the first sentence of 5.5.2.1 after "For each common block", 59 11 000071 1437 c insert "in a scoping unit". [59:11] 59 19 000071 1439 a Use association and common block names 59 19 000071 1439 b X3J3 approved; ready for WG5 59 19 000071 1439 c 2. At the end of 5.5.2.1, add the following paragraph: 59 19 000071 1440 c 59 19 000071 1441 c "Only COMMON statements and EQUIVALENCE statements appearing in the 59 19 000071 1442 c scoping unit contribute to common block storage sequences formed in that 59 19 000071 1443 c unit. Variables, in common blocks, made accessible by use association or 59 19 000071 1444 c host association do not contribute." [59:19] 59 30 000071 1446 a Use association and common block names 59 30 000071 1446 b X3J3 approved; ready for WG5 59 30 000071 1446 c 3. At the end of the first paragraph of 5.5.2.3, add the following sentence: 59 30 000071 1447 c 59 30 000071 1448 c "Use association or host association may cause these associated objects 59 30 000071 1449 c to be accessible in the same scoping unit." [59:30] 60 19 000071 1451 a Use association and common block names 60 19 000071 1451 b X3J3 approved; ready for WG5 60 19 000071 1451 c 4. Delete the last two sentences in 5.5.2.5. [60:19] 63 30 000166 1144 a Array named constant is a constant expression? 63 30 000166 1144 b X3J3 approved; ready for WG5 63 30 000166 1144 c Section 6.2.1, second paragraph: 63 30 000166 1145 c change "the name of a constant expression (5.1.2.1 and 5.2.10)" 63 30 000166 1146 c to "a named constant (5.1.2.1 and 5.2.10)" [63:30-31] 76 22 000163 963 a Pointer assignment of a disassociated pointer 76 22 000163 963 b X3J3 approved; ready for WG5 76 22 000163 963 c In the final sentence of section 7.1.4.1, insert before the terminating 76 22 000163 964 c period 76 22 000163 965 c 76 22 000163 966 c ", or as the target in a pointer assignment statement." [76:22] 77 24 000097 2718 a Specification expression 77 24 000097 2718 b X3J3 approved; ready for WG5 77 24 000097 2718 c 1. Replace 7.1.6.1 (6), in the first list, with the following: [77:24-28] 77 24 000097 2719 c 77 24 000097 2720 c (6) A reference to an intrinsic function which is: 77 24 000097 2721 c a) an array inquiry function (13.10.15) other than ALLOCATED, 77 24 000097 2722 c b) the bit inquiry function BIT_SIZE, 77 24 000097 2723 c c) the character inquiry function LEN, 77 24 000097 2724 c d) the kind inquiry function KIND, or 77 24 000097 2725 c e) a numeric inquiry function (13.10.8) 77 24 000097 2726 c and where each argument of the function is 77 24 000097 2727 c a) a constant expression, or 77 24 000097 2728 c b) a variable whose properties inquired about are not: 77 24 000097 2729 c 1) assumed 77 24 000097 2730 c 2) defined by an expression that is not a constant expression 77 24 000097 2731 c or 77 24 000097 2732 c 3) definable by an ALLOCATE or POINTER assignment statement 77 27 000047 1695 a Automatic data object in initialization expressions 77 27 000047 1695 b WG5 approved; ready for SC22 77 27 000047 1695 c 1. Section 7.1.6.1, page 77, item (6) 77 27 000047 1696 c change "not assumed or" 77 27 000047 1697 c to "not assumed, are not defined by an expression that is not 77 27 000047 1698 c a constant expression, and are not" [77:27] 78 6 000097 2734 a Specification expression 78 6 000097 2734 b X3J3 approved; ready for WG5 78 6 000097 2734 c 2. Replace 7.1.6.1 (6), in the second list with the following: [78:6-10] 78 6 000097 2735 c 78 6 000097 2736 c (6) A reference to an intrinsic function which is: 78 6 000097 2737 c a) an array inquiry function (13.10.15) other than ALLOCATED, 78 6 000097 2738 c b) the bit inquiry function BIT_SIZE, 78 6 000097 2739 c c) the character inquiry function LEN, 78 6 000097 2740 c d) the kind inquiry function KIND, or 78 6 000097 2741 c e) a numeric inquiry function (13.10.8) 78 6 000097 2742 c and where each argument of the function is 78 6 000097 2743 c a) an initialization expression, or 78 6 000097 2744 c b) a variable whose properties inquired about are not: 78 6 000097 2745 c 1) assumed 78 6 000097 2746 c 2) defined by an expression that is not a 78 6 000097 2747 c initialization expression or 78 6 000097 2748 c 3) definable by an ALLOCATE or POINTER assignment 78 6 000097 2749 c statement 78 9 000047 1700 a Automatic data object in initialization expressions 78 9 000047 1700 b WG5 approved; ready for SC22 78 9 000047 1700 c 2. Section 7.1.6.1, page 78, item (6) 78 9 000047 1701 c change "not assumed or" 78 9 000047 1702 c to "not assumed, are not defined by an expression that is not 78 9 000047 1703 c an initialization expression, and are not" [78:9] 79 11 000097 2751 a Specification expression 79 11 000097 2751 b X3J3 approved; ready for WG5 79 11 000097 2751 c 3. Replace 7.1.6.2 (9) with the following: [79:11-15] 79 11 000097 2752 c 79 11 000097 2753 c (9) A reference to an intrinsic function which is: 79 11 000097 2754 c a) an array inquiry function (13.10.15) other than ALLOCATED, 79 11 000097 2755 c b) the bit inquiry function BIT_SIZE, 79 11 000097 2756 c c) the character inquiry function LEN, 79 11 000097 2757 c d) the kind inquiry function KIND, or 79 11 000097 2758 c e) a numeric inquiry function (13.10.8) 79 11 000097 2759 c and where each argument of the function is 79 11 000097 2760 c a) a restricted expression, or 79 11 000097 2761 c b) a variable whose properties inquired about are not: 79 11 000097 2762 c 1) dependent on the upper bound of the last dimension of an 79 11 000097 2763 c assumed-size array 79 11 000097 2764 c 2) defined by an expression that is not a 79 11 000097 2765 c restricted expression or 79 11 000097 2766 c 3) definable by an ALLOCATE or POINTER assignment statement 79 23 000012 490 a Type of a named constant when there is implicit mapping 79 23 000012 490 b X3J3 approved; ready for WG5 79 23 000012 490 c 4. In section 7.1.6.2, in line 2 of the paragraph after the constraint 79 23 000012 491 c [79:23] delete "currently". 92 12 000079 1695 a Automatic character and ALLOCATABLE, POINTER and TARGET attributes 92 12 000079 1695 b X3J3 approved; ready for WG5 92 12 000079 1695 c 1. In the third constraint of section 7.5.2 [92:12] 92 12 000079 1696 c change ", type parameters," 92 12 000079 1697 c to ", kind type parameters," 92 15 000079 1699 a Automatic character and ALLOCATABLE, POINTER and TARGET attributes 92 15 000079 1699 b X3J3 approved; ready for WG5 92 15 000079 1699 c 2. Add at the beginning of the paragraph following the constraints of 92 15 000079 1700 c section 7.5.2 [92:15], 92 15 000079 1701 c 92 15 000079 1702 c "The target must have the same type parameters as the pointer." 93 10 000084 2940 a Change masked array assignment constraint to prose 93 10 000084 2940 b WG5 approved; ready for SC22 93 10 000084 2940 c 1. Delete the first constraint following rule R743. [93:10-11] 93 21 000084 2942 a Change masked array assignment constraint to prose 93 21 000084 2942 b WG5 approved; ready for SC22 93 21 000084 2942 c 2. Use the constraint body as the new first paragraph of section 7.5.3.2. 93 21 000084 2943 c [93:21] 93 29 000080 2885 a Vector subscripts in masked array assignment statements 93 29 000080 2885 b WG5 approved; ready for SC22 93 29 000080 2885 c 1. In the second paragraph of section 7.5.3.2 after 93 29 000080 2886 c [93:29], add "or ". 93 34 000080 2888 a Vector subscripts in masked array assignment statements 93 34 000080 2888 b WG5 approved; ready for SC22 93 34 000080 2888 c 2. In the third paragraph of section 7.5.3.2 after [93:34], 93 34 000080 2889 c add "or ". 93 37 000111 494 a Array constructors in masked assignment statements 93 37 000111 494 b X3J3 approved; ready for WG5 93 37 000111 494 c In 7.5.3.2 following the third paragraph [93:37+], insert the 93 37 000111 495 c following paragraph: 93 37 000111 496 c 93 37 000111 497 c If an array constructor appears in an , the array 93 37 000111 498 c constructor is evaluated without any masked control by the 93 37 000111 499 c and then the is evaluated. 120 25 000072 2701 a Missing constraint for SIZE= 120 25 000072 2701 b WG5 approved; ready for SC22 120 25 000072 2701 c Section 9.4.1, [120:25], add a constraint to the end of list: 120 25 000072 2702 c 120 25 000072 2703 c "If a SIZE= specifier is present, an ADVANCE= specifier also must appear." 123 30 000069 2673 a I/O implied DO variable 123 30 000069 2673 b WG5 approved; ready for SC22 123 30 000069 2673 c In section 9.4.2, in the second constraint, replace the word 123 30 000069 2674 c "scalar" with "named scalar variable". [123:30] 124 44 000150 52 a Undefinition of implied-DO variables in I/O statements 124 44 000150 52 b X3J3 approved; ready for WG5 124 44 000150 52 c 1. Section 9.4.3, second paragraph following the numbered list [124:44], 124 44 000150 53 c change 124 44 000150 54 c any implied-DO variables become undefined 124 44 000150 55 c to 124 44 000150 56 c if the input/output statement contains any implied-DOs, all of 124 44 000150 57 c the implied-DO variables in the statement become undefined 125 7 000150 59 a Undefinition of implied-DO variables in I/O statements 125 7 000150 59 b X3J3 approved; ready for WG5 125 7 000150 59 c 2. Section 9.4.3, second-to-last paragraph [125:7-8], 125 7 000150 60 c change 125 7 000150 61 c any implied-DO variables become undefined 125 7 000150 62 c to 125 7 000150 63 c if the input statement contains any implied-DOs, all of 125 7 000150 64 c the implied-DO variables in the statement become undefined 128 27 000169 1290 a End of Namelist Input 128 27 000169 1290 b X3J3 consideration in progress 128 27 000169 1290 c In section 9.4.6, item 3 [128:27-29] 128 27 000169 1291 c 128 27 000169 1292 c delete "or namelist input reaches the end of a record after having 128 27 000169 1293 c processed a name-value subsequence for every item in the 128 27 000169 1294 c " 139 37 000131 1432 a Formatted Input and Kind Type Parameters 139 37 000131 1432 b X3J3 approved; ready for WG5 139 37 000131 1432 c 1. In Section 10.5.1.1, third paragraph [139:37-38], 139 37 000131 1433 c 139 37 000131 1434 c change "be in the form of an optionally signed integer constant" 139 37 000131 1435 c to "be a (R401)". 139 37 000131 1436 c 139 37 000131 1437 c note: is a BNF term. 139 45 000131 1439 a Formatted Input and Kind Type Parameters 139 45 000131 1439 b X3J3 approved; ready for WG5 139 45 000131 1439 c 2. In Section 10.5.1.1, fourth paragraph [139:45], 139 45 000131 1440 c 139 45 000131 1441 c change "in the form of an unsigned integer constant" 139 45 000131 1442 c to "as a ". 139 45 000131 1443 c 139 45 000131 1444 c Change "Note that an integer constant" 139 45 000131 1445 c to "Note that a ". 139 45 000131 1446 c 139 45 000131 1447 c note: This deals with output, not input, but we should make it clear that 139 45 000131 1448 c output doesn't produce kind type parameters either. 140 6 000131 1450 a Formatted Input and Kind Type Parameters 140 6 000131 1450 b X3J3 approved; ready for WG5 140 6 000131 1450 c 3. In Section 10.5.1.1, sixth paragraph [140:6], 140 6 000131 1451 c 140 6 000131 1452 c change "the unsigned integer constant" 140 6 000131 1453 c to "the ". 140 25 000131 1455 a Formatted Input and Kind Type Parameters 140 25 000131 1455 b X3J3 approved; ready for WG5 140 25 000131 1455 c 4. In Section 10.5.1.2.1 [140:25], list item (1), 140 25 000131 1456 c 140 25 000131 1457 c change "Explicitly signed integer constant" 140 25 000131 1458 c to "A followed by a ". 140 26 000131 1460 a Formatted Input and Kind Type Parameters 140 26 000131 1460 b X3J3 approved; ready for WG5 140 26 000131 1460 c 5. In Section 10.5.1.2.1 items (2) and (3) [140:26-27], 140 26 000131 1461 c 140 26 000131 1462 c change "an optionally signed integer constant" 140 26 000131 1463 c to "a ". 143 47 000131 1465 a Formatted Input and Kind Type Parameters 143 47 000131 1465 b X3J3 approved; ready for WG5 143 47 000131 1465 c 6. In Section 10.5.2, second paragraph [143:47], 143 47 000131 1466 c 143 47 000131 1467 c change "additional characters in the field" 143 47 000131 1468 c to "additional characters in the field, which are ignored". 144 7 000131 1470 a Formatted Input and Kind Type Parameters 144 7 000131 1470 b X3J3 approved; ready for WG5 144 7 000131 1470 c 7. In section 10.5.3, first paragraph [144:7-9], 144 7 000131 1471 c 144 7 000131 1472 c replace the last sentence 144 7 000131 1473 c with "The kind type parameter of all characters transferred and 144 7 000131 1474 c converted under control of one A or G edit descriptor is implied by 144 7 000131 1475 c the kind of the corresponding list item." 144 37 000061 2237 a G edit descriptor with "d" = 0 144 37 000061 2237 b WG5 approved; ready for SC22 144 37 000061 2237 c 1. In section 10.5.4.1.2 second paragraph, 3rd sentence, 144 37 000061 2238 c after "- 0.5," add " or N is identically 0 and d is 0,". [144:37] 144 40 000061 2240 a G edit descriptor with "d" = 0 144 40 000061 2240 b WG5 approved; ready for SC22 144 40 000061 2240 c 2. In section 10.5.4.1.2, second paragraph, fourth sentence, 144 40 000061 2241 c after "N is identically 0" add " and d is not zero". [144:40] 148 17 000131 1477 a Formatted Input and Kind Type Parameters 148 17 000131 1477 b X3J3 approved; ready for WG5 148 17 000131 1477 c 8. In Section 10.8, second paragraph [148:17], 148 17 000131 1478 c 148 17 000131 1479 c replace "constant with no kind type parameter specified." 148 17 000131 1480 c with "constant. Neither nor may have kind type parameters 148 17 000131 1481 c specified. The constant is interpreted as though it had the same 148 17 000131 1482 c kind type parameter as the corresponding list item." 149 1 000131 1484 a Formatted Input and Kind Type Parameters 149 1 000131 1484 b X3J3 approved; ready for WG5 149 1 000131 1484 c 9. In section 10.8.1, sixth paragraph [149:1-2], 149 1 000131 1485 c 149 1 000131 1486 c replace "character literal constant of the same kind as" 149 1 000131 1487 c with "possibly delimited sequence of zero or more s 149 1 000131 1488 c whose kind type parameter is implied by the kind of". 149 12 000043 1532 a List-directed character input 149 12 000043 1532 b WG5 approved; ready for SC22 149 12 000043 1532 c 1. Section 10.8.1: Add " and" to the end of item (4), and [149:12] 149 12 000043 1534 a List-directed character input 149 12 000043 1534 b WG5 approved; ready for SC22 149 12 000043 1534 c 2. Section 10.8.1: Add an additional item to the list after item (4): 149 12 000043 1535 c [149:12] 149 12 000043 1536 c 149 12 000043 1537 c "(5) The character constant contains at least one character," 151 7 000131 1490 a Formatted Input and Kind Type Parameters 151 7 000131 1490 b X3J3 approved; ready for WG5 151 7 000131 1490 c 10. In section 10.8.2, ninth paragraph [151:7], 151 7 000131 1491 c 151 7 000131 1492 c delete "possibly are preceded by a and an underscore,". 151 11 000131 1494 a Formatted Input and Kind Type Parameters 151 11 000131 1494 b X3J3 approved; ready for WG5 151 11 000131 1494 c 11. In section 10.8.2, tenth paragraph [151:11], 151 11 000131 1495 c 151 11 000131 1496 c delete "possibly are preceded by a and an underscore,". 151 31 000131 1498 a Formatted Input and Kind Type Parameters 151 31 000131 1498 b X3J3 approved; ready for WG5 151 31 000131 1498 c 12. In Section 10.9, third paragraph [151:31-32], 151 31 000131 1499 c 151 31 000131 1500 c replace "constant with no kind type parameter specified." 151 31 000131 1501 c with "constant. Neither nor may have kind type parameters 151 31 000131 1502 c specified. The constant is interpreted as though it had the same 151 31 000131 1503 c kind type parameter as the corresponding list item." 151 39 000142 2203 a Namelist I/O 151 39 000142 2203 b X3J3 consideration in progress 151 39 000142 2203 c 2. In section 10.9.1, replace item (2) with [151:39-40] 151 39 000142 2204 c "The character & followed immediately by the 151 39 000142 2205 c as specified in the namelist statement," 152 4 000165 1090 a Vector subscripts in Namelist input 152 4 000165 1090 b X3J3 consideration in progress 152 4 000165 1090 c Add the following phrase in section 10.9.1, second paragraph, 152 4 000165 1091 c after "zero-sized array section," [152:4]: 152 4 000165 1092 c 152 4 000165 1093 c 'an array subscript with a vector subscript,' 153 15 000131 1505 a Formatted Input and Kind Type Parameters 153 15 000131 1505 b X3J3 approved; ready for WG5 153 15 000131 1505 c 13. In section 10.9.1.3, fifth paragraph [153:15-16], 153 15 000131 1506 c 153 15 000131 1507 c replace "character literal constant of the same kind as" 153 15 000131 1508 c with "delimited sequence of zero or more s whose kind 153 15 000131 1509 c type parameter is implied by the kind of". 155 12 000131 1511 a Formatted Input and Kind Type Parameters 155 12 000131 1511 b X3J3 approved; ready for WG5 155 12 000131 1511 c 14. In section 10.9.2.1, seventh paragraph [155:12], 155 12 000131 1512 c 155 12 000131 1513 c delete "possibly are preceded by a and an underscore,". 155 16 000131 1515 a Formatted Input and Kind Type Parameters 155 16 000131 1515 b X3J3 approved; ready for WG5 155 16 000131 1515 c 15. In section 10.9.2.1, eighth paragraph, [155:16], 155 16 000131 1516 c 155 16 000131 1517 c delete "possibly are preceded by a and an underscore,". 158 11 000155 408 a Multiple USE statements, rename and only lists. 158 11 000155 408 b X3J3 approved; ready for WG5 158 11 000155 408 c 1. In section 11.3.2, R1109 [158:11] 158 11 000155 409 c change "" 158 11 000155 410 c to "" 158 13 000155 412 a Multiple USE statements, rename and only lists. 158 13 000155 412 b X3J3 approved; ready for WG5 158 13 000155 412 c 2. In section 11.3.2, the first constraint following R1109 [158:13] 158 13 000155 413 c change "" 158 13 000155 414 c to "" 158 19 000155 416 a Multiple USE statements, rename and only lists. 158 19 000155 416 b X3J3 approved; ready for WG5 158 19 000155 416 c 3. In section 11.3.2, paragraph beginning "A USE statement" [158:19] 158 19 000155 417 c change "s" 158 19 000155 418 c to "s" 158 22 000155 420 a Multiple USE statements, rename and only lists. 158 22 000155 420 b X3J3 approved; ready for WG5 158 22 000155 420 c 4. In section 11.3.2, paragraph beginning "More than one" [158:22-23] 158 22 000155 421 c change "s and s" 158 22 000155 422 c to "s and renames in s" 158 26 000128 1245 a Use associated generic names and renaming 158 26 000128 1245 b X3J3 approved; ready for WG5 158 26 000128 1245 c The sentence in section 11.3.2 that states that if two "generic interfaces 158 26 000128 1246 c that are accessible in a scoping unit have the same name" [158:26-27], 158 26 000128 1247 c 158 26 000128 1248 c change "the same name" 158 26 000128 1249 c to "the same local name". 158 28 000074 2754 a Meaning of "referenced" in 11.3.2 158 28 000074 2754 b WG5 approved; ready for SC22 158 28 000074 2754 c In section 11.3.2 [158:28] 158 28 000074 2755 c change the term "no entity is referenced by this name" 158 28 000074 2756 c to "the name is not used to refer to an entity". 160 29 000058 1242 a Ambiguous use of "keyword" 160 29 000058 1242 b X3J3 approved; ready for WG5 160 29 000058 1242 c 7. Page 160, section 11.3.3.5, first paragraph, third line [160:29] 160 29 000058 1243 c change "keywords" to "argument keywords" 161 16 00000b 16 a Minor edits and corrections for Technical Corrigendum #2 161 16 00000b 16 b X3J3 approved; ready for WG5 161 16 00000b 16 c 1. 11.3.3.7, in the second sentence [161:16], change "C.11.5" to "C.11.4" 163 39 000090 2413 a Subroutine and function names in nested scopes 163 39 000090 2413 b X3J3 consideration in progress 163 39 000090 2413 c 1. In section 12.1.2.2.1: [163:39] 163 39 000090 2414 c 163 39 000090 2415 c change: A name that appears in the scoping unit as an in 163 39 000090 2416 c an 163 39 000090 2417 c 163 39 000090 2418 c to: A name that is declared to be an external procedure name (by an 163 39 000090 2419 c or an ), or that appears as a 163 39 000090 2420 c in a 164 4 000090 2422 a Subroutine and function names in nested scopes 164 4 000090 2422 b X3J3 consideration in progress 164 4 000090 2422 c 2. In section 12.1.2.2.1: [164:4] 164 4 000090 2423 c 164 4 000090 2424 c change: (2) A in a 164 4 000090 2425 c 164 4 000090 2426 c to: .......................................... within an 164 4 000090 2427 c 164 6 000090 2429 a Subroutine and function names in nested scopes 164 6 000090 2429 b X3J3 consideration in progress 164 6 000090 2429 c 3. In section 12.1.2.2.1: [164:6] 164 6 000090 2430 c 164 6 000090 2431 c change: (3) A in a 164 6 000090 2432 c 164 6 000090 2433 c to: .............................................. within an 164 6 000090 2434 c 164 7 000090 2436 a Subroutine and function names in nested scopes 164 7 000090 2436 b X3J3 consideration in progress 164 7 000090 2436 c 4. In section 12.1.2.2.1: [164:7] 164 7 000090 2437 c 164 7 000090 2438 c delete item (4) of the list and renumber the rest of the list. 164 20 000118 3406 a Named constructs and host association 164 20 000118 3406 b WG5 approved; ready for SC22 164 20 000118 3406 c Add new item to the list in section 12.1.2.2.1 [164:20] and adjust the 164 20 000118 3407 c list punctuation accordingly. 164 20 000118 3408 c 164 20 000118 3409 c "(16) The name of a named construct" 164 21 000088 2258 a Common block names and local names 164 21 000088 2258 b X3J3 approved; ready for WG5 164 21 000088 2258 c In section 12.1.2.2.1 in the sentence that contains the list of items 164 21 000088 2259 c replace 'that has this as its nongeneric name is inaccessible.' 164 21 000088 2260 c with 'that has this as its nongeneric name is inaccessible 164 21 000088 2261 c by that name by host association.' [164:21] 164 25 000032 1248 a Implicit declaration of a derived type 164 25 000032 1248 b WG5 approved; ready for SC22 164 25 000032 1248 c 3. In paragraph 3 of 12.1.2.2.1 after "prior to the DATA statement.", 164 25 000032 1249 c insert a new paragraph: [164:25] 164 25 000032 1250 c 164 25 000032 1251 c "If a derived type name of a host is inaccessible, data entities of 164 25 000032 1252 c that type or subobjects of such data entities still can be 164 25 000032 1253 c accessible." 166 4 000049 1128 a Characteristics of function results 166 4 000049 1128 b X3J3 consideration in progress 166 4 000049 1128 c 2. Replace the last two sentences in 12.2.1.1 [166:4-6] with the following: 166 4 000049 1129 c 166 4 000049 1130 c If the shape or character length type parameter is not constant, the 166 4 000049 1131 c corresponding characteristic is the method by which the value is to be 166 4 000049 1132 c determined when the procedure is invoked. This includes the possibility that 166 4 000049 1133 c the value is assumed or that it is given by evaluating a specification 166 4 000049 1134 c expression. Two such methods are considered to be the same if the following 166 4 000049 1135 c are true: 166 4 000049 1136 c 166 4 000049 1137 c (1) they yield the same value 166 4 000049 1138 c 166 4 000049 1139 c (2) if one involves the evaluation of variables then the other must involve 166 4 000049 1140 c the evaluation of the same storage units (although not necessarily the 166 4 000049 1141 c same variable names). 166 14 000049 1113 a Characteristics of function results 166 14 000049 1113 b X3J3 consideration in progress 166 14 000049 1113 c 1. Replace the last two sentences in 12.2.2 [166:14-16] with the following: 166 14 000049 1114 c 166 14 000049 1115 c If the shape or character length type parameter is not constant, the 166 14 000049 1116 c corresponding characteristic is the method by which the value is to be 166 14 000049 1117 c determined when the function is invoked. This includes the possibility that 166 14 000049 1118 c the value is assumed or that it is given by evaluating a specification 166 14 000049 1119 c expression. Two such methods are considered to be the same if the following 166 14 000049 1120 c are true: 166 14 000049 1121 c 166 14 000049 1122 c (1) they yield the same value 166 14 000049 1123 c 166 14 000049 1124 c (2) if one involves the evaluation of variables then the other 166 14 000049 1125 c must involve the evaluation of the same storage units (although 166 14 000049 1126 c not necessarily the same variable names). 167 31 000117 750 a Use of MODULE PROCEDURE statement in internal procedures 167 31 000117 750 b X3J3 approved; ready for WG5 167 31 000117 750 c Replace the second constraint in section 12.3.2.1 [167:31] with: 167 31 000117 751 c 167 31 000117 752 c "The MODULE PROCEDURE specification is allowed only if the 167 31 000117 753 c has a and is contained in a scoping 167 31 000117 754 c unit where each is accessible as a module procedure." 167 39 000057 2086 a Prohibition against multiple explicit specific interfaces 167 39 000057 2086 b WG5 approved; ready for SC22 167 39 000057 2086 c Section 12.3.2.1, the sentence that begins "An interface body..." change 167 39 000057 2087 c "explicit interface" to "explicit specific interface". [167:39] 168 24 000058 1245 a Ambiguous use of "keyword" 168 24 000058 1245 b X3J3 approved; ready for WG5 168 24 000058 1245 c 8. Page 168, replace the second sentence of the paragraph 168 24 000058 1246 c following the line "END INTERFACE" [168:24] with 168 24 000058 1247 c 168 24 000058 1248 c "Invocations of these procedures may 168 24 000058 1249 c use argument keywords; for example:" 168 24 000058 1250 c rationale: "keyword calls" is not defined. In general invocations 168 24 000058 1251 c can use both positional and argument keywords. 170 42 000006 268 a Procedure specifications in a scoping unit 170 42 000006 268 b WG5 approved; ready for SC22 170 42 000006 268 c At the end of the fourth paragraph following R1207 in 12.3.2.2 [170:42], 170 42 000006 269 c add: 170 42 000006 270 c 170 42 000006 271 c A name that appears in an EXTERNAL statement must not also appear 170 42 000006 272 c as a specific procedure name in an interface block in the scoping unit. 172 8 000178 1736 a Specific routine with same name as generic passed as argument 172 8 000178 1736 b X3J3 consideration in progress 172 8 000178 1736 c Section 12.4.1, insert the following in the penultimate constraint, ahead 172 8 000178 1737 c of "(12.3.2.1, 13.1)" [172:8]: 172 8 000178 1738 c 172 8 000178 1739 c "unless it is also a specific name" 172 13 000058 1253 a Ambiguous use of "keyword" 172 13 000058 1253 b X3J3 approved; ready for WG5 172 13 000058 1253 c 9. Page 172, in the first paragraph following the 172 13 000058 1254 c constraints [172:13-17] change "a keyword" to "an argument 172 13 000058 1255 c keyword" twice, and change "the keyword" 172 13 000058 1256 c to "the argument keyword" 172 41 00000a 41 a Minor edits and corrections for Technical Corrigendum #1 172 41 00000a 41 b WG5 approved; ready for SC22 172 41 00000a 41 c 3. 12.4.1.1, first paragraph, last line [172:41]; Change "of the the 172 41 00000a 42 c dummy" to "of the dummy" 172 41 000119 3437 a Rank of assumed-shape array 172 41 000119 3437 b WG5 approved; ready for SC22 172 41 000119 3437 c At the end of the first paragraph of section 12.4.1.1 [172:41], add: "If 172 41 000119 3438 c the dummy argument is an assumed-shape array, the rank of the dummy argument 172 41 000119 3439 c must agree with the rank of the actual argument." 173 13 000039 957 a Association of a pointer actual argument with a dummy argument 173 13 000039 957 b X3J3 approved; ready for WG5 173 13 000039 957 c 2. Add the following new paragraph following the current fifth 173 13 000039 958 c paragraph of section 12.4.1.1: [173:13+] 173 13 000039 959 c 173 13 000039 960 c If the dummy argument is not a pointer and the corresponding actual 173 13 000039 961 c argument is, the actual argument must be currently associated with a 173 13 000039 962 c target and the dummy argument becomes argument associated with that 173 13 000039 963 c target. 173 14 000125 1009 a Copy in/copy out of target dummy arguments 173 14 000125 1009 b X3J3 consideration in progress 173 14 000125 1009 c 1. In section 12.4.1.1, in the paragraph that starts "If the actual 173 14 000125 1010 c argument has the TARGET attribute," [173:14] 173 14 000125 1011 c change "do not become" 173 14 000125 1012 c to "do not necessarily become" 173 16 000125 1014 a Copy in/copy out of target dummy arguments 173 16 000125 1014 b X3J3 consideration in progress 173 16 000125 1014 c 2. In section 12.4.1.1, in the paragraph that starts "If the actual 173 16 000125 1015 c argument has the TARGET attribute," add to the end of the first 173 16 000125 1016 c sentence [173:16] 173 16 000125 1017 c "that is, whether the pointers associated with the actual argument 173 16 000125 1018 c become associated with the dummy argument is processor dependent." 177 29 00000a 44 a Minor edits and corrections for Technical Corrigendum #1 177 29 00000a 44 b WG5 approved; ready for SC22 177 29 00000a 44 c 4. 12.5.2.4, at end of first paragraph [177:29]; Add new sentence 177 29 00000a 45 c "When a statement function is invoked, an instance of that statement 177 29 00000a 46 c function is created." 178 19 000055 1993 a Characteristics of character function results 178 19 000055 1993 b WG5 approved; ready for SC22 178 19 000055 1993 c In Section 12.5.2.5 in the sentence that starts: "Otherwise, 178 19 000055 1994 c they ... " delete: "all be scalars ... length or". [178:19] 179 38 000053 1949 a Optional intrinsic function arguments 179 38 000053 1949 b WG5 approved; ready for SC22 179 38 000053 1949 c 1. Add the following point to the numbered list in section 12.5.2.8: 179 38 000053 1950 c [179:38] 179 38 000053 1951 c 179 38 000053 1952 c (5) If it is an array, it must not be supplied as an actual 179 38 000053 1953 c argument to an elemental procedure unless an array of the same 179 38 000053 1954 c rank is supplied as an actual argument corresponding to a 179 38 000053 1955 c nonoptional dummy argument of that elemental procedure. 179 39 000053 1957 a Optional intrinsic function arguments 179 39 000053 1957 b WG5 approved; ready for SC22 179 39 000053 1957 c 2. In the paragraph following the numbered list, replace "It" with 179 39 000053 1958 c "Except as noted in (5) above, it" [179:39] 180 4 000081 1862 a Pointer actual argument overlap 180 4 000081 1862 b X3J3 consideration in progress 180 4 000081 1862 c 1. In section 12.5.2.9, [180:4] after "dummy argument" add 180 4 000081 1863 c ", unless the dummy argument has either the POINTER or TARGET attribute" 180 4 000081 1864 c 180 36 000081 1866 a Pointer actual argument overlap 180 36 000081 1866 b X3J3 consideration in progress 180 36 000081 1866 c 2. In section 12.5.2.9, [180:36-38] in the second to last paragraph on the 180 36 000081 1867 c page, after "execution of the procedure" add ", unless all dummy arguments 180 36 000081 1868 c involved in the overlap have the POINTER or TARGET attribute". 182 4 000052 1876 a Expressions in statement function definitions 182 4 000052 1876 b WG5 approved; ready for SC22 182 4 000052 1876 c 1. Section 12.5.4: First constraint, first sentence [182:4] 182 4 000052 1877 c change "references to scalar variables and array elements" 182 4 000052 1878 c to "references to variables" 182 4 000052 1879 c 182 4 000052 1880 c change "intrinsic operators" 182 4 000052 1881 c to "intrinsic operations" 182 4 000052 1882 c 182 4 000052 1883 c after first sentence add 182 4 000052 1884 c 182 4 000052 1885 c If contains a reference to a function or a function 182 4 000052 1886 c dummy procedure, the reference must not require an explicit 182 4 000052 1887 c interface, the function must not require an explicit interface or 182 4 000052 1888 c be a transformational intrinsic, and the result must be scalar. 182 4 000052 1889 c If an argument to a function or a function dummy procedure is array 182 4 000052 1890 c valued, it must be an array name. 182 12 000052 1892 a Expressions in statement function definitions 182 12 000052 1892 b WG5 approved; ready for SC22 182 12 000052 1892 c 2. Section 12.5.4: Second constraint, third sentence [182:12] 182 12 000052 1893 c change "scalar variable, array element" 182 12 000052 1894 c to "variable" 182 12 000103 3155 a Statement Function with unreferenced dummy argument 182 12 000103 3155 b WG5 approved; ready for SC22 182 12 000103 3155 c In section 12.5.4 split the second constraint at "If a scalar variable 182 12 000103 3156 c ..." [182:12] into a new constraint and add "dummy-arg-name," just before 182 12 000103 3157 c "scalar variable". 182 19 000052 1896 a Expressions in statement function definitions 182 19 000052 1896 b WG5 approved; ready for SC22 182 19 000052 1896 c 3. Section 12.5.4: Fifth constraint, first sentence delete second word 182 19 000052 1897 c ("scalar") [182:19] 182 20 000062 2288 a Statement function constraints 182 20 000062 2288 b WG5 approved; ready for SC22 182 20 000062 2288 c In the last constraint after R1226 in section 12.5.4 182 20 000062 2289 c replace "local to" 182 20 000062 2290 c with "accessible in". [182:20] 183 37 000058 1258 a Ambiguous use of "keyword" 183 37 000058 1258 b X3J3 approved; ready for WG5 183 37 000058 1258 c 10. Section 13.3, first sentence [183:37], set "positional arguments" 183 37 000058 1259 c and "keyword arguments" in regular font 183 38 000058 1261 a Ambiguous use of "keyword" 183 38 000058 1261 b X3J3 approved; ready for WG5 183 38 000058 1261 c 11. Page 183, section 13.3, first paragraph, third line [183:38] 183 38 000058 1262 c 183 38 000058 1263 c change "the keyword" to "the argument keyword" and 183 38 000058 1264 c change "A keyword" to "An argument keyword" 184 18 000159 739 a May undefined expressions be used as arguments to INQUIRY functions 184 18 000159 739 b X3J3 consideration in progress 184 18 000159 739 c 1. In section 13.5.4 Character Inquiry Function [184:18-19] 184 18 000159 740 c replace the second sentence "The value of ...." 184 18 000159 741 c 184 18 000159 742 c with "If the argument to this function consists of a single primary 184 18 000159 743 c (7.1.1.1) that is a variable name then that variable need not be defined." 185 4 000159 745 a May undefined expressions be used as arguments to INQUIRY functions 185 4 000159 745 b X3J3 consideration in progress 185 4 000159 745 c 2. In section 13.5.7 Bit Manipulation and Inquiry Procedures [185:4-5] 185 4 000159 746 c In the paragraph beginning "An inquiry ..." 185 4 000159 747 c replace the second sentence "The value of ...." 185 4 000159 748 c 185 4 000159 749 c with "If the argument to this function consists of a single primary 185 4 000159 750 c (7.1.1.1) that is a variable name then that variable need not be defined, 185 4 000159 751 c if a pointer it may be disassociated, and if allocatable need not be 185 4 000159 752 c allocated." 186 5 000108 434 a Referencing disassociated pointers 186 5 000108 434 b X3J3 approved; ready for WG5 186 5 000108 434 c 2. Replace the first two sentences in section 13.7.2 [186:5] with: 186 5 000108 435 c 186 5 000108 436 c "The inquiry functions RADIX, DIGITS, MINEXPONENT, MAXEXPONENT, 186 5 000108 437 c PRECISION, RANGE, HUGE, TINY, and EPSILON return scalar values 186 5 000108 438 c related to the parameters of the model associated with the types and 186 5 000108 439 c kind type parameters of the arguments. The values of the arguments to 186 5 000108 440 c these functions need not be defined, pointer arguments may have 186 5 000108 441 c undefined or disassociated association status, and array arguments 186 5 000108 442 c need not be allocated." 186 7 000159 754 a May undefined expressions be used as arguments to INQUIRY functions 186 7 000159 754 b X3J3 consideration in progress 186 7 000159 754 c 3. In section 13.7.2 Numeric Inquiry Functions [186:7-8] 186 7 000159 755 c replace the last sentence "The value of ...." 186 7 000159 756 c 186 7 000159 757 c with "If the argument to these functions consists of a single primary 186 7 000159 758 c (7.1.1.1) that is a variable name then that variable need not be defined, 186 7 000159 759 c if a pointer it may be disassociated, and if allocatable need not be 186 7 000159 760 c allocated." 187 12 000159 762 a May undefined expressions be used as arguments to INQUIRY functions 187 12 000159 762 b X3J3 consideration in progress 187 12 000159 762 c 4. In section 13.8.5 Array Inquiry Functions [187:12] 187 12 000159 763 c replace the second paragraph "The values of ..." 187 12 000159 764 c 187 12 000159 765 c with "If the argument to these functions consists of a single primary 187 12 000159 766 c (7.1.1.1) that is a variable name then that variable need not be defined." 188 12 000058 1266 a Ambiguous use of "keyword" 188 12 000058 1266 b X3J3 approved; ready for WG5 188 12 000058 1266 c 12. Page 188, section 13.10, first paragraph, first two lines [188:12-13] 188 12 000058 1267 c 188 12 000058 1268 c change "keyword" to "argument keyword" and 188 12 000058 1269 c change "keywords" to "argument keywords" 198 33 000109 3270 a Intrinsic function ASSOCIATED 198 33 000109 3270 b WG5 approved; ready for SC22 198 33 000109 3270 c In 13.13.13 in the specification of the result type, add "scalar" after 198 33 000109 3271 c "default logical". [198:33] 198 37 000100 62 a ASSOCIATED intrinsic and zero-sized objects 198 37 000100 62 b Returned by WG5 for X3J3 reconsideration 198 37 000100 62 c 1. Section 13.13.13 Case (ii) [198:37], replace by 198 37 000100 63 c 198 37 000100 64 c If TARGET is present and is a nonzero-sized target, the result is 198 37 000100 65 c true if POINTER is currently associated with TARGET. If TARGET is 198 37 000100 66 c zero sized, but has the same type, type parameters, rank, and shape 198 37 000100 67 c as POINTER, the result is undefined. Otherwise, the result is false. 199 1 000100 69 a ASSOCIATED intrinsic and zero-sized objects 199 1 000100 69 b Returned by WG5 for X3J3 reconsideration 199 1 000100 69 c 2. Section 13.13.13 Case (iii) [199:1], replace by 199 1 000100 70 c 199 1 000100 71 c If TARGET is present and is a pointer, the result is true if both POINTER 199 1 000100 72 c and TARGET are currently associated with the same nonzero-sized target. 199 1 000100 73 c If the targets are zero sized and have the same type, type parameters, 199 1 000100 74 c rank, and shape, the result is undefined. Otherwise the result is false. 199 1 000100 75 c The result is also false if either POINTER or TARGET is disassociated. 203 23 00000a 48 a Minor edits and corrections for Technical Corrigendum #1 203 23 00000a 48 b WG5 approved; ready for SC22 203 23 00000a 48 c 5. 13.13.25, Result Value, Case (ii), at beginning of the third line 203 23 00000a 49 c [203:23]; Change "1,sh" to "sh,1". 205 7 000171 1357 a Equivalence of DBLE(A) and REAL(A,KIND(0.0D0)) Intrinsics 205 7 000171 1357 b X3J3 consideration in progress 205 7 000171 1357 c In 13.13.27 DBLE, replace the text of the 'Result Value' section 205 7 000171 1358 c with: 205 7 000171 1359 c The result has the value REAL (A, KIND (0.0D0) ). [205:7-11] 210 23 00000c 52 a Minor edits and corrections 210 23 00000c 52 b X3J3 approved; ready for WG5 210 23 00000c 52 c 6. In 13.13.42 IBITS, Result value, 210 23 00000c 53 c 210 23 00000c 54 c change '.... bit POS right-adjusted' 210 23 00000c 55 c to '.... bit POS, right-adjusted' [210:23] 210 23 00000c 56 c 210 23 00000c 57 c Rationale: it is the result, not POS, that is right-adjusted. 214 22 000124 950 a Result of LBOUND for assumed-size arrays 214 22 000124 950 b X3J3 approved; ready for WG5 214 22 000124 950 c In section 13.13.52 replace the text of case (i) [214:22-25] with: 214 22 000124 951 c 214 22 000124 952 c "For an array section or for an array expression other than a whole 214 22 000124 953 c array or array structure component, LBOUND(ARRAY,DIM) has the value 214 22 000124 954 c 1. For a whole array or array structure component, LBOUND(ARRAY,DIM) 214 22 000124 955 c has the value: 214 22 000124 956 c (a) equal to the lower bound for subscript DIM of ARRAY if dimension 214 22 000124 957 c DIM of ARRAY does not have size zero or if the upper bound for 214 22 000124 958 c dimension DIM is *; or 214 22 000124 959 c (b) 1." 220 25 00000a 51 a Minor edits and corrections for Technical Corrigendum #1 220 25 00000a 51 b WG5 approved; ready for SC22 220 25 00000a 51 c 6. 13.13.66, Result Value, Case (iii) [220:25]; Change",[" to "[" 220 25 00000a 52 c (i.e. delete comma). 226 17 000120 3475 a PRESENT intrinsic and host association 226 17 000120 3475 b WG5 approved; ready for SC22 226 17 000120 3475 c Replace the description of Argument in 13.13.80 [226:17] with 226 17 000120 3476 c 226 17 000120 3477 c "A must be the name of an optional dummy argument that is accessible in 226 17 000120 3478 c the procedure in which the PRESENT function reference appears." 228 9 000176 1607 a Definition of RANDOM_SEED 228 9 000176 1607 b X3J3 consideration in progress 228 9 000176 1607 c 1. In 13.13.84, RANDOM_SEED, PUT argument, replace the last sentence 228 9 000176 1608 c (beginning "It is used by the processor ..." with [228:9]: 228 9 000176 1609 c 228 9 000176 1610 c It is used in a processor-dependent manner to compute the seed value. 228 9 000176 1611 c It is not required that an immediately following 228 9 000176 1612 c "CALL RANDOM_SEED (GET=aseed)" assign a physical representation 228 9 000176 1613 c to "aseed" identical to the physical representation of the value 228 9 000176 1614 c specified for PUT. 228 11 000176 1616 a Definition of RANDOM_SEED 228 11 000176 1616 b X3J3 consideration in progress 228 11 000176 1616 c 2. In 13.13.84, RANDOM_SEED, GET argument, replace the last sentence 228 11 000176 1617 c (beginning "It is set by the processor ...") with [228:11-12]: 228 11 000176 1618 c 228 11 000176 1619 c It is assigned the physical representation of the seed value in a 228 11 000176 1620 c processor-dependent mannor. 234 6 000064 2348 a SPACING result for 0.0 234 6 000064 2348 b WG5 approved; ready for SC22 234 6 000064 2348 c In section 13.13.100, after "Result Value." 234 6 000064 2349 c change "The" 234 6 000064 2350 c to "If X is not zero, the". 234 6 000064 2351 c In the same section, 234 6 000064 2352 c change "; otherwise " 234 6 000064 2353 c to ". Otherwise". [234:6] 234 20 000174 1494 a Consistent definition of NCOPIES 234 20 000174 1494 b X3J3 consideration in progress 234 20 000174 1494 c 1. In 13.13.101, to definition of NCOPIES [234:20] add: 234 20 000174 1495 c 234 20 000174 1496 c Its value must not be negative. 234 23 000174 1498 a Consistent definition of NCOPIES 234 23 000174 1498 b X3J3 consideration in progress 234 23 000174 1498 c 2. In 12.13.101 [234:23-25] 234 23 000174 1499 c 234 23 000174 1500 c Replace all occurances of: MAX(NCOPIES,0) 234 23 000174 1501 c with: NCOPIES 236 11 000132 1594 a SYSTEM_CLOCK intrinsic conformance requirements 236 11 000132 1594 b X3J3 approved; ready for WG5 236 11 000132 1594 c In section 13.13.104, SYSTEM_CLOCK, change the text for COUNT_RATE 236 11 000132 1595 c from 'the number' 236 11 000132 1596 c to 'a processor-dependent approximation to the number' [236:11] 242 28 000083 1999 a Extending generic intrinsic procedures 242 28 000083 1999 b X3J3 consideration in progress 242 28 000083 1999 c In section 14.1.2.3 add after the second sentence [242:28]: 242 28 000083 2000 c 242 28 000083 2001 c "If a generic interface has the same name as an accessible generic intrinsic 242 28 000083 2002 c procedure and the scoping unit either contains an INTRINSIC attribute 242 28 000083 2003 c specification for that name or accesses that generic intrinsic procedure 242 28 000083 2004 c with that name by use association, the generic interface extends the 242 28 000083 2005 c generic intrinsic procedure." 245 3 00000c 43 a Minor edits and corrections 245 3 00000c 43 b X3J3 approved; ready for WG5 245 3 00000c 43 c 5. Page 245, section 14.1.2.5, in the second sentence [245:3] 245 3 00000c 44 c 245 3 00000c 45 c change 'It' 245 3 00000c 46 c to 'Outside the type definition, it'. 245 3 00000c 47 c 245 3 00000c 48 c Reason: a component name appears in the derived type definition 245 3 00000c 49 c as well as possibly appearing in a component of a 245 3 00000c 50 c structure of that type. 245 14 000170 1318 a Argument Keywords and Intrinsic Procedures 245 14 000170 1318 b X3J3 approved; ready for WG5 245 14 000170 1318 c In section 14.1.2.6 add a new paragraph after the current 245 14 000170 1319 c paragraph. [245:14+] 245 14 000170 1320 c 245 14 000170 1321 c "A dummy argument name in an intrinsic procedure has a scope as an 245 14 000170 1322 c argument keyword of the scoping unit making reference to it. 245 14 000170 1323 c As an argument keyword, it may appear only in a procedure reference 245 14 000170 1324 c for the procedure of which it is a dummy argument." 245 23 000031 1157 a Overloaded implied-DO variable names 245 23 000031 1157 b WG5 approved; ready for SC22 245 23 000031 1157 c Replace the last paragraph of section 14.1.3 with the following two 245 23 000031 1158 c paragraphs: [245:23] 245 23 000031 1159 c 245 23 000031 1160 c Except for a common block name or a scalar variable name, a name that 245 23 000031 1161 c identifies a global entity or local entity of class 1 (14.1.2) 245 23 000031 1162 c accessible in the scoping unit of a statement must not be the name of 245 23 000031 1163 c a statement entity of that statement. Within the scope of a 245 23 000031 1164 c statement entity, another statement entity must not have the same name. 245 23 000031 1165 c 245 23 000031 1166 c If the name of a global or local entity accessible in the scoping unit of 245 23 000031 1167 c a statement is the same as the name of a statement entity in that 245 23 000031 1168 c statement, the name is interpreted within the scope of the statement 245 23 000031 1169 c entity as that of the statement entity. Elsewhere in the scoping unit, 245 23 000031 1170 c including parts of the statement outside the scope of the statement 245 23 000031 1171 c entity, the name is interpreted as that of the global or local entity. 247 2 000068 2622 a Pointer association status 247 2 000068 2622 b WG5 approved; ready for SC22 247 2 000068 2622 c 1. In section 14.6.2.1, item (3) subitem (c), delete "or" [247:2] 247 4 000068 2624 a Pointer association status 247 4 000068 2624 b WG5 approved; ready for SC22 247 4 000068 2624 c 2. The reference to section 6.3.3.2 in 14.6.2.1 (3) (d) is misleading. 247 4 000068 2625 c In section 14.6.2.1, item (3) subitem (d), remove "6.3.3.2," 247 4 000068 2626 c and change the period at the end to ", or" [247:4]. 247 4 000068 2628 a Pointer association status 247 4 000068 2628 b WG5 approved; ready for SC22 247 4 000068 2628 c 3. The list in section 14.6.2.1, item (3), of ways that pointer 247 4 000068 2629 c association status can become undefined is incomplete. 247 4 000068 2630 c In section 14.6.2.1, item (3) add a new subitem as follows: [247:4] 247 4 000068 2631 c 247 4 000068 2632 c (e) After the execution of a RETURN or END statement in a procedure 247 4 000068 2633 c where the pointer was either declared or, with the exceptions 247 4 000068 2634 c described in 6.3.3.2, accessed. 248 15 000154 342 a EQUIVALENCE and zero-sized sequences 248 15 000154 342 b X3J3 consideration in progress 248 15 000154 342 c In section 14.6.3.2 [248:15], after the last sentence in the second 248 15 000154 343 c paragraph, add "Two zero-sized subobjects of the same object are the same zero 248 15 000154 344 c sized storage sequence.". 248 40 000126 1058 a Character Entry statements and Partial Association 248 40 000126 1058 b X3J3 approved; ready for WG5 248 40 000126 1058 c In section 14.6.3.3 in the sentence (last two lines of page 248) 248 40 000126 1059 c [248:40-41] "For character entities, partial association may occur only through 248 40 000126 1060 c argument association, or the use of COMMON, EQUIVALENCE, or ENTRY statements." 248 40 000126 1061 c 248 40 000126 1062 c change "COMMON, EQUIVALENCE, or ENTRY" 248 40 000126 1063 c to "COMMON or EQUIVALENCE" 250 24 00000b 22 a Minor edits and corrections for Technical Corrigendum #2 250 24 00000b 22 b X3J3 approved; ready for WG5 250 24 00000b 22 c 4. Page 250, section 14.7.5, item (8) 250 24 00000b 23 c change 'input/output IOSTAT= specifier' 250 24 00000b 24 c to 'IOSTAT= specifier' 250 24 00000b 25 c Reason: 'input/output' is redundant. [250:24] 251 43 000150 66 a Undefinition of implied-DO variables in I/O statements 251 43 000150 66 b X3J3 approved; ready for WG5 251 43 000150 66 c 3. Section 14.7.6, item (6) [251:43-45], 251 43 000150 67 c change 251 43 000150 68 c input/output statement, some or all of the implied-DO variables may 251 43 000150 69 c become 251 43 000150 70 c to 251 43 000150 71 c input/output statement and the statement contains any implied-DOs, 251 43 000150 72 c all of the implied-DO variables in the statement become 255 27 00000a 54 a Minor edits and corrections for Technical Corrigendum #1 255 27 00000a 54 b WG5 approved; ready for SC22 255 27 00000a 54 c 7. Annex A, conformable [255:27]; Change "2.4.7" to "2.4.5". 255 38 00000a 56 a Minor edits and corrections for Technical Corrigendum #1 255 38 00000a 56 b WG5 approved; ready for SC22 255 38 00000a 56 c 8. Annex A, constant [255:38]; Change "2.4.4" to "2.4.3.1.2". 256 10 000096 2659 a Definition of "Declaration" 256 10 000096 2659 b X3J3 consideration in progress 256 10 000096 2659 c 1. In Annex A, add to page 256 after "datum" [256:10+] 256 10 000096 2660 c 256 10 000096 2661 c Declaration(2.5.3): The specification of for various program 256 10 000096 2662 c , Often this involves specifying the of a 256 10 000096 2663 c or specifing the of a ." 256 10 000096 2664 c 256 23 00000a 58 a Minor edits and corrections for Technical Corrigendum #1 256 23 00000a 58 b WG5 approved; ready for SC22 256 23 00000a 58 c 9. Annex A, derived type [256:23]; Change "2," to "2)". 256 38 000077 1606 a Miscellaneous questions 256 38 000077 1606 b X3J3 approved; ready for WG5 256 38 000077 1606 c 1. In Annex A, in the entry for "entity", 256 38 000077 1607 c replace "a named variable, an expression, a component of a structure, a named 256 38 000077 1608 c constant" 256 38 000077 1609 c with "a data entity". [256:38-39] 257 8 00000a 60 a Minor edits and corrections for Technical Corrigendum #1 257 8 00000a 60 b WG5 approved; ready for SC22 257 8 00000a 60 c 10. Annex A, extent [257:8]; Change "2.4.7" to " 2.4.5". 257 29 00000b 18 a Minor edits and corrections for Technical Corrigendum #2 257 29 00000b 18 b X3J3 approved; ready for WG5 257 29 00000b 18 c 2. Annex A, host association [257:29]; Change "11.2.2" to "12.1.2.2.1". 258 19 00000a 62 a Minor edits and corrections for Technical Corrigendum #1 258 19 00000a 62 b WG5 approved; ready for SC22 258 19 00000a 62 c 11. Annex A, literal constant [258:19]; Change "2.4.4" to "2.4.3.1.2". 258 22 00000a 64 a Minor edits and corrections for Technical Corrigendum #1 258 22 00000a 64 b WG5 approved; ready for SC22 258 22 00000a 64 c 12. Annex A, main program [258:22]; Change "2," to "2)". 258 22 000077 1611 a Miscellaneous questions 258 22 000077 1611 b X3J3 approved; ready for WG5 258 22 000077 1611 c 2. In Annex A, in the entry for "main program", 258 22 000077 1612 c replace "subprogram" 258 22 000077 1613 c with "external subprogram" [258:22] 258 25 00000a 66 a Minor edits and corrections for Technical Corrigendum #1 258 25 00000a 66 b WG5 approved; ready for SC22 258 25 00000a 66 c 13. Annex A, module [258:25]; Change "4," to "4)". 258 34 00000a 68 a Minor edits and corrections for Technical Corrigendum #1 258 34 00000a 68 b WG5 approved; ready for SC22 258 34 00000a 68 c 14. Annex A, named constant [258:34]; Change "2.4.4" to "2.4.3.1.2". 259 19 00000a 70 a Minor edits and corrections for Technical Corrigendum #1 259 19 00000a 70 b WG5 approved; ready for SC22 259 19 00000a 70 c 15. Annex A, procedure [259:19]; Change "3," to "3)". 259 31 00000a 72 a Minor edits and corrections for Technical Corrigendum #1 259 31 00000a 72 b WG5 approved; ready for SC22 259 31 00000a 72 c 16. Annex A, rank [259:31]; Change "2.4.7" to "2.4.5". 260 12 00000a 74 a Minor edits and corrections for Technical Corrigendum #1 260 12 00000a 74 b WG5 approved; ready for SC22 260 12 00000a 74 c 17. Annex A, shape [ 260:12]; Change "2.4.7" to "2.4.5". 260 14 00000a 76 a Minor edits and corrections for Technical Corrigendum #1 260 14 00000a 76 b WG5 approved; ready for SC22 260 14 00000a 76 c 18. Annex A, size [260:14]; Change "2.4.7" to "2.4.5". 260 14 000096 2666 a Definition of "Declaration" 260 14 000096 2666 b X3J3 consideration in progress 260 14 000096 2666 c 2. In Annex A, add to page 260 after "size" [260:14+] 260 14 000096 2667 c 260 14 000096 2668 c Specification: The assignment of attributes and properties to names. 260 35 00000a 78 a Minor edits and corrections for Technical Corrigendum #1 260 35 00000a 78 b WG5 approved; ready for SC22 260 35 00000a 78 c 19. Annex A, subobject [260:35]; Change "2.4.3.2" to "2.4.3.1". 261 9 00000a 80 a Minor edits and corrections for Technical Corrigendum #1 261 9 00000a 80 b WG5 approved; ready for SC22 261 9 00000a 80 c 20. Annex A, target [261:9]; Change "specified in a" to "specified in 261 9 00000a 81 c a TARGET statement or". 261 30 00000a 83 a Minor edits and corrections for Technical Corrigendum #1 261 30 00000a 83 b WG5 approved; ready for SC22 261 30 00000a 83 c 21. Annex A, variable [261:30]; Change "2.4.5" to "2.4.3.1.1". 269 21 000041 1012 a Procedure with target dummy argument requires explicit interface 269 21 000041 1012 b X3J3 consideration in progress 269 21 000041 1012 c Section C.5.3, second sentence, change "solely" to "primarily". [269:21] 273 14 00000b 20 a Minor edits and corrections for Technical Corrigendum #2 273 14 00000b 20 b X3J3 approved; ready for WG5 273 14 00000b 20 c 3. Annex C, first example [273:14]; change "ENDTYPE" to "END TYPE". 286 16 000153 217 a Defined Operations, dummy arguments INTENT(IN) 286 16 000153 217 b X3J3 approved; ready for WG5 286 16 000153 217 c 1. Section C.11.4, in function ELEMENT [286:16,17], change 286 16 000153 218 c INTEGER X 286 16 000153 219 c to 286 16 000153 220 c INTEGER, INTENT(IN) :: X 286 16 000153 221 c and change 286 16 000153 222 c TYPE (SET) A 286 16 000153 223 c to 286 16 000153 224 c TYPE (SET), INTENT(IN) :: A 286 21 000153 226 a Defined Operations, dummy arguments INTENT(IN) 286 21 000153 226 b X3J3 approved; ready for WG5 286 21 000153 226 c 2. Section C.11.4, in function UNION [286:21], change 286 21 000153 227 c TYPE (SET) A, B, UNION 286 21 000153 228 c to 286 21 000153 229 c TYPE (SET) UNION 286 21 000153 230 c TYPE (SET), INTENT(IN) :: A, B 286 37 000153 232 a Defined Operations, dummy arguments INTENT(IN) 286 37 000153 232 b X3J3 approved; ready for WG5 286 37 000153 232 c 3. Section C.11.4, in function DIFFERENCE [286:37], change 286 37 000153 233 c TYPE (SET) A, B, DIFFERENCE 286 37 000153 234 c to 286 37 000153 235 c TYPE (SET) DIFFERENCE 286 37 000153 236 c TYPE (SET), INTENT(IN) :: A, B 287 2 000153 238 a Defined Operations, dummy arguments INTENT(IN) 287 2 000153 238 b X3J3 approved; ready for WG5 287 2 000153 238 c 4. Section C.11.4, in function INTERSECTION [287:2], change 287 2 000153 239 c TYPE (SET) A, B, INTERSECTION 287 2 000153 240 c to 287 2 000153 241 c TYPE (SET) INTERSECTION 287 2 000153 242 c TYPE (SET), INTENT(IN) :: A, B 287 5 000153 244 a Defined Operations, dummy arguments INTENT(IN) 287 5 000153 244 b X3J3 approved; ready for WG5 287 5 000153 244 c 5. Section C.11.4, in function SUBSET [287:5], change 287 5 000153 245 c TYPE (SET) A, B 287 5 000153 246 c to 287 5 000153 247 c TYPE (SET), INTENT(IN) :: A, B 363 37 000058 1271 a Ambiguous use of "keyword" 363 37 000058 1271 b X3J3 approved; ready for WG5 363 37 000058 1271 c 13. Page 363, delete the entry for "argument keywords 183" [363:37] 363 37 000058 1272 c rationale: odd to index both singular and plural. "Keyword", 363 37 000058 1273 c and "statement keyword" are indexed to page 16, as is the remaining 363 37 000058 1274 c entry for "argument keyword". 368 13 000058 1276 a Ambiguous use of "keyword" 368 13 000058 1276 b X3J3 approved; ready for WG5 368 13 000058 1276 c 14. Annex F, delete the entry "positional arguments" [368:13]