From jls@cray.com Mon Aug 7 20:48:49 2000 Received: from timbuk.cray.com (timbuk-fddi.cray.com [128.162.8.102]) by dkuug.dk (8.9.2/8.9.2) with ESMTP id UAA53845 for ; Mon, 7 Aug 2000 20:48:48 +0200 (CEST) (envelope-from jls@cray.com) From: jls@cray.com Received: from relayb.cray.com (root@relayb.americas.sgi.com [128.162.2.87]) by timbuk.cray.com (8.8.8/CRI-gate-news-1.3) with ESMTP id NAA28841 for ; Mon, 7 Aug 2000 13:48:41 -0500 (CDT) Received: from fsgi027.americas.sgi.com (fsgi027.americas.sgi.com [128.162.186.138]) by relayb.cray.com (8.10.1/8.10.1) with ESMTP id e77Ibgr01721 for ; Mon, 7 Aug 2000 13:37:43 -0500 Received: by fsgi027.americas.sgi.com (980427.SGI.8.8.8/Cray-client-1.6c) id NAA17851; Mon, 7 Aug 2000 13:48:40 -0500 (CDT) Message-Id: <200008071848.NAA17851@fsgi027.americas.sgi.com> Subject: Re: WG5 letter ballot on Fortran interpretations To: sc22wg5@dkuug.dk Date: Mon, 7 Aug 2000 13:48:39 -0500 (CDT) X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Yes No Number Title --- -x- 000067 Writing zeros This is an incompatable change with F77 and F90. The change could be made to F2k, but should not be made as a "fix" to F95. --- -x- 000068 Asterisks as I/O units As with interpretation 67, this is an incompatable change and will causes implementations to no longer be standard conforming. This change should not be made as an interpretation to an existing standard but may be made to a future (F2K) standard. The change to specify that there are specific unit numbers attached to the asterisk units and that they may appear in OPEN and CLOSE statements is extending the standard. The standard does not indicate the unit attached to the asterisk must be zero or positive. Only integer unit numbers must be zero or positive. In section 9.3 FILE CONNECTION, an io_unit is either an external-file unit, an asterisk, or an internal-file-unit. The external file unit is a scalar-int-expr. ...An external unit is used to refer to an external file and is specified by an external-file-unit or an asterisk. ... A scalar integer expression that identifies an external file unit shall be zero or positive. An asterisk identifies particular processor-dependent external units that are preconnected for formatted sequential access (9.4.4.2). The standard indicates in section 9.4.4.2 IDENTIFYING a UNIT that: ...A READ statement that does not contain an input/control list specifies a particular processor-dependent unit, which is the same as the unit identified by * in a READ statement that contains an input/output control list. The PRINT statement specifies some other processor-dependent unit, which is the same as the unit identified by * in a WRITE statement. Thus, each data transfer input/output statement identifies an external unit or an internal file. We disagree with answers 2 and 3. The answers to the questions should be: 2) Yes. The unit identified by * is not a normal unit (it is implementation defined) and thus does not fall under the restriction of 9.3.2 as cited in the discussion. 3) No. The units specified by asterisks are not normal units (implementation defined) and do not necessarily correspond to numbered units accessible to the user, and thus do not fall under this restriction. -x- --- 000069 What is a numeric character? -c- --- 000070 Asymmetry between constant specification and initialization expressions See Henry's comments. -x- --- 000071 Character array constructors -x- --- 000072 Resolving generic procedure references -x- --- 000076 INTENT(IN) dummy arguments and implied DO loops -x- --- 000077 INTENT(IN) dummy arguments and NULLIFY -x- --- 000079 Pointer Assignment and Allocatable Arrays -x- --- 000080 Host association and the EXTERNAL attribute -x- --- 000082 Usage of BOZ literal constants -x- --- 000083 Scope of array-constructor implied-DO variable -x- --- 000084 Events that cause variables to be defined Part 2: -x- --- F90/000100 ASSOCIATED intrinsic and zero-sized objects -x- --- F90/000179 DO variable with POINTER attribute -x- --- F90/000185 What is the allocation status of an array after an allocation failure? -x- --- F90/000194 Statements between SELECT CASE and CASE