From owner-sc22wg5+sc22wg5-dom8=www.open-std.org@open-std.org  Tue Dec 13 10:20:54 2011
Return-Path: <owner-sc22wg5+sc22wg5-dom8=www.open-std.org@open-std.org>
X-Original-To: sc22wg5-dom8
Delivered-To: sc22wg5-dom8@www.open-std.org
Received: by www.open-std.org (Postfix, from userid 521)
	id DFC35356953; Tue, 13 Dec 2011 10:20:53 +0100 (CET)
Delivered-To: sc22wg5@open-std.org
X-Greylist: delayed 2128 seconds by postgrey-1.34 at www5.open-std.org; Tue, 13 Dec 2011 10:20:52 CET
Received: from rcsinet14.oracle.com (rcsinet14.oracle.com [148.87.113.126])
	by www.open-std.org (Postfix) with ESMTP id 5F3FB356944
	for <sc22wg5@open-std.org>; Tue, 13 Dec 2011 10:20:51 +0100 (CET)
Received: from rcsinet15.oracle.com (rcsinet15.oracle.com [148.87.113.117])
	by rcsinet14.oracle.com (Switch-3.4.4/Switch-3.4.1) with ESMTP id pBD8jPiN015465
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK)
	for <sc22wg5@open-std.org>; Tue, 13 Dec 2011 08:45:25 GMT
Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94])
	by rcsinet15.oracle.com (Switch-3.4.4/Switch-3.4.4) with ESMTP id pBD8jHVK029714
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK)
	for <sc22wg5@open-std.org>; Tue, 13 Dec 2011 08:45:18 GMT
Received: from acsmt357.oracle.com (acsmt357.oracle.com [141.146.40.157])
	by ucsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id pBD8jG1S015101
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <sc22wg5@open-std.org>; Tue, 13 Dec 2011 08:45:17 GMT
Received: from abhmt107.oracle.com (abhmt107.oracle.com [141.146.116.59])
	by acsmt357.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id pBD8jBTg007673
	for <sc22wg5@open-std.org>; Tue, 13 Dec 2011 02:45:11 -0600
Received: from [10.132.140.77] (/10.132.140.77)
	by default (Oracle Beehive Gateway v4.0)
	with ESMTP ; Tue, 13 Dec 2011 00:45:11 -0800
Message-ID: <4EE71039.4030203@oracle.com>
Date: Tue, 13 Dec 2011 00:43:37 -0800
From: Robert Corbett <robert.corbett@oracle.com>
Reply-To: robert.corbett@oracle.com
Organization: Oracle America
User-Agent: Mozilla/5.0 (X11; SunOS sun4u; rv:6.0) Gecko/20110814 Thunderbird/6.0
MIME-Version: 1.0
CC: WG5 <sc22wg5@open-std.org>
Subject: Re: (j3.2006) (SC22WG5.4586) Corrigendum 1
References: <20111115103238.7CF7A3568EC@www.open-std.org>
In-Reply-To: <20111115103238.7CF7A3568EC@www.open-std.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Source-IP: ucsinet22.oracle.com [156.151.31.94]
X-CT-RefId: str=0001.0A090207.4EE7109E.0181,ss=1,re=0.000,fgs=0
Sender: owner-sc22wg5@open-std.org
Precedence: bulk

I vote

2)  Yes, but I recommend the following changes.

on the question "Is N1893, with the references and notes
removed, acceptable for submission to SC22 for publication
as Corrigendum 1 for Fortran 2008?"

I too wish to thank John and David for producing this
corrigendum.

Robert Corbett
representing Oracle America

------------------------------------------------------

I realize that the issues I am raising here should have
been raised earlier.  I do not expect any changes to be
made either now or subsequently as a result of these
comments.

In the first edit for the Introduction, the form of the
proposed sentence differs from the form of the sentences
already present in the cited paragraph.  The sentence

     An array or an object with a nonconstant length
     type parameter can have the VALUE attribute.

is more in line with the existing sentences.

In the second edit for the Introduction, the word "may"
in the proposed edit should, perhaps, be "can".

In the edits for Subclause 1.6.2, the final sentence of
the second new paragraph could be clearer.  The
alternative sentence

     This part of ISO/IEC specifies that an
     INTENT(OUT) argument of a pure subroutine
     shall not be polymorphic.

is clearer, though wordier.

There might be a problem with the edit for Subclause 5.5.
If a derived type definition appears in the specification
part of a BLOCK construct, the edits provided appear to
say that the scope of a data entity implicitly declared
in the derived type definition is the BLOCK construct.
The BLOCK construct would be the host of the scope that
is the derived type definition.
