From dtm@castle.edinburgh.ac.uk Wed Mar 10 15:14:10 1993 Received: from sun2.nsfnet-relay.ac.uk by dkuug.dk with SMTP id AA04702 (5.65c8/IDA-1.4.4j for ); Wed, 10 Mar 1993 16:52:05 +0100 Via: uk.ac.edinburgh.castle; Wed, 10 Mar 1993 15:14:47 +0000 Date: 10 Mar 93 15:14:10 GMT From: D Muxworthy Subject: UK vote on WG5-N865 To: Jeanne Martin Cc: sc22wg5@dkuug.dk Message-Id: <9303101514.aa18947@castle.ed.ac.uk> X-Charset: ASCII X-Char-Esc: 29 Country Ballot U.K. |Y|wc N N865 Item |x|_| |_| 000000 Minor edits and corrections to ISO/IEC 1539:1991 (E) |x|_| |_| 000001 Equivalence of Expression Evaluations |x|_| |_| 000002 Default Main Program Name |x|_| |_| 000003 Preconnected Units and UNIT=* |x|_| |_| 000005 Namelist Output of Zero Length Character Strings |x|_| |_| 000006 Procedure Specifications in a Scoping Unit |x|_| |_| 000009 Generic Interfaces with the Same Name in a Program |x|_| |_| 000010 Generic Interfaces with the Same Name in a Scoping Unit |_|_| |x| 000013 Implicit Environment of an Interface Block |x|_| |_| 000014 Interface for Character Function with a Variable Length Result |x|_| |_| 000015 Error in Fourth Constraint for R429 |x|_| |_| 000016 Character Length Specification |x|_| |_| 000017 Creation of Entities by Local Names in rename-list |x|_| |_| 000018 Valid Characters Indicating Fixed Form Statement Continuation |x|_| |_| 000019 Correctness of Last Example in Section 4.5 |x|_| |_| 000020 References to the Same Derived Type by Different Names |x|_| |_| 000021 References to Different Derived Types with the Same Name |x|_| |_| 000022 Use of Derived Type Name in Host Scoping Unit |x|_| |_| 000024 IMPLICIT NONE and the Type of an Internal Procedure Result |x|_| |_| 000025 Resolution of Internal Procedure References |x|_| |_| 000026 Bounds of Array Expressions |x|_| |_| 000031 Overloaded Implied-DO Variable Names |x|_| |_| 000032 Implicit Declaration of a Derived Type |x|_| |_| 000036 Pointer to an Assumed-size Array |x|_| |_| 000037 Use of Array Sections in Pointer Assignment Statements |x|_| |_| 000038 Same Interface Body in Multiple Generic Interface Blocks |x|_| |_| 000040 Allocation of Arrays of Pointers |x|_| |_| 000042 KIND parameter value |x|_| |_| 000043 List-directed character input |x|_| |_| 000044 END Statement and Fixed Form Source |x|_| |_| 000045 Array Intrinsics with Arrays of Derived-type Arguments |x|_| |_| 000046 RESULT clause for RECURSIVE functions |x|_| |_| 000047 Automatic data object in initialization expressions |x|_| |_| 000048 Pointer-valued statement functions |x|_| |_| 000050 Repeat counts on edit descriptors |x|_| |_| 000051 On Unambiguous generic procedure references |x|_| |_| 000052 Expressions in Statement Function Definitions |x|_| |_| 000053 Optional Intrinsic Function Arguments |x|_| |_| 000055 Characteristics of character function results |x|_| |_| 000056 TRANSFER intrinsic function description |_|x| |_| 000057 Prohibition against multiple explicit specific interfaces |x|_| |_| 000059 SEQUENCE derived type and component bounds |x|_| |_| 000060 Statement function argument references |x|_| |_| 000061 G edit descriptor with _d_ = 0 |x|_| |_| 000062 Statement function constraints |x|_| |_| 000063 Interfaces and dummy procedure arguments |x|_| |_| 000064 SPACING result for 0.0 |x|_| |_| 000065 Block and Nonblock DO Construct |x|_| |_| 000066 Declaration of FUNCTION type |x|_| |_| 000067 Output of negative signed zero |x|_| |_| 000068 Pointer association status |x|_| |_| 000069 I/O implied DO variable |x|_| |_| 000072 Missing constraint for SIZE= |x|_| |_| 000074 Meaning of "referenced" in 11.3.2 |x|_| |_| 000078 Intrinsic functions in MODULE specification statements |x|_| |_| 000080 Vector subscripts in masked array assignment statements |_|x| |_| 000084 Change masked array assignment constraint to prose |x|_| |_| 000085 Nondefault Integer Data Type for UNIT=, ... Specifiers |x|_| |_| 000094 Functions in WRITE statement implied-DO loops |x|_| |_| 000095 Functions in IOLENGTH implied-DO loops |_|_| |x| 000098 KIND param and list directed I/O |x|_| |_| 000103 Statement Function with unreferenced dummy argument |x|_| |_| 000104 rounding formatted output |x|_| |_| 000107 USE renaming of generic and specific interfaces |x|_| |_| 000109 Intrinsic Function ASSOCIATED |x|_| |_| 000110 Named Constant Shape Specification |x|_| |_| 000115 Multiple dummy arguments |x|_| |_| 000118 Named constructs and host association |x|_| |_| 000119 Rank of assumed-shape array |x|_| |_| 000120 PRESENT intrinsic and host association General comments Procedure: The UK believes that edits should be made to IS 1539:1991 only where absolutely necessary to remove errors, to resolve inconstencies and to provide essential clarification. No technical changes should be made other than for these reasons. Simple editorial improvements should even not be considered. Form of Technical Corrigendum: The UK recommends that the Technical Corrigendum be in the form of an ordered list of approved edits to the standard, with an edited form of the current maintenance document supplied as as informative annex. This would avoid the problem of putting the maintenance document into an ISO-approved format. The annex should not include items of minimal interest, possibly where the original query was based on a misunderstanding and where the item adds little to the understanding of a new reader. It is suggested that items 24, 36, 37, 42, 94 and 95 fall into this category. This refers only to the public document: such items would be retained in any internal working documents. Form of Maintenance Document: Although it is ISO policy not to use page and line numbers in defect reports, it would be helpful if the maintenance document, as an "internal working document", were to contain page and line numbers to identify text. Reasons for "no" votes 13. This is a very strong "no". The edit proposed involves a technical change to the standard. There are valid technical arguments both for using the scoping rules as described in the standard and for the different scoping rules suggested by this item. However the standard is clear and is internally consistent. There is no reason even to consider a technical change. Compilers, documentation and text books have already been written to accord to the standard. If the principle were to be accepted of changing the standard retrospectively because opinions had changed since it was approved, there would be no end to such edits and confidence in the whole standards-making process would be reduced. Incidentally the content of the discussion is incorrect. It is not true to say that the possibility of different implicit mappings was overlooked; the different possibilities were considered and the form finally adopted was positively chosen. 98. No edit is needed. The descriptions of input fields in section 10 do not mention the possibility of named constants in input records. Moreover the suggested edit is incomplete and misleading. For completeness it should also have refered to section 5.2.10 (54/6). It is misleading because the name of a named constant may appear in an I/O record and be processed as a character string. Comments accompanying "yes" votes: 57. There are two sentences in section 12.3.2.1 that begin "An interface body...". To clarify, change the text to "An interface body in an interface block...". 84. The edit which is proposed puts text in an inappropriate place. The new sentence should be in section 7.5.3.1, before the example. ---------------------------------end----------------------------------------