PC File: 94-006-3.edt Archive: 94-006r3.edits -------------------------------------------------------------------------------- xvi 1 00000a 28 a Minor edits and corrections for Technical Corrigendum #1 xvi 1 00000a 28 b Published xvi 1 00000a 28 c 1. Introduction, Overview, Data Concepts, last sentence [xvi:1-2]; xvi 1 00000a 29 c Delete the sentence "The section concludes ... names." 2 4 000135 1817 a INTENT(IN) conformance 2 4 000135 1817 b X3J3 consideration in progress 2 4 000135 1817 c 1. Section 1.4 second paragraph, first sentence [2:4] 2 4 000135 1818 c change 'uses' 2 4 000135 1819 c to 'contains' 2 39 000135 1821 a INTENT(IN) conformance 2 39 000135 1821 b X3J3 consideration in progress 2 39 000135 1821 c 2. Section 1.4 sixth paragraph, first sentence [2:39] 2 39 000135 1822 c change 'use' 2 39 000135 1823 c to 'contain' 2 42 000146 2686 a Conformance 2 42 000146 2686 b X3J3 consideration in progress 2 42 000146 2686 c 1. In section 1.4, change the paragraph beginning "Note that" so that 2 42 000146 2687 c added data types are described in a manner parallel to added intrinsic 2 42 000146 2688 c procedures in the prior paragraph. [2:42] 2 42 000146 2689 c 2 42 000146 2690 c change "a nonstandard data type" 2 42 000146 2691 c to "additional intrinsic data types" 3 32 000061 2235 a G edit descriptor with "d" = 0 3 32 000061 2235 b Published 3 32 000061 2235 c 3. In section 1.4.1, add item (5) as follows: [3:32] 3 32 000061 2236 c 3 32 000061 2237 c (5) A value of 0 for a list item in a formatted output statement 3 32 000061 2238 c will be formatted in a different form for some G edit 3 32 000061 2239 c descriptors. In addition, the Fortran 90 standard specifies how 3 32 000061 2240 c rounding of values will affect the output field form, but 3 32 000061 2241 c FORTRAN 77 did not address this issue: therefore, some 3 32 000061 2242 c FORTRAN 77 processors may produce a different output form than 3 32 000061 2243 c Fortran 90 processors for certain combinations of values and G 3 32 000061 2244 c edit descriptors. 3 32 000139 2092 a INTRINSIC, EXTERNAL attribute questions 3 32 000139 2092 b X3J3 consideration in progress 3 32 000139 2092 c 4. Section 1.4.1 [3:32+] 3 32 000139 2093 c 3 32 000139 2094 c Add (6) 'FORTRAN 77 permitted the specification of a type for an 3 32 000139 2095 c intrinsic function even when there was no function defined 3 32 000139 2096 c for that type. For example: 3 32 000139 2097 c INTRINSIC SIN 3 32 000139 2098 c LOGICAL SIN 3 32 000139 2099 c This International Standard specifies (5.1) that a type 3 32 000139 2100 c declaration for an intrinsic function may only confirm the type 3 32 000139 2101 c of an existing function. Thus a standard-conforming FORTRAN 77 3 32 000139 2102 c program specifying a type that is not defined for an intrinsic 3 32 000139 2103 c function does not conform to this International Standard. 5 9 000058 1301 a Ambiguous use of "keyword" 5 9 000058 1301 b Returned by WG5 for X3J3 reconsideration 5 9 000058 1301 c 1. Page 5, section 1.5.3, (3) [5:9] 5 9 000058 1302 c delete "keyword actual arguments and" 5 9 000058 1303 c rationale: these are not specifiers and -spec is not used with them. 8 8 000101 118 a Specification statements 8 8 000101 118 b X3J3 consideration in progress 8 8 000101 118 c 1. Section 2.1, R207 [8:8] change 'specification-stmt' to 'declaration-stmt' 8 29 000101 120 a Specification statements 8 29 000101 120 b X3J3 consideration in progress 8 29 000101 120 c 2. Section 2.1, R214 [8:29] change 'specification-stmt' to 'declaration-stmt' 11 13 000101 122 a Specification statements 11 13 000101 122 b X3J3 consideration in progress 11 13 000101 122 c 3. Section 2.3.1, following 2nd paragraph [11:13+] insert new paragraph: 11 13 000101 123 c 11 13 000101 124 c Specification statements are all the statements that can appear in 11 13 000101 125 c the , except for the ENTRY and FORMAT statements. 11 13 000101 126 c 11 13 000101 127 c note to editor: "Specification statements", above, should be in bold. 11 30 000101 129 a Specification statements 11 30 000101 129 b X3J3 consideration in progress 11 30 000101 129 c 4. Figure 2.1, [11:30] change 'Specification' to 'Declaration' 12 31 000101 131 a Specification statements 12 31 000101 131 b X3J3 consideration in progress 12 31 000101 131 c 5. In note to Figure 2.1, [12:31] change 'Specification' to 'Declaration' 15 25 00000a 31 a Minor edits and corrections for Technical Corrigendum #1 15 25 00000a 31 b Published 15 25 00000a 31 c 2. 2.4.6, third sentence [15:25]; Change "of" to "or". 16 3 000058 1305 a Ambiguous use of "keyword" 16 3 000058 1305 b Returned by WG5 for X3J3 reconsideration 16 3 000058 1305 c 2. Page 16, section 2.5.2, first paragraph, first occurrence [16:3] 16 3 000058 1306 c change "statement keyword" 16 3 000058 1307 c --------- ------- 16 3 000058 1308 c to "statement keyword (often abbreviated to keyword)" 16 3 000058 1309 c --------- ------- ------- 16 3 000058 1310 c rationale: define "keyword", in a style similar to "object" 16 3 000058 1311 c in 2.4.3.1. 16 5 000058 1313 a Ambiguous use of "keyword" 16 5 000058 1313 b Returned by WG5 for X3J3 reconsideration 16 5 000058 1313 c 3. Page 16, section 2.5.2, first paragraph, end of [16:5] 16 5 000058 1314 c add "Keywords appear as upper-case words in the syntax rules 16 5 000058 1315 c in Sections 4 through 12". 16 6 000058 1317 a Ambiguous use of "keyword" 16 6 000058 1317 b Returned by WG5 for X3J3 reconsideration 16 6 000058 1317 c 4. Page 16, section 2.5.2, second paragraph, first sentence [16:6] 16 6 000058 1318 c change "name." to "name (see 12.4.1)." 16 35 000146 2693 a Conformance 16 35 000146 2693 b X3J3 consideration in progress 16 35 000146 2693 c 2. In section 2.5.7 [16:35-36] 16 35 000146 2694 c 16 35 000146 2695 c change "International Standard" 16 35 000146 2696 c to "International Standard or by the processor" 19 35 000058 1320 a Ambiguous use of "keyword" 19 35 000058 1320 b Returned by WG5 for X3J3 reconsideration 19 35 000058 1320 c 5. Page 19, section 3.2 [19:35] 19 35 000058 1321 c change "keywords" to "statement keywords (2.5.2)" 19 37 000058 1323 a Ambiguous use of "keyword" 19 37 000058 1323 b Returned by WG5 for X3J3 reconsideration 19 37 000058 1323 c 6. Page 19, section 3.2.1 [19:37-38] 19 37 000058 1324 c delete 19 37 000058 1325 c rationale: 2.5.2 is now the complete definition. 21 33 000130 1465 a Multiple statements on line with END statement 21 33 000130 1465 b WG5 approved; ready for SC22 21 33 000130 1465 c Replace the first sentence of 3.3 [21:33] with: 21 33 000130 1466 c 21 33 000130 1467 c A Fortran program unit is a sequence of one or more lines, 21 33 000130 1468 c organized as Fortran statements, comments, and INCLUDE lines. 22 6 000004 286 a Blanks in format specifications in free form source 22 6 000004 286 b X3J3 draft response 22 6 000004 286 c Section 3.3.1, second paragraph [22:6], 22 6 000004 287 c change "... character context." 22 6 000004 288 c to "... character context or in a format specification." 22 44 000121 818 a ";" As a Statement Separator 22 44 000121 818 b X3J3 consideration in progress 22 44 000121 818 c 1. Section 3.3.1.2 [22:44-45], change the first sentence to read as follows: 22 44 000121 819 c 22 44 000121 820 c "The character ``;'' terminates a statement, except when the ``;'' appears 22 44 000121 821 c in a character context or in a comment. This optional termination allows 22 44 000121 822 c another statement to begin following the ``;'' on the same line. A ``;'' 22 44 000121 823 c must not appear as the first nonblank character on a line." 23 1 000121 825 a ";" As a Statement Separator 23 1 000121 825 b X3J3 consideration in progress 23 1 000121 825 c 2. Section 3.3.1.2 [23:1-2], eliminate the last sentence of this section (it 23 1 000121 826 c becomes redundant with edit 1). 23 36 000121 828 a ";" As a Statement Separator 23 36 000121 828 b X3J3 consideration in progress 23 36 000121 828 c 3. Section 3.3.2.2 [23:36-37], change the first sentence to read as follows: 23 36 000121 829 c 23 36 000121 830 c "The character ``;'' terminates a statement, except when the ``;'' appears 23 36 000121 831 c in a character context or in a comment. This optional termination allows 23 36 000121 832 c another statement to begin following the ``;'' on the same line. A ``;'' 23 36 000121 833 c must not appear as the first nonblank character on a line." 23 39 000121 835 a ";" As a Statement Separator 23 39 000121 835 b X3J3 consideration in progress 23 39 000121 835 c 4. Section 3.3.2.2 [23:39-40], eliminate the last sentence of this section (it 23 39 000121 836 c becomes redundant with edit 3). 24 13 000044 1577 a END statement and fixed form source 24 13 000044 1577 b Published 24 13 000044 1577 c In 3.3.2.4 replace the text 24 13 000044 1578 c 24 13 000044 1579 c "and no other statement in the program unit may have an initial line that 24 13 000044 1580 c appears to be a program unit END statement" 24 13 000044 1581 c with 24 13 000044 1582 c ". A statement whose initial line appears to be a program unit END 24 13 000044 1583 c statement must not be continued." [24:13] 27 2 00000c 60 a Minor edits and corrections 27 2 00000c 60 b X3J3 approved; ready for WG5 27 2 00000c 60 c 7. In 4.3.1 Numeric Types 27 2 00000c 61 c 27 2 00000c 62 c delete the last sentence "In this standard..." [27:2-3] 27 2 00000c 63 c 27 2 00000c 64 c Rationale: this is a not quite accurate restatement of R306 in section 3.2.3. 27 2 00000c 65 c ("unsigned" is not defined for boz numeric constants) 33 12 000146 2698 a Conformance 33 12 000146 2698 b X3J3 consideration in progress 33 12 000146 2698 c 3. In section 4.4.1, change the fifth constraint following R424 to: [33:12-13] 33 12 000146 2699 c 33 12 000146 2700 c Constraint: A derived type must not be the same as the name 33 12 000146 2701 c of any intrinsic type defined in this standard nor the 33 12 000146 2702 c same as any other accessible derived type . 33 36 000015 479 a Error in fourth constraint for R429 33 36 000015 479 b Published 33 36 000015 479 c Replace the fourth constraint after R429 [33:36] with: 33 36 000015 480 c 33 36 000015 481 c The character length specified by the in a 33 36 000015 482 c or the in a 33 36 000015 483 c (5.1, 5.1.1.5) must be a constant specification expression (7.1.6.2). 38 3 000030 839 a Length of character literals in array constructors 38 3 000030 839 b Returned by WG5 for X3J3 reconsideration 38 3 000030 839 c 1. Delete the second constraint following R435. [38:3] 38 4 000030 841 a Length of character literals in array constructors 38 4 000030 841 b Returned by WG5 for X3J3 reconsideration 38 4 000030 841 c 2. Add the following paragraph after the constraints in 4.5. [38:4] 38 4 000030 842 c 38 4 000030 843 c Each expression in the must have 38 4 000030 844 c the same type and type parameters. 39 36 000066 2489 a Declaration of FUNCTION type 39 36 000066 2489 b Published 39 36 000066 2489 c 1. Change R504 "{()}" to "". 39 36 000066 2490 c [39:36] 40 12 000066 2492 a Declaration of FUNCTION type 40 12 000066 2492 b Published 40 12 000066 2492 c 2. Change "Constraint: An for a that 40 12 000066 2493 c does not have the POINTER attribute must be an 40 12 000066 2494 c " 40 12 000066 2495 c to "Constraint: An for an that 40 12 000066 2496 c is a function result that does not have the POINTER attribute 40 12 000066 2497 c must be an ". [40:12] 40 14 000066 2499 a Declaration of FUNCTION type 40 14 000066 2499 b Published 40 14 000066 2499 c 3. Delete the constraint "An for a that 40 14 000066 2500 c does have the POINTER attribute must be a ". [40:14] 40 24 000087 2298 a PARAMETER statements and SAVE statements 40 24 000087 2298 b Returned by WG5 for X3J3 reconsideration 40 24 000087 2298 c 1. Change the sixteenth constraint of section 5.1 to [40:24] 40 24 000087 2299 c 40 24 000087 2300 c The SAVE attribute must not be specified for an object that is in a common 40 24 000087 2301 c block, a dummy argument, a procedure, a function result, an automatic data 40 24 000087 2302 c object, or an object with the PARAMETER attribute. 40 35 000139 2082 a INTRINSIC, EXTERNAL attribute questions 40 35 000139 2082 b X3J3 consideration in progress 40 35 000139 2082 c 3. Section 5.1, second paragraph following the constraints [40:35-36] 40 35 000139 2083 c 40 35 000139 2084 c Replace 'An explicit type declaration statement is not required; 40 35 000139 2085 c however it is permitted. Specifying a type for a generic 40 35 000139 2086 c intrinsic function name in a ...' 40 35 000139 2087 c 40 35 000139 2088 c with 'An explicit type declaration statement confirming that type 40 35 000139 2089 c for either a specific or generic name is not required; however 40 35 000139 2090 c it is permitted. Such a ...' 40 38 000093 2752 a Scalar pointer function results 40 38 000093 2752 b X3J3 approved; ready for WG5 40 38 000093 2752 c 2. Insert the following paragraph after the second paragraph following 40 38 000093 2753 c the constraints in 5.1 [40:38+] 40 38 000093 2754 c 40 38 000093 2755 c A function result may be declared to have the POINTER attribute. 40 39 000145 2630 a Expressions in of a FUNCTION statement 40 39 000145 2630 b X3J3 consideration in progress 40 39 000145 2630 c Section 5.1, in the first sentence of the paragraph that starts 40 39 000145 2631 c "The (7.1.6.2)" [40:39-41], 40 39 000145 2632 c 40 39 000145 2633 c replace "in an interface body (12.3.2.1) or in the specification part of a 40 39 000145 2634 c subprogram" 40 39 000145 2635 c 40 39 000145 2636 c with "contained in an interface body (12.3.2.1), is contained in the 40 39 000145 2637 c specification part of a subprogram, or is in the of a 40 39 000145 2638 c FUNCTION statement (12.5.2.2)" 41 8 000113 607 a Ordering of array specification and initialization 41 8 000113 607 b WG5 approved; ready for SC22 41 8 000113 607 c Section 5.1, add the following to the end of the fifth paragraph 41 8 000113 608 c following the constraints [41:8]: 41 8 000113 609 c 41 8 000113 610 c "If the variable is an array, it must have its shape specified either in 41 8 000113 611 c the type declaration statement or a previous attribute specification 41 8 000113 612 c statement in the same scoping unit." 41 9 000087 2304 a PARAMETER statements and SAVE statements 41 9 000087 2304 b Returned by WG5 for X3J3 reconsideration 41 9 000087 2304 c 2. In section 5.1, change the first sentence of the next to last 41 9 000087 2305 c paragraph before the examples [41:9]: 41 9 000087 2306 c 41 9 000087 2307 c The presence of = implies that is a 41 9 000087 2308 c saved object, except for an in a named common block or an 41 9 000087 2309 c with the PARAMETER attribute. 42 29 000016 508 a Character length specification 42 29 000016 508 b Published 42 29 000016 508 c Replace the text following the constraints for R508 [42:29] with: 42 29 000016 509 c 42 29 000016 510 c The in a CHARACTER and the * 42 29 000016 511 c in an or in a of a type definition 42 29 000016 512 c specify character length. The * in an or 42 29 000016 513 c a specifies an individual length and overrides the 42 29 000016 514 c length specified in the , if any. If a * 42 29 000016 515 c is not specified in an or a , the 42 29 000016 516 c or specified in the 42 29 000016 517 c is the character length. If the length is not 42 29 000016 518 c specified in a or a * , the length is 1. 43 5 000070 1454 a Characteristics specified by interface bodies 43 5 000070 1454 b X3J3 consideration in progress 43 5 000070 1454 c In section 5.1.1.5 item (3), add to the end [43:5]: 43 5 000070 1455 c 43 5 000070 1456 c "Note that the interface for such a function cannot be specified in an 43 5 000070 1457 c interface body." 43 6 000172 1484 a Length specified for a character-valued statement function 43 6 000172 1484 b X3J3 approved; ready for WG5 43 6 000172 1484 c In 5.1.1.5 [43:6-7] change the paragraph following item (3) to: 43 6 000172 1485 c 43 6 000172 1486 c The length specified for a character-valued statement function 43 6 000172 1487 c or statement function dummy argument of type character must be a 43 6 000172 1488 c constant specification expression. 43 22 000032 1231 a Implicit declaration of a derived type 43 22 000032 1231 b Published 43 22 000032 1231 c 1. In the first paragraph of 5.1.1.7, 43 22 000032 1232 c change "is specified" 43 22 000032 1233 c to "is declared explicitly". [43:22] 43 23 000112 551 a Sequence derived type external functions 43 23 000112 551 b WG5 approved; ready for SC22 43 23 000112 551 c Add after the last sentence of the first paragraph of 5.1.1.7: [43:23] 43 23 000112 552 c 43 23 000112 553 c "If the data entity is a function result, the derived type can be specified 43 23 000112 554 c on the FUNCTION statement providing the derived type is defined within the 43 23 000112 555 c body of the function or is accessible there by use or host association." 46 30 000108 428 a Referencing disassociated pointers 46 30 000108 428 b WG5 approved; ready for SC22 46 30 000108 428 c 1. Replace the first two lines of the seventh paragraph of 5.1.2.4.3, 46 30 000108 429 c "The size, bounds, and shape of the target ... association status." 46 30 000108 430 c [46:30-33] with: 46 30 000108 431 c 46 30 000108 432 c "The size, bounds, and shape of the target of a disassociated array 46 30 000108 433 c pointer are undefined. No part of such an array may be referenced 46 30 000108 434 c or defined; however, the array may appear as an argument to an 46 30 000108 435 c intrinsic inquiry function that is inquiring about argument presence, 46 30 000108 436 c a property of the type or type parameters, or association status." 46 41 000039 1037 a Association of a pointer actual argument with a dummy argument 46 41 000039 1037 b WG5 approved; ready for SC22 46 41 000039 1037 c 1. Delete the penultimate (tenth) paragraph of 5.1.2.4.3, "A pointer 46 41 000039 1038 c dummy argument ... argument." [46:41-42] 46 43 000093 2750 a Scalar pointer function results 46 43 000093 2750 b X3J3 approved; ready for WG5 46 43 000093 2750 c 1. Delete the last paragraph of 5.1.2.4.3 [46:43]. 47 39 000087 2311 a PARAMETER statements and SAVE statements 47 39 000087 2311 b Returned by WG5 for X3J3 reconsideration 47 39 000087 2311 c 3. Remove the penultimate sentence of 5.1.2.5, "The SAVE attribute ... result, 47 39 000087 2312 c or an automatic data object." [47:39] 48 26 000139 2078 a INTRINSIC, EXTERNAL attribute questions 48 26 000139 2078 b X3J3 consideration in progress 48 26 000139 2078 c 1. Section 5.1.2.10 Replace 'object name' with '' [48:26] 48 30 000139 2080 a INTRINSIC, EXTERNAL attribute questions 48 30 000139 2080 b X3J3 consideration in progress 48 30 000139 2080 c 2. Section 5.1.2.11 Replace 'object name' with '' [48:30] 49 31 000143 2363 a Use association and functions/subroutines/intrinsics 49 31 000143 2363 b X3J3 consideration in progress 49 31 000143 2363 c Add at the end of the first paragraph of 5.2.3 [49:31]: 49 31 000143 2364 c 49 31 000143 2365 c "If a procedure is accessible from a module, then within the scoping unit of 49 31 000143 2366 c the module one of the following must be true: 49 31 000143 2367 c (1) if it is an intrinsic procedure, it must be given the INTRINSIC 49 31 000143 2368 c attribute or be used as an intrinsic procedure 49 31 000143 2369 c (2) the procedure must have an explicit interface 49 31 000143 2370 c (3) the procedure must be given the EXTERNAL attribute and if it is a 49 31 000143 2371 c function it must be explicitly declared in a type declaration 49 31 000143 2372 c statement. 50 9 000087 2314 a PARAMETER statements and SAVE statements 50 9 000087 2314 b Returned by WG5 for X3J3 reconsideration 50 9 000087 2314 c 4. Change the first constraint of section 5.2.4 to [50:9] 50 9 000087 2315 c 50 9 000087 2316 c An must not be the name of an object in a common block, a dummy 50 9 000087 2317 c argument name, a procedure name, a function result name, an automatic data 50 9 000087 2318 c object name, or the name of an object with the PARAMETER attribute. 52 20 000136 1883 a scalar-structure-component in data-implied-do 52 20 000136 1883 b X3J3 approved; ready for WG5 52 20 000136 1883 c In section 5.2.9, following the second constraint [52:20], insert the 52 20 000136 1884 c following constraint: 52 20 000136 1885 c 52 20 000136 1886 c Constraint: The must contain at least one 52 20 000136 1887 c that contains a . 52 25 000089 2430 a Errors in the DATA statement description 52 25 000089 2430 b WG5 approved; ready for SC22 52 25 000089 2430 c 1. Add a new constraint after the second constraint following R537: [52:25] 52 25 000089 2431 c 52 25 000089 2432 c If a DATA statement constant value is a named constant or a structure 52 25 000089 2433 c constructor, the named constant or derived type must have been declared 52 25 000089 2434 c previously in the scoping unit or made accessible by use or host association. 52 44 000137 1951 a array-element in data-implied-do 52 44 000137 1951 b X3J3 consideration in progress 52 44 000137 1951 c In section 5.2.9, following the last paragraph [52:44+], add the following text: 52 44 000137 1952 c 52 44 000137 1953 c The of a must appear in at least 52 44 000137 1954 c one of each and 52 44 000137 1955 c contained within the range of the 52 44 000137 1956 c . 52 44 000137 1957 c 52 44 000137 1958 c Example: 52 44 000137 1959 c 52 44 000137 1960 c INTEGER ARRAY_1(5,5), ARRAY_2(5), ARRAY_3(10) 52 44 000137 1961 c DATA ((ARRAY_1(I, J+1), I = 1, 5), ARRAY_2(J+1), J = 0, 4) ... 52 44 000137 1962 c DATA ((ARRAY_3(I + J*1), I = 1, 2), J = 3, 4) ... 52 44 000137 1963 c 52 44 000137 1964 c TYPE SMALL 52 44 000137 1965 c INTEGER I(2) 52 44 000137 1966 c REAL R 52 44 000137 1967 c END TYPE 52 44 000137 1968 c 52 44 000137 1969 c TYPE(SMALL) GROUP(3) 52 44 000137 1970 c 52 44 000137 1971 c DATA ((GROUP(J)%I(K), K = 1, 2), J = 1, 3) ... 52 44 000137 1972 c 52 44 000137 1973 c Since ARRAY_1 is within the range of both I and J, its subscript list must 52 44 000137 1974 c contain references to both I and J, but since ARRAY_2 is only within the range 52 44 000137 1975 c of J, its subscript list need only reference J. 52 44 000137 1976 c 52 44 000137 1977 c The second DATA statement demonstrates that the DATA implied-DO variables need 52 44 000137 1978 c not be referenced in separate subscript expressions. 52 44 000137 1979 c 52 44 000137 1980 c The third DATA statement demonstrates that the implied-DO variables can be 52 44 000137 1981 c referenced in separate subscript lists of the same designator. In this case, 52 44 000137 1982 c note too that both J and K must be referenced in the designator since it falls 52 44 000137 1983 c within the range of both implied-DO variables. 53 4 000089 2436 a Errors in the DATA statement description 53 4 000089 2436 b WG5 approved; ready for SC22 53 4 000089 2436 c 2. Delete the second sentence in the third paragraph following the 53 4 000089 2437 c constraints [53:4-5], "Each such value ...host association." 53 6 000089 2439 a Errors in the DATA statement description 53 6 000089 2439 b WG5 approved; ready for SC22 53 6 000089 2439 c 3. In the third sentence [53:6], 53 6 000089 2440 c replace "following constant" 53 6 000089 2441 c with "following constant value". 53 11 000089 2443 a Errors in the DATA statement description 53 11 000089 2443 b WG5 approved; ready for SC22 53 11 000089 2443 c 4. In the next paragraph, second sentence [53:11], 53 11 000089 2444 c change "constant" 53 11 000089 2445 c to "constant value". 53 17 000089 2447 a Errors in the DATA statement description 53 17 000089 2447 b WG5 approved; ready for SC22 53 17 000089 2447 c 5. In the following paragraph, last sentence [53:17], 53 17 000089 2448 c change "constant" 53 17 000089 2449 c to "constant value". 53 18 000089 2451 a Errors in the DATA statement description 53 18 000089 2451 b WG5 approved; ready for SC22 53 18 000089 2451 c 6. In the sixth paragraph [53:18-19], 53 18 000089 2452 c change "value of the constant" 53 18 000089 2453 c to "constant value" (twice) 53 43 000012 530 a Type of a named constant when there is implicit mapping 53 43 000012 530 b X3J3 approved; ready for WG5 53 43 000012 530 c 1. In section 5.2.10 change the second paragraph to: [53:43-47] 53 43 000012 531 c 53 43 000012 532 c "The named constant must have its type, type parameters, and shape 53 43 000012 533 c specified in a prior specification of the or 53 43 000012 534 c declared implicitly (5.3). If the named constant is typed by the implicit 53 43 000012 535 c typing rules, its appearance in any subsequent specification of the 53 43 000012 536 c must confirm this implied type and the values of any 53 43 000012 537 c implied type parameters." 54 30 000013 388 a Implicit mapping of an interface block 54 30 000013 388 b Published 54 30 000013 388 c 1. In Section 5.3 in the second paragraph after the constraints [54:30], 54 30 000013 389 c in the phrase: "the default is the mapping ...", after "default": 54 30 000013 390 c 54 30 000013 391 c add "for a program unit or an interface body is default integer if 54 30 000013 392 c the letter is I,J, ... , or N and default real otherwise, and the 54 30 000013 393 c default for an internal or module procedure". 54 30 000013 394 c 54 30 000013 395 c Delete "A program ... O-Z)" 54 35 000012 539 a Type of a named constant when there is implicit mapping 54 35 000012 539 b X3J3 approved; ready for WG5 54 35 000012 539 c 2. In section 5.3 in line 3 of the paragraph that starts with "Any data 54 35 000012 540 c entity that is" after 'not null.' and before the Corrigendum 1 54 35 000012 541 c addition [54:35], add: 54 35 000012 542 c 54 35 000012 543 c "The mapping for the first letter of the data entity must either 54 35 000012 544 c have been established by a prior IMPLICIT statement or be the 54 35 000012 545 c default mapping for the letter." 54 35 000032 1235 a Implicit declaration of a derived type 54 35 000032 1235 b Published 54 35 000032 1235 c 2. In paragraph 5 of 5.3 after "provided the mapping is not null.", 54 35 000032 1236 c insert the new sentence: "Note that the mapping can be to a derived 54 35 000032 1237 c type that is inaccessible in the local scope if the derived type is 54 35 000032 1238 c accessible to the host scope." [54:35] 55 2 000013 397 a Implicit mapping of an interface block 55 2 000013 397 b Published 55 2 000013 397 c 2. In the example in section 5.3 for FUNCTION FUN [55:2] in the interface 55 2 000013 398 c block the comment should be changed from: 55 2 000013 399 c 55 2 000013 400 c ! All data entities must 55 2 000013 401 c ! be declared explicitly 55 2 000013 402 c 55 2 000013 403 c to 55 2 000013 404 c 55 2 000013 405 c ! Not all entities need be 55 2 000013 406 c ! declared explicitly 55 3 000013 408 a Implicit mapping of an interface block 55 3 000013 408 b Published 55 3 000013 408 c 3. In the first example in section 5.3 [55:3], change "INTEGER FUN, I" 55 3 000013 409 c to be "INTEGER FUN". 56 13 000142 2292 a Namelist I/O 56 13 000142 2292 b X3J3 draft response 56 13 000142 2292 c 1. In section 5.4, add to the end of the second constraint [56:13] 56 13 000142 2293 c "or have private components" 56 22 000012 547 a Type of a named constant when there is implicit mapping 56 22 000012 547 b X3J3 approved; ready for WG5 56 22 000012 547 c 3. In section 5.4 in the penultimate paragraph [56:22-24]: 56 22 000012 548 c in line 3, delete "currently" 56 22 000012 549 c and in lines 4-5 replace "this implied type" 56 22 000012 550 c by "the implied type and type parameters". 57 17 000160 823 a Variables with the TARGET attribute in EQUIVALENCE groups 57 17 000160 823 b X3J3 approved; ready for WG5 57 17 000160 823 c After the sixth constraint of section 5.5.1 add [57:17+] 57 17 000160 824 c 57 17 000160 825 c Constraint: An must not have the TARGET attribute. 59 11 000071 1522 a Use association and common block names 59 11 000071 1522 b WG5 approved; ready for SC22 59 11 000071 1522 c 1. In the first sentence of 5.5.2.1 after "For each common block", 59 11 000071 1523 c insert "in a scoping unit". [59:11] 59 19 000071 1525 a Use association and common block names 59 19 000071 1525 b WG5 approved; ready for SC22 59 19 000071 1525 c 2. At the end of 5.5.2.1, add the following paragraph: 59 19 000071 1526 c 59 19 000071 1527 c "Only COMMON statements and EQUIVALENCE statements appearing in the 59 19 000071 1528 c scoping unit contribute to common block storage sequences formed in that 59 19 000071 1529 c unit. Variables, in common blocks, made accessible by use association or 59 19 000071 1530 c host association do not contribute." [59:19] 59 30 000071 1532 a Use association and common block names 59 30 000071 1532 b WG5 approved; ready for SC22 59 30 000071 1532 c 3. At the end of the first paragraph of 5.5.2.3, add the following sentence: 59 30 000071 1533 c 59 30 000071 1534 c "Use association or host association may cause these associated objects 59 30 000071 1535 c to be accessible in the same scoping unit." [59:30] 60 19 000071 1537 a Use association and common block names 60 19 000071 1537 b WG5 approved; ready for SC22 60 19 000071 1537 c 4. Delete the last two sentences in 5.5.2.5. [60:19] 63 30 000166 1216 a Array named constant is a constant expression? 63 30 000166 1216 b X3J3 approved; ready for WG5 63 30 000166 1216 c Section 6.2.1, second paragraph: 63 30 000166 1217 c change "the name of a constant expression (5.1.2.1 and 5.2.10)" 63 30 000166 1218 c to "a named constant (5.1.2.1 and 5.2.10)" [63:30-31] 76 22 000163 1020 a Pointer assignment of a disassociated pointer 76 22 000163 1020 b X3J3 approved; ready for WG5 76 22 000163 1020 c In the final sentence of section 7.1.4.1, insert before the terminating 76 22 000163 1021 c period 76 22 000163 1022 c 76 22 000163 1023 c ", or as the target in a pointer assignment statement." [76:22] 77 24 000097 2847 a Specification expression 77 24 000097 2847 b WG5 approved; ready for SC22 77 24 000097 2847 c 1. Replace 7.1.6.1 (6), in the first list, with the following: [77:24-28] 77 24 000097 2848 c 77 24 000097 2849 c (6) A reference to an intrinsic function which is: 77 24 000097 2850 c a) an array inquiry function (13.10.15) other than ALLOCATED, 77 24 000097 2851 c b) the bit inquiry function BIT_SIZE, 77 24 000097 2852 c c) the character inquiry function LEN, 77 24 000097 2853 c d) the kind inquiry function KIND, or 77 24 000097 2854 c e) a numeric inquiry function (13.10.8) 77 24 000097 2855 c and where each argument of the function is 77 24 000097 2856 c a) a constant expression, or 77 24 000097 2857 c b) a variable whose properties inquired about are not: 77 24 000097 2858 c 1) assumed 77 24 000097 2859 c 2) defined by an expression that is not a constant expression 77 24 000097 2860 c or 77 24 000097 2861 c 3) definable by an ALLOCATE or POINTER assignment statement 77 27 000047 1687 a Automatic data object in initialization expressions 77 27 000047 1687 b Published 77 27 000047 1687 c 1. Section 7.1.6.1, page 77, item (6) 77 27 000047 1688 c change "not assumed or" 77 27 000047 1689 c to "not assumed, are not defined by an expression that is not 77 27 000047 1690 c a constant expression, and are not" [77:27] 77 39 000129 1403 a Array constructors in initialization expressions 77 39 000129 1403 b X3J3 draft response 77 39 000129 1403 c 1. In section 7.1.6.1, in the second list, in item 2 [77:39], 77 39 000129 1404 c 77 39 000129 1405 c change: "either initialization expressions or implied-DO variables" 77 39 000129 1406 c to: "initialization expressions" 78 6 000097 2863 a Specification expression 78 6 000097 2863 b WG5 approved; ready for SC22 78 6 000097 2863 c 2. Replace 7.1.6.1 (6), in the second list with the following: [78:6-10] 78 6 000097 2864 c 78 6 000097 2865 c (6) A reference to an intrinsic function which is: 78 6 000097 2866 c a) an array inquiry function (13.10.15) other than ALLOCATED, 78 6 000097 2867 c b) the bit inquiry function BIT_SIZE, 78 6 000097 2868 c c) the character inquiry function LEN, 78 6 000097 2869 c d) the kind inquiry function KIND, or 78 6 000097 2870 c e) a numeric inquiry function (13.10.8) 78 6 000097 2871 c and where each argument of the function is 78 6 000097 2872 c a) an initialization expression, or 78 6 000097 2873 c b) a variable whose properties inquired about are not: 78 6 000097 2874 c 1) assumed 78 6 000097 2875 c 2) defined by an expression that is not a 78 6 000097 2876 c initialization expression or 78 6 000097 2877 c 3) definable by an ALLOCATE or POINTER assignment 78 6 000097 2878 c statement 78 9 000047 1692 a Automatic data object in initialization expressions 78 9 000047 1692 b Published 78 9 000047 1692 c 2. Section 7.1.6.1, page 78, item (6) 78 9 000047 1693 c change "not assumed or" 78 9 000047 1694 c to "not assumed, are not defined by an expression that is not 78 9 000047 1695 c an initialization expression, and are not" [78:9] 78 10 000129 1408 a Array constructors in initialization expressions 78 10 000129 1408 b X3J3 draft response 78 10 000129 1408 c 2. In section 7.1.6.1, in the second list, in item 6 [78:10], delete the 78 10 000129 1409 c last "or" 78 11 000129 1411 a Array constructors in initialization expressions 78 11 000129 1411 b X3J3 draft response 78 11 000129 1411 c 3. In section 7.1.6.1, in the second list, in item 7 [78:11], 78 11 000129 1412 c 78 11 000129 1413 c change: "." 78 11 000129 1414 c to: ", or" 78 11 000129 1416 a Array constructors in initialization expressions 78 11 000129 1416 b X3J3 draft response 78 11 000129 1416 c 4. In section 7.1.6.1, in the second list, add item 8 [78:11+]: 78 11 000129 1417 c 78 11 000129 1418 c "(8) An implied-DO variable where the bounds and strides of the 78 11 000129 1419 c corresponding implied-DO are initialization expressions." 78 18 000162 957 a Pointer expression "(i)" 78 18 000162 957 b X3J3 draft response 78 18 000162 957 c 7.1.4.1: Change the first sentence of the last paragraph to: [78:18-19] 78 18 000162 958 c 78 18 000162 959 c "If a pointer appears as one of the following, the associated target 78 18 000162 960 c object is referenced: 78 18 000162 961 c (1) A primary in an intrinsic operation, 78 18 000162 962 c (2) A defined operation in which it corresponds to a nonpointer dummy 78 18 000162 963 c argument, 78 18 000162 964 c (3) As the of a parenthesized primary, or 78 18 000162 965 c (4) As the only primary on the right hand side of an intrinsic assignment 78 18 000162 966 c statement." 79 11 000097 2880 a Specification expression 79 11 000097 2880 b WG5 approved; ready for SC22 79 11 000097 2880 c 3. Replace 7.1.6.2 (9) with the following: [79:11-15] 79 11 000097 2881 c 79 11 000097 2882 c (9) A reference to an intrinsic function which is: 79 11 000097 2883 c a) an array inquiry function (13.10.15) other than ALLOCATED, 79 11 000097 2884 c b) the bit inquiry function BIT_SIZE, 79 11 000097 2885 c c) the character inquiry function LEN, 79 11 000097 2886 c d) the kind inquiry function KIND, or 79 11 000097 2887 c e) a numeric inquiry function (13.10.8) 79 11 000097 2888 c and where each argument of the function is 79 11 000097 2889 c a) a restricted expression, or 79 11 000097 2890 c b) a variable whose properties inquired about are not: 79 11 000097 2891 c 1) dependent on the upper bound of the last dimension of an 79 11 000097 2892 c assumed-size array 79 11 000097 2893 c 2) defined by an expression that is not a 79 11 000097 2894 c restricted expression or 79 11 000097 2895 c 3) definable by an ALLOCATE or POINTER assignment statement 79 23 000012 552 a Type of a named constant when there is implicit mapping 79 23 000012 552 b X3J3 approved; ready for WG5 79 23 000012 552 c 4. In section 7.1.6.2, in line 2 of the paragraph after the constraint 79 23 000012 553 c [79:23] delete "currently". 85 2 00000d 91 a Minor edits and corrections 85 2 00000d 91 b X3J3 draft response 85 2 00000d 91 c 11. Section 7.2.3., first sentence [85:2] 85 2 00000d 92 c Change "operator" to "operation". 92 12 000079 1792 a Automatic character and ALLOCATABLE, POINTER and TARGET attributes 92 12 000079 1792 b X3J3 approved; ready for WG5 92 12 000079 1792 c 1. In the third constraint of section 7.5.2 [92:12] 92 12 000079 1793 c change ", type parameters," 92 12 000079 1794 c to ", kind type parameters," 92 15 000079 1796 a Automatic character and ALLOCATABLE, POINTER and TARGET attributes 92 15 000079 1796 b X3J3 approved; ready for WG5 92 15 000079 1796 c 2. Add at the beginning of the paragraph following the constraints of 92 15 000079 1797 c section 7.5.2 [92:15], 92 15 000079 1798 c 92 15 000079 1799 c "The target must have the same type parameters as the pointer." 93 10 000084 2932 a Change masked array assignment constraint to prose 93 10 000084 2932 b Published 93 10 000084 2932 c 1. Delete the first constraint following rule R743. [93:10-11] 93 21 000084 2934 a Change masked array assignment constraint to prose 93 21 000084 2934 b Published 93 21 000084 2934 c 2. Use the constraint body as the new first paragraph of section 7.5.3.2. 93 21 000084 2935 c [93:21] 93 29 000080 2877 a Vector subscripts in masked array assignment statements 93 29 000080 2877 b Published 93 29 000080 2877 c 1. In the second paragraph of section 7.5.3.2 after 93 29 000080 2878 c [93:29], add "or ". 93 34 000080 2880 a Vector subscripts in masked array assignment statements 93 34 000080 2880 b Published 93 34 000080 2880 c 2. In the third paragraph of section 7.5.3.2 after [93:34], 93 34 000080 2881 c add "or ". 93 37 000111 499 a Array constructors in masked assignment statements 93 37 000111 499 b WG5 approved; ready for SC22 93 37 000111 499 c In 7.5.3.2 following the third paragraph [93:37+], insert the 93 37 000111 500 c following paragraph: 93 37 000111 501 c 93 37 000111 502 c If an array constructor appears in an , the array 93 37 000111 503 c constructor is evaluated without any masked control by the 93 37 000111 504 c and then the is evaluated. 120 25 000072 2693 a Missing constraint for SIZE= 120 25 000072 2693 b Published 120 25 000072 2693 c Section 9.4.1, [120:25], add a constraint to the end of list: 120 25 000072 2694 c 120 25 000072 2695 c "If a SIZE= specifier is present, an ADVANCE= specifier also must appear." 123 30 000069 2665 a I/O implied DO variable 123 30 000069 2665 b Published 123 30 000069 2665 c In section 9.4.2, in the second constraint, replace the word 123 30 000069 2666 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 WG5 approved; ready for SC22 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 WG5 approved; ready for SC22 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 1364 a End of Namelist Input 128 27 000169 1364 b X3J3 draft response 128 27 000169 1364 c In section 9.4.6, item 3 [128:27-29] 128 27 000169 1365 c 128 27 000169 1366 c delete "or namelist input reaches the end of a record after having 128 27 000169 1367 c processed a name-value subsequence for every item in the 128 27 000169 1368 c " 139 37 000131 1536 a Formatted Input and Kind Type Parameters 139 37 000131 1536 b WG5 approved; ready for SC22 139 37 000131 1536 c 1. In Section 10.5.1.1, third paragraph [139:37-38], 139 37 000131 1537 c 139 37 000131 1538 c change "be in the form of an optionally signed integer constant" 139 37 000131 1539 c to "be a (R401)". 139 37 000131 1540 c 139 37 000131 1541 c note: is a BNF term. 139 45 000131 1543 a Formatted Input and Kind Type Parameters 139 45 000131 1543 b WG5 approved; ready for SC22 139 45 000131 1543 c 2. In Section 10.5.1.1, fourth paragraph [139:45], 139 45 000131 1544 c 139 45 000131 1545 c change "in the form of an unsigned integer constant" 139 45 000131 1546 c to "as a ". 139 45 000131 1547 c 139 45 000131 1548 c Change "Note that an integer constant" 139 45 000131 1549 c to "Note that a ". 139 45 000131 1550 c 139 45 000131 1551 c note: This deals with output, not input, but we should make it clear that 139 45 000131 1552 c output doesn't produce kind type parameters either. 140 6 000131 1554 a Formatted Input and Kind Type Parameters 140 6 000131 1554 b WG5 approved; ready for SC22 140 6 000131 1554 c 3. In Section 10.5.1.1, sixth paragraph [140:6], 140 6 000131 1555 c 140 6 000131 1556 c change "the unsigned integer constant" 140 6 000131 1557 c to "the ". 140 25 000131 1559 a Formatted Input and Kind Type Parameters 140 25 000131 1559 b WG5 approved; ready for SC22 140 25 000131 1559 c 4. In Section 10.5.1.2.1 [140:25], list item (1), 140 25 000131 1560 c 140 25 000131 1561 c change "Explicitly signed integer constant" 140 25 000131 1562 c to "A followed by a ". 140 26 000131 1564 a Formatted Input and Kind Type Parameters 140 26 000131 1564 b WG5 approved; ready for SC22 140 26 000131 1564 c 5. In Section 10.5.1.2.1 items (2) and (3) [140:26-27], 140 26 000131 1565 c 140 26 000131 1566 c change "an optionally signed integer constant" 140 26 000131 1567 c to "a ". 143 47 000131 1569 a Formatted Input and Kind Type Parameters 143 47 000131 1569 b WG5 approved; ready for SC22 143 47 000131 1569 c 6. In Section 10.5.2, second paragraph [143:47], 143 47 000131 1570 c 143 47 000131 1571 c change "additional characters in the field" 143 47 000131 1572 c to "additional characters in the field, which are ignored". 144 7 000131 1574 a Formatted Input and Kind Type Parameters 144 7 000131 1574 b WG5 approved; ready for SC22 144 7 000131 1574 c 7. In section 10.5.3, first paragraph [144:7-9], 144 7 000131 1575 c 144 7 000131 1576 c replace the last sentence 144 7 000131 1577 c with "The kind type parameter of all characters transferred and 144 7 000131 1578 c converted under control of one A or G edit descriptor is implied by 144 7 000131 1579 c the kind of the corresponding list item." 144 37 000061 2229 a G edit descriptor with "d" = 0 144 37 000061 2229 b Published 144 37 000061 2229 c 1. In section 10.5.4.1.2 second paragraph, 3rd sentence, 144 37 000061 2230 c after "- 0.5," add " or N is identically 0 and d is 0,". [144:37] 144 40 000061 2232 a G edit descriptor with "d" = 0 144 40 000061 2232 b Published 144 40 000061 2232 c 2. In section 10.5.4.1.2, second paragraph, fourth sentence, 144 40 000061 2233 c after "N is identically 0" add " and d is not zero". [144:40] 148 17 000131 1581 a Formatted Input and Kind Type Parameters 148 17 000131 1581 b WG5 approved; ready for SC22 148 17 000131 1581 c 8. In Section 10.8, second paragraph [148:17], 148 17 000131 1582 c 148 17 000131 1583 c replace "constant with no kind type parameter specified." 148 17 000131 1584 c with "constant. Neither nor may have kind type parameters 148 17 000131 1585 c specified. The constant is interpreted as though it had the same 148 17 000131 1586 c kind type parameter as the corresponding list item." 149 1 000131 1588 a Formatted Input and Kind Type Parameters 149 1 000131 1588 b WG5 approved; ready for SC22 149 1 000131 1588 c 9. In section 10.8.1, sixth paragraph [149:1-2], 149 1 000131 1589 c 149 1 000131 1590 c replace "character literal constant of the same kind as" 149 1 000131 1591 c with "possibly delimited sequence of zero or more s 149 1 000131 1592 c whose kind type parameter is implied by the kind of". 149 12 000043 1524 a List-directed character input 149 12 000043 1524 b Published 149 12 000043 1524 c 1. Section 10.8.1: Add " and" to the end of item (4), and [149:12] 149 12 000043 1526 a List-directed character input 149 12 000043 1526 b Published 149 12 000043 1526 c 2. Section 10.8.1: Add an additional item to the list after item (4): 149 12 000043 1527 c [149:12] 149 12 000043 1528 c 149 12 000043 1529 c "(5) The character constant contains at least one character," 151 7 000131 1594 a Formatted Input and Kind Type Parameters 151 7 000131 1594 b WG5 approved; ready for SC22 151 7 000131 1594 c 10. In section 10.8.2, ninth paragraph [151:7], 151 7 000131 1595 c 151 7 000131 1596 c delete "possibly are preceded by a and an underscore,". 151 11 000131 1598 a Formatted Input and Kind Type Parameters 151 11 000131 1598 b WG5 approved; ready for SC22 151 11 000131 1598 c 11. In section 10.8.2, tenth paragraph [151:11], 151 11 000131 1599 c 151 11 000131 1600 c delete "possibly are preceded by a and an underscore,". 151 31 000131 1602 a Formatted Input and Kind Type Parameters 151 31 000131 1602 b WG5 approved; ready for SC22 151 31 000131 1602 c 12. In Section 10.9, third paragraph [151:31-32], 151 31 000131 1603 c 151 31 000131 1604 c replace "constant with no kind type parameter specified." 151 31 000131 1605 c with "constant. Neither nor may have kind type parameters 151 31 000131 1606 c specified. The constant is interpreted as though it had the same 151 31 000131 1607 c kind type parameter as the corresponding list item." 151 39 000142 2295 a Namelist I/O 151 39 000142 2295 b X3J3 draft response 151 39 000142 2295 c 2. In section 10.9.1, replace item (2) with [151:39-40] 151 39 000142 2296 c "The character & followed immediately by the 151 39 000142 2297 c as specified in the namelist statement," 152 4 000165 1161 a Vector subscripts in Namelist input 152 4 000165 1161 b X3J3 draft response 152 4 000165 1161 c In section 10.9.1, second paragraph [152:4], add the following sentence 152 4 000165 1162 c at the end of the paragraph: 152 4 000165 1163 c 152 4 000165 1164 c 'The optional qualification, if any, must not contain a vector subscript.' 152 23 00000d 94 a Minor edits and corrections 152 23 00000d 94 b X3J3 draft response 152 23 00000d 94 c 12. Section 10.9.1.2., first sentence [152:23] 152 23 00000d 95 c After "" add "(10.9)" 153 15 000131 1609 a Formatted Input and Kind Type Parameters 153 15 000131 1609 b WG5 approved; ready for SC22 153 15 000131 1609 c 13. In section 10.9.1.3, fifth paragraph [153:15-16], 153 15 000131 1610 c 153 15 000131 1611 c replace "character literal constant of the same kind as" 153 15 000131 1612 c with "delimited sequence of zero or more s whose kind 153 15 000131 1613 c type parameter is implied by the kind of". 155 12 000131 1615 a Formatted Input and Kind Type Parameters 155 12 000131 1615 b WG5 approved; ready for SC22 155 12 000131 1615 c 14. In section 10.9.2.1, seventh paragraph [155:12], 155 12 000131 1616 c 155 12 000131 1617 c delete "possibly are preceded by a and an underscore,". 155 16 000131 1619 a Formatted Input and Kind Type Parameters 155 16 000131 1619 b WG5 approved; ready for SC22 155 16 000131 1619 c 15. In section 10.9.2.1, eighth paragraph, [155:16], 155 16 000131 1620 c 155 16 000131 1621 c delete "possibly are preceded by a and an underscore,". 158 11 000155 413 a Multiple USE statements, rename and only lists. 158 11 000155 413 b Returned by WG5 for X3J3 reconsideration 158 11 000155 413 c 1. In section 11.3.2, R1109 [158:11] 158 11 000155 414 c change "" 158 11 000155 415 c to "" 158 13 000155 417 a Multiple USE statements, rename and only lists. 158 13 000155 417 b Returned by WG5 for X3J3 reconsideration 158 13 000155 417 c 2. In section 11.3.2, the first constraint following R1109 [158:13] 158 13 000155 418 c change "" 158 13 000155 419 c to "" 158 19 000155 421 a Multiple USE statements, rename and only lists. 158 19 000155 421 b Returned by WG5 for X3J3 reconsideration 158 19 000155 421 c 3. In section 11.3.2, paragraph beginning "A USE statement" [158:19] 158 19 000155 422 c change "s" 158 19 000155 423 c to "s" 158 22 000155 425 a Multiple USE statements, rename and only lists. 158 22 000155 425 b Returned by WG5 for X3J3 reconsideration 158 22 000155 425 c 4. In section 11.3.2, paragraph beginning "More than one" [158:22-23] 158 22 000155 426 c change "s and s" 158 22 000155 427 c to "s and renames in s" 158 26 000128 1343 a Use associated generic names and renaming 158 26 000128 1343 b WG5 approved; ready for SC22 158 26 000128 1343 c The sentence in section 11.3.2 that states that if two "generic interfaces 158 26 000128 1344 c that are accessible in a scoping unit have the same name" [158:26-27], 158 26 000128 1345 c 158 26 000128 1346 c change "the same name" 158 26 000128 1347 c to "the same local name". 158 28 000074 2746 a Meaning of "referenced" in 11.3.2 158 28 000074 2746 b Published 158 28 000074 2746 c In section 11.3.2 [158:28] 158 28 000074 2747 c change the term "no entity is referenced by this name" 158 28 000074 2748 c to "the name is not used to refer to an entity". 160 29 000058 1327 a Ambiguous use of "keyword" 160 29 000058 1327 b Returned by WG5 for X3J3 reconsideration 160 29 000058 1327 c 7. Page 160, section 11.3.3.5, first paragraph, third line [160:29] 160 29 000058 1328 c change "keywords" to "argument keywords" 161 16 00000b 16 a Minor edits and corrections for Technical Corrigendum #2 161 16 00000b 16 b WG5 approved; ready for SC22 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 2537 a Subroutine and function names in nested scopes 163 39 000090 2537 b X3J3 consideration in progress 163 39 000090 2537 c 1. In section 12.1.2.2.1: [163:39] 163 39 000090 2538 c 163 39 000090 2539 c change: A name that appears in the scoping unit as an in 163 39 000090 2540 c an 163 39 000090 2541 c 163 39 000090 2542 c to: A name that is declared to be an external procedure name (by an 163 39 000090 2543 c or an ), or that appears as a 163 39 000090 2544 c in a 164 4 000090 2546 a Subroutine and function names in nested scopes 164 4 000090 2546 b X3J3 consideration in progress 164 4 000090 2546 c 2. In section 12.1.2.2.1: [164:4] 164 4 000090 2547 c 164 4 000090 2548 c change: (2) A in a 164 4 000090 2549 c 164 4 000090 2550 c to: .......................................... within an 164 4 000090 2551 c 164 6 000090 2553 a Subroutine and function names in nested scopes 164 6 000090 2553 b X3J3 consideration in progress 164 6 000090 2553 c 3. In section 12.1.2.2.1: [164:6] 164 6 000090 2554 c 164 6 000090 2555 c change: (3) A in a 164 6 000090 2556 c 164 6 000090 2557 c to: .............................................. within an 164 6 000090 2558 c 164 7 000090 2560 a Subroutine and function names in nested scopes 164 7 000090 2560 b X3J3 consideration in progress 164 7 000090 2560 c 4. In section 12.1.2.2.1: [164:7] 164 7 000090 2561 c 164 7 000090 2562 c delete item (4) of the list and renumber the rest of the list. 164 20 000118 3398 a Named constructs and host association 164 20 000118 3398 b Published 164 20 000118 3398 c Add new item to the list in section 12.1.2.2.1 [164:20] and adjust the 164 20 000118 3399 c list punctuation accordingly. 164 20 000118 3400 c 164 20 000118 3401 c "(16) The name of a named construct" 164 21 000088 2381 a Common block names and local names 164 21 000088 2381 b X3J3 approved; ready for WG5 164 21 000088 2381 c In section 12.1.2.2.1 in the sentence that contains the list of items 164 21 000088 2382 c replace 'that has this as its nongeneric name is inaccessible.' 164 21 000088 2383 c with 'that has this as its nongeneric name is inaccessible 164 21 000088 2384 c by that name by host association.' [164:21] 164 25 000032 1240 a Implicit declaration of a derived type 164 25 000032 1240 b Published 164 25 000032 1240 c 3. In paragraph 3 of 12.1.2.2.1 after "prior to the DATA statement.", 164 25 000032 1241 c insert a new paragraph: [164:25] 164 25 000032 1242 c 164 25 000032 1243 c "If a derived type name of a host is inaccessible, data entities of 164 25 000032 1244 c that type or subobjects of such data entities still can be 164 25 000032 1245 c accessible." 166 4 000049 1212 a Characteristics of function results 166 4 000049 1212 b X3J3 consideration in progress 166 4 000049 1212 c 2. Replace the last two sentences in 12.2.1.1 [166:4-6] with the following: 166 4 000049 1213 c 166 4 000049 1214 c If the shape or character length type parameter is not constant, the 166 4 000049 1215 c corresponding characteristic is the method by which the value is to be 166 4 000049 1216 c determined when the procedure is invoked. This includes the possibility that 166 4 000049 1217 c the value is assumed or that it is given by evaluating a specification 166 4 000049 1218 c expression. Two such methods are considered to be the same if the following 166 4 000049 1219 c are true: 166 4 000049 1220 c 166 4 000049 1221 c (1) they yield the same value 166 4 000049 1222 c 166 4 000049 1223 c (2) if one involves the evaluation of variables then the other must involve 166 4 000049 1224 c the evaluation of the same storage units (although not necessarily the 166 4 000049 1225 c same variable names). 166 14 000049 1197 a Characteristics of function results 166 14 000049 1197 b X3J3 consideration in progress 166 14 000049 1197 c 1. Replace the last two sentences in 12.2.2 [166:14-16] with the following: 166 14 000049 1198 c 166 14 000049 1199 c If the shape or character length type parameter is not constant, the 166 14 000049 1200 c corresponding characteristic is the method by which the value is to be 166 14 000049 1201 c determined when the function is invoked. This includes the possibility that 166 14 000049 1202 c the value is assumed or that it is given by evaluating a specification 166 14 000049 1203 c expression. Two such methods are considered to be the same if the following 166 14 000049 1204 c are true: 166 14 000049 1205 c 166 14 000049 1206 c (1) they yield the same value 166 14 000049 1207 c 166 14 000049 1208 c (2) if one involves the evaluation of variables then the other 166 14 000049 1209 c must involve the evaluation of the same storage units (although 166 14 000049 1210 c not necessarily the same variable names). 167 31 000117 758 a Use of MODULE PROCEDURE statement in internal procedures 167 31 000117 758 b WG5 approved; ready for SC22 167 31 000117 758 c Replace the second constraint in section 12.3.2.1 [167:31] with: 167 31 000117 759 c 167 31 000117 760 c "The MODULE PROCEDURE specification is allowed only if the 167 31 000117 761 c has a and is contained in a scoping 167 31 000117 762 c unit where each is accessible as a module procedure." 167 36 000007 349 a Duplicate module procedures in interface blocks 167 36 000007 349 b X3J3 draft response 167 36 000007 349 c The following additional constraint should be added to section 167 36 000007 350 c 12.3.2.1 [167:36]: 167 36 000007 351 c 167 36 000007 352 c Constraint: A in a must 167 36 000007 353 c not be one which previously had been specified in any 167 36 000007 354 c with the same generic identifier in this 167 36 000007 355 c specification part. 167 39 000057 2078 a Prohibition against multiple explicit specific interfaces 167 39 000057 2078 b Published 167 39 000057 2078 c Section 12.3.2.1, the sentence that begins "An interface body..." change 167 39 000057 2079 c "explicit interface" to "explicit specific interface". [167:39] 168 24 000058 1330 a Ambiguous use of "keyword" 168 24 000058 1330 b Returned by WG5 for X3J3 reconsideration 168 24 000058 1330 c 8. Page 168, replace the second sentence of the paragraph 168 24 000058 1331 c following the line "END INTERFACE" [168:24] with 168 24 000058 1332 c 168 24 000058 1333 c "Invocations of these procedures may 168 24 000058 1334 c use argument keywords; for example:" 168 24 000058 1335 c rationale: "keyword calls" is not defined. In general invocations 168 24 000058 1336 c can use both positional and argument keywords. 170 42 000006 260 a Procedure specifications in a scoping unit 170 42 000006 260 b Published 170 42 000006 260 c At the end of the fourth paragraph following R1207 in 12.3.2.2 [170:42], 170 42 000006 261 c add: 170 42 000006 262 c 170 42 000006 263 c A name that appears in an EXTERNAL statement must not also appear 170 42 000006 264 c as a specific procedure name in an interface block in the scoping unit. 171 15 000083 2119 a Extending generic intrinsic procedures 171 15 000083 2119 b X3J3 consideration in progress 171 15 000083 2119 c 2. In section 12.3.2.3 add to the end of the first paragraph after 171 15 000083 2120 c the constraint [171:15]: 171 15 000083 2121 c 171 15 000083 2122 c "A generic intrinsic procedure with a name that has the INTRINSIC 171 15 000083 2123 c attribute can also be the name of a generic interface." 172 8 000178 1801 a Specific routine with same name as generic passed as argument 172 8 000178 1801 b X3J3 draft response 172 8 000178 1801 c Section 12.4.1, insert the following in the penultimate constraint, ahead 172 8 000178 1802 c of "(12.3.2.1, 13.1)" [172:8]: 172 8 000178 1803 c 172 8 000178 1804 c "unless it is also a specific name" 172 13 000058 1338 a Ambiguous use of "keyword" 172 13 000058 1338 b Returned by WG5 for X3J3 reconsideration 172 13 000058 1338 c 9. Page 172, in the first paragraph following the 172 13 000058 1339 c constraints [172:13-17] change "a keyword" to "an argument 172 13 000058 1340 c keyword" twice, and change "the keyword" 172 13 000058 1341 c to "the argument keyword" 172 41 00000a 33 a Minor edits and corrections for Technical Corrigendum #1 172 41 00000a 33 b Published 172 41 00000a 33 c 3. 12.4.1.1, first paragraph, last line [172:41]; Change "of the the 172 41 00000a 34 c dummy" to "of the dummy" 172 41 000119 3429 a Rank of assumed-shape array 172 41 000119 3429 b Published 172 41 000119 3429 c At the end of the first paragraph of section 12.4.1.1 [172:41], add: "If 172 41 000119 3430 c the dummy argument is an assumed-shape array, the rank of the dummy argument 172 41 000119 3431 c must agree with the rank of the actual argument." 173 6 000125 1030 a Copy in/copy out of target dummy arguments 173 6 000125 1030 b X3J3 draft response 173 6 000125 1030 c 1. Section 12.4.1.1, add at the end of the fourth paragraph [173:6], 173 6 000125 1031 c 173 6 000125 1032 c "If the dummy argument has the TARGET attribute and the actual 173 6 000125 1033 c argument has the TARGET attribute, the dummy and actual arguments 173 6 000125 1034 c must have the same shape." 173 10 000125 1036 a Copy in/copy out of target dummy arguments 173 10 000125 1036 b X3J3 draft response 173 10 000125 1036 c 2. Section 12.4.1.1, fifth paragraph, last sentence [173:10-13] 173 10 000125 1037 c delete, "with a dummy argument of the procedure that has the 173 10 000125 1038 c TARGET attribute or" 173 13 000039 1040 a Association of a pointer actual argument with a dummy argument 173 13 000039 1040 b WG5 approved; ready for SC22 173 13 000039 1040 c 2. Add the following new paragraph following the current fifth 173 13 000039 1041 c paragraph of section 12.4.1.1: [173:13+] 173 13 000039 1042 c 173 13 000039 1043 c If the dummy argument is not a pointer and the corresponding actual 173 13 000039 1044 c argument is, the actual argument must be currently associated with a 173 13 000039 1045 c target and the dummy argument becomes argument associated with that 173 13 000039 1046 c target. 173 14 000125 1040 a Copy in/copy out of target dummy arguments 173 14 000125 1040 b X3J3 draft response 173 14 000125 1040 c 3. Section 12.4.1.1, delete the sixth paragraph [173:14-17] and 173 14 000125 1041 c replace with, 173 14 000125 1042 c 173 14 000125 1043 c "If the actual argument has the TARGET attribute and the 173 14 000125 1044 c corresponding dummy argument has the TARGET attribute: 173 14 000125 1045 c 173 14 000125 1046 c (1) Any pointers associated with the actual argument 173 14 000125 1047 c become associated with the corresponding dummy argument 173 14 000125 1048 c on invocation of the procedure. 173 14 000125 1049 c 173 14 000125 1050 c (2) When execution of the procedure completes, any 173 14 000125 1051 c pointers associated with the dummy argument remain 173 14 000125 1052 c associated with the actual argument. 173 14 000125 1053 c 173 14 000125 1054 c If the actual argument does not have the TARGET attribute 173 14 000125 1055 c and the corresponding dummy argument has the TARGET attribute, 173 14 000125 1056 c any pointers associated with the dummy argument become undefined 173 14 000125 1057 c when execution of the procedure completes." 177 29 00000a 36 a Minor edits and corrections for Technical Corrigendum #1 177 29 00000a 36 b Published 177 29 00000a 36 c 4. 12.5.2.4, at end of first paragraph [177:29]; Add new sentence 177 29 00000a 37 c "When a statement function is invoked, an instance of that statement 177 29 00000a 38 c function is created." 178 19 000055 1985 a Characteristics of character function results 178 19 000055 1985 b Published 178 19 000055 1985 c In Section 12.5.2.5 in the sentence that starts: "Otherwise, 178 19 000055 1986 c they ... " delete: "all be scalars ... length or". [178:19] 179 38 000053 1941 a Optional intrinsic function arguments 179 38 000053 1941 b Published 179 38 000053 1941 c 1. Add the following point to the numbered list in section 12.5.2.8: 179 38 000053 1942 c [179:38] 179 38 000053 1943 c 179 38 000053 1944 c (5) If it is an array, it must not be supplied as an actual 179 38 000053 1945 c argument to an elemental procedure unless an array of the same 179 38 000053 1946 c rank is supplied as an actual argument corresponding to a 179 38 000053 1947 c nonoptional dummy argument of that elemental procedure. 179 39 000053 1949 a Optional intrinsic function arguments 179 39 000053 1949 b Published 179 39 000053 1949 c 2. In the paragraph following the numbered list, replace "It" with 179 39 000053 1950 c "Except as noted in (5) above, it" [179:39] 180 4 000081 1959 a Pointer actual argument overlap 180 4 000081 1959 b X3J3 consideration in progress 180 4 000081 1959 c 1. In section 12.5.2.9, [180:4] after "dummy argument" add 180 4 000081 1960 c ", unless the dummy argument has either the POINTER or TARGET attribute" 180 4 000081 1961 c 180 36 000081 1963 a Pointer actual argument overlap 180 36 000081 1963 b X3J3 consideration in progress 180 36 000081 1963 c 2. In section 12.5.2.9, [180:36-38] in the second to last paragraph on the 180 36 000081 1964 c page, after "execution of the procedure" add ", unless all dummy arguments 180 36 000081 1965 c involved in the overlap have the POINTER or TARGET attribute". 182 4 000052 1868 a Expressions in statement function definitions 182 4 000052 1868 b Published 182 4 000052 1868 c 1. Section 12.5.4: First constraint, first sentence [182:4] 182 4 000052 1869 c change "references to scalar variables and array elements" 182 4 000052 1870 c to "references to variables" 182 4 000052 1871 c 182 4 000052 1872 c change "intrinsic operators" 182 4 000052 1873 c to "intrinsic operations" 182 4 000052 1874 c 182 4 000052 1875 c after first sentence add 182 4 000052 1876 c 182 4 000052 1877 c If contains a reference to a function or a function 182 4 000052 1878 c dummy procedure, the reference must not require an explicit 182 4 000052 1879 c interface, the function must not require an explicit interface or 182 4 000052 1880 c be a transformational intrinsic, and the result must be scalar. 182 4 000052 1881 c If an argument to a function or a function dummy procedure is array 182 4 000052 1882 c valued, it must be an array name. 182 12 000052 1884 a Expressions in statement function definitions 182 12 000052 1884 b Published 182 12 000052 1884 c 2. Section 12.5.4: Second constraint, third sentence [182:12] 182 12 000052 1885 c change "scalar variable, array element" 182 12 000052 1886 c to "variable" 182 12 000103 3147 a Statement Function with unreferenced dummy argument 182 12 000103 3147 b Published 182 12 000103 3147 c In section 12.5.4 split the second constraint at "If a scalar variable 182 12 000103 3148 c ..." [182:12] into a new constraint and add "dummy-arg-name," just before 182 12 000103 3149 c "scalar variable". 182 19 000052 1888 a Expressions in statement function definitions 182 19 000052 1888 b Published 182 19 000052 1888 c 3. Section 12.5.4: Fifth constraint, first sentence delete second word 182 19 000052 1889 c ("scalar") [182:19] 182 20 000062 2280 a Statement function constraints 182 20 000062 2280 b Published 182 20 000062 2280 c In the last constraint after R1226 in section 12.5.4 182 20 000062 2281 c replace "local to" 182 20 000062 2282 c with "accessible in". [182:20] 183 37 000058 1343 a Ambiguous use of "keyword" 183 37 000058 1343 b Returned by WG5 for X3J3 reconsideration 183 37 000058 1343 c 10. Section 13.3, first sentence [183:37], set "positional arguments" 183 37 000058 1344 c and "keyword arguments" in regular font 183 38 000058 1346 a Ambiguous use of "keyword" 183 38 000058 1346 b Returned by WG5 for X3J3 reconsideration 183 38 000058 1346 c 11. Page 183, section 13.3, first paragraph, third line [183:38] 183 38 000058 1347 c 183 38 000058 1348 c change "the keyword" to "the argument keyword" and 183 38 000058 1349 c change "A keyword" to "An argument keyword" 184 18 000159 746 a May undefined expressions be used as arguments to INQUIRY functions 184 18 000159 746 b X3J3 draft response 184 18 000159 746 c 1. In section 13.5.4 Character Inquiry Function [184:18-19] 184 18 000159 747 c replace the second sentence "The value of ...." 184 18 000159 748 c 184 18 000159 749 c with "If the argument to this function consists of a single primary 184 18 000159 750 c (7.1.1.1) that is a variable name then that variable need not be defined." 185 4 000159 752 a May undefined expressions be used as arguments to INQUIRY functions 185 4 000159 752 b X3J3 draft response 185 4 000159 752 c 2. In section 13.5.7 Bit Manipulation and Inquiry Procedures [185:4-5] 185 4 000159 753 c In the paragraph beginning "An inquiry ..." 185 4 000159 754 c replace the second sentence "The value of ...." 185 4 000159 755 c 185 4 000159 756 c with "If the argument to this function consists of a single primary 185 4 000159 757 c (7.1.1.1) that is a variable name then that variable need not be defined, 185 4 000159 758 c if a pointer it may be disassociated, and if allocatable need not be 185 4 000159 759 c allocated." 186 5 000108 438 a Referencing disassociated pointers 186 5 000108 438 b WG5 approved; ready for SC22 186 5 000108 438 c 2. Replace the first two sentences in section 13.7.2 [186:5] with: 186 5 000108 439 c 186 5 000108 440 c "The inquiry functions RADIX, DIGITS, MINEXPONENT, MAXEXPONENT, 186 5 000108 441 c PRECISION, RANGE, HUGE, TINY, and EPSILON return scalar values 186 5 000108 442 c related to the parameters of the model associated with the types and 186 5 000108 443 c kind type parameters of the arguments. The values of the arguments to 186 5 000108 444 c these functions need not be defined, pointer arguments may have 186 5 000108 445 c undefined or disassociated association status, and array arguments 186 5 000108 446 c need not be allocated." 186 7 000159 761 a May undefined expressions be used as arguments to INQUIRY functions 186 7 000159 761 b X3J3 draft response 186 7 000159 761 c 3. In section 13.7.2 Numeric Inquiry Functions [186:7-8] 186 7 000159 762 c replace the last sentence "The value of ...." 186 7 000159 763 c 186 7 000159 764 c with "If the argument to these functions consists of a single primary 186 7 000159 765 c (7.1.1.1) that is a variable name then that variable need not be defined, 186 7 000159 766 c if a pointer it may be disassociated, and if allocatable need not be 186 7 000159 767 c allocated." 187 12 000159 769 a May undefined expressions be used as arguments to INQUIRY functions 187 12 000159 769 b X3J3 draft response 187 12 000159 769 c 4. In section 13.8.5 Array Inquiry Functions [187:12] 187 12 000159 770 c replace the second paragraph "The values of ..." 187 12 000159 771 c 187 12 000159 772 c with "If the argument to these functions consists of a single primary 187 12 000159 773 c (7.1.1.1) that is a variable name then that variable need not be defined." 188 12 000058 1351 a Ambiguous use of "keyword" 188 12 000058 1351 b Returned by WG5 for X3J3 reconsideration 188 12 000058 1351 c 12. Page 188, section 13.10, first paragraph, first two lines [188:12-13] 188 12 000058 1352 c 188 12 000058 1353 c change "keyword" to "argument keyword" and 188 12 000058 1354 c change "keywords" to "argument keywords" 198 33 000109 3262 a Intrinsic function ASSOCIATED 198 33 000109 3262 b Published 198 33 000109 3262 c In 13.13.13 in the specification of the result type, add "scalar" after 198 33 000109 3263 c "default logical". [198:33] 198 37 000100 63 a ASSOCIATED intrinsic and zero-sized objects 198 37 000100 63 b Returned by WG5 for X3J3 reconsideration 198 37 000100 63 c 1. Section 13.13.13 Case (ii) [198:37], replace by 198 37 000100 64 c 198 37 000100 65 c If TARGET is present and is a nonzero-sized target, the result is 198 37 000100 66 c true if POINTER is currently associated with TARGET. If TARGET is 198 37 000100 67 c zero sized, but has the same type, type parameters, rank, and shape 198 37 000100 68 c as POINTER, the result is undefined. Otherwise, the result is false. 199 1 000100 70 a ASSOCIATED intrinsic and zero-sized objects 199 1 000100 70 b Returned by WG5 for X3J3 reconsideration 199 1 000100 70 c 2. Section 13.13.13 Case (iii) [199:1], replace by 199 1 000100 71 c 199 1 000100 72 c If TARGET is present and is a pointer, the result is true if both POINTER 199 1 000100 73 c and TARGET are currently associated with the same nonzero-sized target. 199 1 000100 74 c If the targets are zero sized and have the same type, type parameters, 199 1 000100 75 c rank, and shape, the result is undefined. Otherwise the result is false. 199 1 000100 76 c The result is also false if either POINTER or TARGET is disassociated. 203 23 00000a 40 a Minor edits and corrections for Technical Corrigendum #1 203 23 00000a 40 b Published 203 23 00000a 40 c 5. 13.13.25, Result Value, Case (ii), at beginning of the third line 203 23 00000a 41 c [203:23]; Change "1,sh" to "sh,1". 205 7 000171 1433 a Equivalence of DBLE(A) and REAL(A,KIND(0.0D0)) Intrinsics 205 7 000171 1433 b X3J3 consideration in progress 205 7 000171 1433 c In 13.13.27 DBLE, replace the text of the 'Result Value' section 205 7 000171 1434 c with: 205 7 000171 1435 c The result has the value REAL (A, KIND (0.0D0) ). [205:7-11] 210 23 00000c 53 a Minor edits and corrections 210 23 00000c 53 b X3J3 approved; ready for WG5 210 23 00000c 53 c 6. In 13.13.42 IBITS, Result value, 210 23 00000c 54 c 210 23 00000c 55 c change '.... bit POS right-adjusted' 210 23 00000c 56 c to '.... bit POS, right-adjusted' [210:23] 210 23 00000c 57 c 210 23 00000c 58 c Rationale: it is the result, not POS, that is right-adjusted. 214 22 000124 962 a Result of LBOUND for assumed-size arrays 214 22 000124 962 b X3J3 approved; ready for WG5 214 22 000124 962 c In section 13.13.52 replace the text of case (i) [214:22-25] with: 214 22 000124 963 c 214 22 000124 964 c "For an array section or for an array expression other than a whole 214 22 000124 965 c array or array structure component, LBOUND(ARRAY,DIM) has the value 214 22 000124 966 c 1. For a whole array or array structure component, LBOUND(ARRAY,DIM) 214 22 000124 967 c has the value: 214 22 000124 968 c (a) equal to the lower bound for subscript DIM of ARRAY if dimension 214 22 000124 969 c DIM of ARRAY does not have extent zero or if the upper bound for 214 22 000124 970 c dimension DIM is *; otherwise, 214 22 000124 971 c (b) 1." 220 25 00000a 43 a Minor edits and corrections for Technical Corrigendum #1 220 25 00000a 43 b Published 220 25 00000a 43 c 6. 13.13.66, Result Value, Case (iii) [220:25]; Change",[" to "[" 220 25 00000a 44 c (i.e. delete comma). 226 17 000120 3467 a PRESENT intrinsic and host association 226 17 000120 3467 b Published 226 17 000120 3467 c Replace the description of Argument in 13.13.80 [226:17] with 226 17 000120 3468 c 226 17 000120 3469 c "A must be the name of an optional dummy argument that is accessible in 226 17 000120 3470 c the procedure in which the PRESENT function reference appears." 228 2 000148 2828 a RANDOM_SEED, RANDOM_NUMBER 228 2 000148 2828 b X3J3 draft response 228 2 000148 2828 c In the description of RANDOM_SEED after RANDOM_NUMBER, 228 2 000148 2829 c add the text : [228:2] 228 2 000148 2830 c 228 2 000148 2831 c "The pseudo random number generator accessed by RANDOM_SEED and 228 2 000148 2832 c RANDOM_NUMBER maintains a seed that is updated during the execution 228 2 000148 2833 c of RANDOM_NUMBER and that may be specified or returned by 228 2 000148 2834 c RANDOM_SEED. Following execution of the statements 228 2 000148 2835 c 228 2 000148 2836 c CALL RANDOM_SEED(PUT=SEED1) 228 2 000148 2837 c CALL RANDOM_SEED(GET=SEED2) 228 2 000148 2838 c 228 2 000148 2839 c it is not required that SEED1 equal SEED2. However it is required that 228 2 000148 2840 c calls to RANDOM_NUMBER immediately after a call to RANDOM_SEED 228 2 000148 2841 c with a seed that is either SEED1 or SEED2 return the same sequence of 228 2 000148 2842 c pseudo random numbers. In particular, after subsequent execution of the 228 2 000148 2843 c statements 228 2 000148 2844 c 228 2 000148 2845 c CALL RANDOM_NUMBER(X1) 228 2 000148 2846 c CALL RANDOM_SEED(PUT=SEED2) 228 2 000148 2847 c CALL RANDOM_NUMBER(X2) 228 2 000148 2848 c 228 2 000148 2849 c it is required that X1=X2." 228 9 000176 1672 a Definition of RANDOM_SEED 228 9 000176 1672 b X3J3 draft response 228 9 000176 1672 c 1. In 13.13.84, RANDOM_SEED, PUT argument, replace the last sentence 228 9 000176 1673 c (beginning "It is used by the processor ..." with [228:9]: 228 9 000176 1674 c 228 9 000176 1675 c It is used in a processor-dependent manner to compute the seed value. 228 9 000176 1676 c It is not required that an immediately following 228 9 000176 1677 c "CALL RANDOM_SEED (GET=aseed)" assign a physical representation 228 9 000176 1678 c to "aseed" identical to the physical representation of the value 228 9 000176 1679 c specified for PUT. 228 11 000176 1681 a Definition of RANDOM_SEED 228 11 000176 1681 b X3J3 draft response 228 11 000176 1681 c 2. In 13.13.84, RANDOM_SEED, GET argument, replace the last sentence 228 11 000176 1682 c (beginning "It is set by the processor ...") with [228:11-12]: 228 11 000176 1683 c 228 11 000176 1684 c It is assigned the physical representation of the seed value in a 228 11 000176 1685 c processor-dependent manner. 234 6 000064 2340 a SPACING result for 0.0 234 6 000064 2340 b Published 234 6 000064 2340 c In section 13.13.100, after "Result Value." 234 6 000064 2341 c change "The" 234 6 000064 2342 c to "If X is not zero, the". 234 6 000064 2343 c In the same section, 234 6 000064 2344 c change "; otherwise " 234 6 000064 2345 c to ". Otherwise". [234:6] 236 11 000132 1699 a SYSTEM_CLOCK intrinsic conformance requirements 236 11 000132 1699 b WG5 approved; ready for SC22 236 11 000132 1699 c In section 13.13.104, SYSTEM_CLOCK, change the text for COUNT_RATE 236 11 000132 1700 c from 'the number' 236 11 000132 1701 c to 'a processor-dependent approximation to the number' [236:11] 242 28 000083 2111 a Extending generic intrinsic procedures 242 28 000083 2111 b X3J3 consideration in progress 242 28 000083 2111 c 1. In section 14.1.2.3 add after the second sentence [242:28]: 242 28 000083 2112 c 242 28 000083 2113 c "If a generic interface has the same name as an accessible generic intrinsic 242 28 000083 2114 c procedure and the scoping unit either contains an INTRINSIC attribute 242 28 000083 2115 c specification for that name or accesses that generic intrinsic procedure 242 28 000083 2116 c with that name by use association, the generic interface extends the 242 28 000083 2117 c generic intrinsic procedure." 245 3 00000c 44 a Minor edits and corrections 245 3 00000c 44 b X3J3 approved; ready for WG5 245 3 00000c 44 c 5. Page 245, section 14.1.2.5, in the second sentence [245:3] 245 3 00000c 45 c 245 3 00000c 46 c change 'It' 245 3 00000c 47 c to 'Outside the type definition, it'. 245 3 00000c 48 c 245 3 00000c 49 c Reason: a component name appears in the derived type definition 245 3 00000c 50 c as well as possibly appearing in a component of a 245 3 00000c 51 c structure of that type. 245 14 000170 1393 a Argument Keywords and Intrinsic Procedures 245 14 000170 1393 b WG5 approved; ready for SC22 245 14 000170 1393 c In section 14.1.2.6 add a new paragraph after the current 245 14 000170 1394 c paragraph. [245:14+] 245 14 000170 1395 c 245 14 000170 1396 c "A dummy argument name in an intrinsic procedure has a scope as an 245 14 000170 1397 c argument keyword of the scoping unit making reference to it. 245 14 000170 1398 c As an argument keyword, it may appear only in a procedure reference 245 14 000170 1399 c for the procedure of which it is a dummy argument." 245 23 000031 1149 a Overloaded implied-DO variable names 245 23 000031 1149 b Published 245 23 000031 1149 c Replace the last paragraph of section 14.1.3 with the following two 245 23 000031 1150 c paragraphs: [245:23] 245 23 000031 1151 c 245 23 000031 1152 c Except for a common block name or a scalar variable name, a name that 245 23 000031 1153 c identifies a global entity or local entity of class 1 (14.1.2) 245 23 000031 1154 c accessible in the scoping unit of a statement must not be the name of 245 23 000031 1155 c a statement entity of that statement. Within the scope of a 245 23 000031 1156 c statement entity, another statement entity must not have the same name. 245 23 000031 1157 c 245 23 000031 1158 c If the name of a global or local entity accessible in the scoping unit of 245 23 000031 1159 c a statement is the same as the name of a statement entity in that 245 23 000031 1160 c statement, the name is interpreted within the scope of the statement 245 23 000031 1161 c entity as that of the statement entity. Elsewhere in the scoping unit, 245 23 000031 1162 c including parts of the statement outside the scope of the statement 245 23 000031 1163 c entity, the name is interpreted as that of the global or local entity. 247 2 000068 2614 a Pointer association status 247 2 000068 2614 b Published 247 2 000068 2614 c 1. In section 14.6.2.1, item (3) subitem (c), delete "or" [247:2] 247 4 000068 2616 a Pointer association status 247 4 000068 2616 b Published 247 4 000068 2616 c 2. The reference to section 6.3.3.2 in 14.6.2.1 (3) (d) is misleading. 247 4 000068 2617 c In section 14.6.2.1, item (3) subitem (d), remove "6.3.3.2," 247 4 000068 2618 c and change the period at the end to ", or" [247:4]. 247 4 000068 2620 a Pointer association status 247 4 000068 2620 b Published 247 4 000068 2620 c 3. The list in section 14.6.2.1, item (3), of ways that pointer 247 4 000068 2621 c association status can become undefined is incomplete. 247 4 000068 2622 c In section 14.6.2.1, item (3) add a new subitem as follows: [247:4] 247 4 000068 2623 c 247 4 000068 2624 c (e) After the execution of a RETURN or END statement in a procedure 247 4 000068 2625 c where the pointer was either declared or, with the exceptions 247 4 000068 2626 c described in 6.3.3.2, accessed. 248 15 000154 347 a EQUIVALENCE and zero-sized sequences 248 15 000154 347 b X3J3 consideration in progress 248 15 000154 347 c In section 14.6.3.2 [248:15], after the last sentence in the second 248 15 000154 348 c paragraph, add "Two zero-sized subobjects of the same object are the same zero 248 15 000154 349 c sized storage sequence.". 248 40 000126 1153 a Character Entry statements and Partial Association 248 40 000126 1153 b WG5 approved; ready for SC22 248 40 000126 1153 c In section 14.6.3.3 in the sentence (last two lines of page 248) 248 40 000126 1154 c [248:40-41] "For character entities, partial association may occur only through 248 40 000126 1155 c argument association, or the use of COMMON, EQUIVALENCE, or ENTRY statements." 248 40 000126 1156 c 248 40 000126 1157 c change "COMMON, EQUIVALENCE, or ENTRY" 248 40 000126 1158 c to "COMMON or EQUIVALENCE" 250 24 00000b 22 a Minor edits and corrections for Technical Corrigendum #2 250 24 00000b 22 b WG5 approved; ready for SC22 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 WG5 approved; ready for SC22 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 46 a Minor edits and corrections for Technical Corrigendum #1 255 27 00000a 46 b Published 255 27 00000a 46 c 7. Annex A, conformable [255:27]; Change "2.4.7" to "2.4.5". 255 38 00000a 48 a Minor edits and corrections for Technical Corrigendum #1 255 38 00000a 48 b Published 255 38 00000a 48 c 8. Annex A, constant [255:38]; Change "2.4.4" to "2.4.3.1.2". 255 42 00000d 97 a Minor edits and corrections 255 42 00000d 97 b X3J3 draft response 255 42 00000d 97 c 13. Annex A, [255:42] 255 42 00000d 98 c Change "CASE" to "SELECT CASE" 256 10 000096 2788 a Definition of "Declaration" 256 10 000096 2788 b X3J3 consideration in progress 256 10 000096 2788 c 1. In Annex A, add to page 256 after "datum" [256:10+] 256 10 000096 2789 c 256 10 000096 2790 c Declaration(2.5.3): The specification of for various program 256 10 000096 2791 c , Often this involves specifying the of a 256 10 000096 2792 c or specifying the of a ." 256 10 000096 2793 c 256 23 00000a 50 a Minor edits and corrections for Technical Corrigendum #1 256 23 00000a 50 b Published 256 23 00000a 50 c 9. Annex A, derived type [256:23]; Change "2," to "2)". 256 38 000077 1702 a Miscellaneous questions 256 38 000077 1702 b WG5 approved; ready for SC22 256 38 000077 1702 c 1. In Annex A, in the entry for "entity", 256 38 000077 1703 c replace "a named variable, an expression, a component of a structure, a named 256 38 000077 1704 c constant" 256 38 000077 1705 c with "a data entity". [256:38-39] 257 8 00000a 52 a Minor edits and corrections for Technical Corrigendum #1 257 8 00000a 52 b Published 257 8 00000a 52 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 WG5 approved; ready for SC22 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 54 a Minor edits and corrections for Technical Corrigendum #1 258 19 00000a 54 b Published 258 19 00000a 54 c 11. Annex A, literal constant [258:19]; Change "2.4.4" to "2.4.3.1.2". 258 22 00000a 56 a Minor edits and corrections for Technical Corrigendum #1 258 22 00000a 56 b Published 258 22 00000a 56 c 12. Annex A, main program [258:22]; Change "2," to "2)". 258 22 000077 1707 a Miscellaneous questions 258 22 000077 1707 b WG5 approved; ready for SC22 258 22 000077 1707 c 2. In Annex A, in the entry for "main program", 258 22 000077 1708 c replace "subprogram" 258 22 000077 1709 c with "external subprogram" [258:22] 258 25 00000a 58 a Minor edits and corrections for Technical Corrigendum #1 258 25 00000a 58 b Published 258 25 00000a 58 c 13. Annex A, module [258:25]; Change "4," to "4)". 258 34 00000a 60 a Minor edits and corrections for Technical Corrigendum #1 258 34 00000a 60 b Published 258 34 00000a 60 c 14. Annex A, named constant [258:34]; Change "2.4.4" to "2.4.3.1.2". 259 19 00000a 62 a Minor edits and corrections for Technical Corrigendum #1 259 19 00000a 62 b Published 259 19 00000a 62 c 15. Annex A, procedure [259:19]; Change "3," to "3)". 259 31 00000a 64 a Minor edits and corrections for Technical Corrigendum #1 259 31 00000a 64 b Published 259 31 00000a 64 c 16. Annex A, rank [259:31]; Change "2.4.7" to "2.4.5". 260 12 00000a 66 a Minor edits and corrections for Technical Corrigendum #1 260 12 00000a 66 b Published 260 12 00000a 66 c 17. Annex A, shape [ 260:12]; Change "2.4.7" to "2.4.5". 260 14 00000a 68 a Minor edits and corrections for Technical Corrigendum #1 260 14 00000a 68 b Published 260 14 00000a 68 c 18. Annex A, size [260:14]; Change "2.4.7" to "2.4.5". 260 14 000096 2795 a Definition of "Declaration" 260 14 000096 2795 b X3J3 consideration in progress 260 14 000096 2795 c 2. In Annex A, add to page 260 after "size" [260:14+] 260 14 000096 2796 c 260 14 000096 2797 c Specification: The assignment of attributes and properties to names. 260 35 00000a 70 a Minor edits and corrections for Technical Corrigendum #1 260 35 00000a 70 b Published 260 35 00000a 70 c 19. Annex A, subobject [260:35]; Change "2.4.3.2" to "2.4.3.1". 261 9 00000a 72 a Minor edits and corrections for Technical Corrigendum #1 261 9 00000a 72 b Published 261 9 00000a 72 c 20. Annex A, target [261:9]; Change "specified in a" to "specified in 261 9 00000a 73 c a TARGET statement or". 261 30 00000a 75 a Minor edits and corrections for Technical Corrigendum #1 261 30 00000a 75 b Published 261 30 00000a 75 c 21. Annex A, variable [261:30]; Change "2.4.5" to "2.4.3.1.1". 266 17 00000d 100 a Minor edits and corrections 266 17 00000d 100 b X3J3 draft response 266 17 00000d 100 c 14. Section C4.3 [266:17] 266 17 00000d 101 c Change "KIND" to "kind". 269 21 000041 1096 a Procedure with target dummy argument requires explicit interface 269 21 000041 1096 b X3J3 consideration in progress 269 21 000041 1096 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 WG5 approved; ready for SC22 273 14 00000b 20 c 3. Annex C, first example [273:14]; change "ENDTYPE" to "END TYPE". 281 5 00000d 103 a Minor edits and corrections 281 5 00000d 103 b X3J3 draft response 281 5 00000d 103 c 15. Section C10 [281:5] 281 5 00000d 104 c Change "an apostrophe edit descriptor" 281 5 00000d 105 c to "a character constant edit descriptor delimited with apostrophes" 281 6 00000d 107 a Minor edits and corrections 281 6 00000d 107 b X3J3 draft response 281 6 00000d 107 c 16. Section C10 [281:6-7] 281 6 00000d 108 c Change "the apostrophe edit descriptor" twice 281 6 00000d 109 c to "the edit descriptor" 281 6 00000d 110 c 281 6 00000d 111 c Rationale: for 15 and 16: In section 10 the term "apostrophe edit 281 6 00000d 112 c descriptor" is absent (see 10.2.1 and 10.7.1) 286 16 000153 220 a Defined Operations, dummy arguments INTENT(IN) 286 16 000153 220 b X3J3 approved; ready for WG5 286 16 000153 220 c 1. Section C.11.4, in function ELEMENT [286:16,17], change 286 16 000153 221 c INTEGER X 286 16 000153 222 c to 286 16 000153 223 c INTEGER, INTENT(IN) :: X 286 16 000153 224 c and change 286 16 000153 225 c TYPE (SET) A 286 16 000153 226 c to 286 16 000153 227 c TYPE (SET), INTENT(IN) :: A 286 21 000153 229 a Defined Operations, dummy arguments INTENT(IN) 286 21 000153 229 b X3J3 approved; ready for WG5 286 21 000153 229 c 2. Section C.11.4, in function UNION [286:21], change 286 21 000153 230 c TYPE (SET) A, B, UNION 286 21 000153 231 c to 286 21 000153 232 c TYPE (SET) UNION 286 21 000153 233 c TYPE (SET), INTENT(IN) :: A, B 286 37 000153 235 a Defined Operations, dummy arguments INTENT(IN) 286 37 000153 235 b X3J3 approved; ready for WG5 286 37 000153 235 c 3. Section C.11.4, in function DIFFERENCE [286:37], change 286 37 000153 236 c TYPE (SET) A, B, DIFFERENCE 286 37 000153 237 c to 286 37 000153 238 c TYPE (SET) DIFFERENCE 286 37 000153 239 c TYPE (SET), INTENT(IN) :: A, B 287 2 000153 241 a Defined Operations, dummy arguments INTENT(IN) 287 2 000153 241 b X3J3 approved; ready for WG5 287 2 000153 241 c 4. Section C.11.4, in function INTERSECTION [287:2], change 287 2 000153 242 c TYPE (SET) A, B, INTERSECTION 287 2 000153 243 c to 287 2 000153 244 c TYPE (SET) INTERSECTION 287 2 000153 245 c TYPE (SET), INTENT(IN) :: A, B 287 6 000153 247 a Defined Operations, dummy arguments INTENT(IN) 287 6 000153 247 b X3J3 approved; ready for WG5 287 6 000153 247 c 5. Section C.11.4, in function SUBSET [287:6], change 287 6 000153 248 c TYPE (SET) A, B 287 6 000153 249 c to 287 6 000153 250 c TYPE (SET), INTENT(IN) :: A, B 292 5 000125 1059 a Copy in/copy out of target dummy arguments 292 5 000125 1059 b X3J3 draft response 292 5 000125 1059 c 4. Section C.12.8, delete the second paragraph through the end of 292 5 000125 1060 c the section [292:5-37] and replace with 292 5 000125 1061 c 292 5 000125 1062 c "When execution of a procedure completes, any pointer that remains 292 5 000125 1063 c defined and that is associated with a dummy argument that has the 292 5 000125 1064 c TARGET attribute, remains associated with the corresponding actual 292 5 000125 1065 c argument if the actual argument has the TARGET attribute. 292 5 000125 1066 c 292 5 000125 1067 c REAL, POINTER :: PBEST 292 5 000125 1068 c REAL, TARGET :: B (10000) 292 5 000125 1069 c CALL BEST (PBEST, B) ! Upon return PBEST is associated 292 5 000125 1070 c ... ! with the "best" element of B 292 5 000125 1071 c CONTAINS 292 5 000125 1072 c SUBROUTINE BEST (P, A) 292 5 000125 1073 c REAL, POINTER :: P 292 5 000125 1074 c REAL, TARGET :: A (:) 292 5 000125 1075 c ... ! Find the "best" element A(I) 292 5 000125 1076 c P => A (I) 292 5 000125 1077 c RETURN 292 5 000125 1078 c END SUBROUTINE 292 5 000125 1079 c END 292 5 000125 1080 c 292 5 000125 1081 c When the procedure BEST completes, the pointer PBEST is 292 5 000125 1082 c associated with an element of B. 292 5 000125 1083 c 292 5 000125 1084 c An actual argument without the TARGET attribute can become 292 5 000125 1085 c associated with a dummy argument with the TARGET attribute. 292 5 000125 1086 c This permits pointers to become associated with the dummy 292 5 000125 1087 c argument during execution of the procedure that contains 292 5 000125 1088 c the dummy argument. For example: 292 5 000125 1089 c 292 5 000125 1090 c INTEGER LARGE(100,100) 292 5 000125 1091 c CALL SUB(LARGE) 292 5 000125 1092 c ... 292 5 000125 1093 c CALL SUB() 292 5 000125 1094 c CONTAINS 292 5 000125 1095 c SUBROUTINE SUB(ARG) 292 5 000125 1096 c INTEGER, TARGET, OPTIONAL :: ARG(100,100) 292 5 000125 1097 c INTEGER, POINTER, DIMENSION(:,:) :: PARG 292 5 000125 1098 c IF (PRESENT(ARG)) THEN 292 5 000125 1099 c PARG => ARG 292 5 000125 1100 c ELSE 292 5 000125 1101 c ALLOCATE (PARG(100,100)) 292 5 000125 1102 c PARG = 0 292 5 000125 1103 c ENDIF 292 5 000125 1104 c ... ! Code with lots of references to PARG 292 5 000125 1105 c If (.NOT. PRESENT(ARG)) DEALLOCATE(PARG) 292 5 000125 1106 c END SUBROUTINE SUB 292 5 000125 1107 c END 292 5 000125 1108 c 292 5 000125 1109 c Within subroutine SUB the pointer PARG is either associated with 292 5 000125 1110 c the dummy argument ARG or it is associated with an allocated target. 292 5 000125 1111 c The bulk of the code can reference PARG without further calls to 292 5 000125 1112 c the PRESENT intrinsic." 294 39 00000d 114 a Minor edits and corrections 294 39 00000d 114 b X3J3 draft response 294 39 00000d 114 c 17. Section C13.1.6.3 [294:39-42] 294 39 00000d 115 c Delete word: "Declared" (4 times) 294 39 00000d 116 c Rationale: In section 13 descriptions of these functions do not 294 39 00000d 117 c contain the word "declared". These array inquire functions allow 294 39 00000d 118 c certain properties of an array to be determined dynamically. 294 39 00000d 119 c 339 3 00000d 87 a Minor edits and corrections 339 3 00000d 87 b X3J3 draft response 339 3 00000d 87 c 10. Page 339, section D.2.3 [339:3], add after the line for "'" 339 3 00000d 88 c ' " R408 R409 R410 R420' 339 3 00000d 89 c Rationale: Terminal symbol " was omitted from list 363 37 000058 1356 a Ambiguous use of "keyword" 363 37 000058 1356 b Returned by WG5 for X3J3 reconsideration 363 37 000058 1356 c 13. Page 363, delete the entry for "argument keywords 183" [363:37] 363 37 000058 1357 c rationale: odd to index both singular and plural. "Keyword", 363 37 000058 1358 c and "statement keyword" are indexed to page 16, as is the remaining 363 37 000058 1359 c entry for "argument keyword". 368 13 000058 1361 a Ambiguous use of "keyword" 368 13 000058 1361 b Returned by WG5 for X3J3 reconsideration 368 13 000058 1361 c 14. Annex F, delete the entry "positional arguments" [368:13]