From owner-sc22wg5@open-std.org  Wed Feb 10 01:50:57 2010
Return-Path: <owner-sc22wg5@open-std.org>
X-Original-To: sc22wg5-dom8
Delivered-To: sc22wg5-dom8@www2.open-std.org
Received: by www2.open-std.org (Postfix, from userid 521)
	id B2955C3BA32; Wed, 10 Feb 2010 01:50:57 +0100 (CET)
X-Original-To: sc22wg5@open-std.org
Delivered-To: sc22wg5@open-std.org
Received: from mail1.cray.com (mail1.cray.com [136.162.62.100])
	by www2.open-std.org (Postfix) with ESMTP id EA13CC3BA23
	for <sc22wg5@open-std.org>; Wed, 10 Feb 2010 01:50:55 +0100 (CET)
Received: from beaver.us.cray.com (beaver.us.cray.com [172.30.74.51])
	by mail1.cray.com (8.13.6/8.13.3/gw-5323) with ESMTP id o1A0hNQu001736
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 9 Feb 2010 18:43:24 -0600 (CST)
Received: from cfexcas01.americas.cray.com (cfexcas-2.us.cray.com [172.30.74.227])
	by beaver.us.cray.com (8.13.8/8.13.3/hub-5273) with ESMTP id o1A0hLXl022582;
	Tue, 9 Feb 2010 18:43:22 -0600
Received: from fortran.us.cray.com (172.31.19.200) by
 cfexcas01.americas.cray.com (172.30.74.226) with Microsoft SMTP Server (TLS)
 id 8.1.393.1; Tue, 9 Feb 2010 18:43:21 -0600
Message-ID: <4B720138.7030506@cray.com>
Date: Tue, 9 Feb 2010 18:43:36 -0600
From: Bill Long <longb@cray.com>
Reply-To: <longb@cray.com>
Organization: Cray Inc.
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: fortran standards email list for J3 <j3@j3-fortran.org>
Cc: "sc22wg5@open-std.org" <sc22wg5@open-std.org>
Subject: Re: (j3.2006) (SC22WG5.4157) Urgent: letter ballot on interps - comment
 on a comment
References: <20100205115844.6D657C3BA06@www2.open-std.org>
In-Reply-To: <20100205115844.6D657C3BA06@www2.open-std.org>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit
X-Cray-VirusStatus: clean
Sender: owner-sc22wg5@open-std.org
Precedence: bulk


In preparing my Ballot, I was tempted to add a Comment stating the 
observations below, but I would end up Commenting that there should be 
no change in the interp, which seemed odd.  So, I'm replying to David's 
ballot instead.  (I did agree with all of David's other comments.)


David Muxworthy wrote:

> 
> F03/0138 External <procedure-name> as <proc-target>
> The proposed edit results in rather opaque English.  

Arguably true.

Changing
> "association, referenced" to "association and is referenced" gives a
> slight improvement.  

Perhaps in the flow of speech, but I think it changes the meaning.

The constraint would then be:
> 
>    A <procedure-name> shall be the name of a module or dummy procedure,
>    a specific intrinsic function listed in 13.6 and not marked with a
>    bullet (•), a procedure pointer, or an external procedure that is
>    accessed by USE or host association and is referenced in the scoping
>    unit as a procedure, or that has the EXTERNAL attribute.

I believe that the focus of the interp is that "is referenced in the 
scoping unit as a procedure" should be a standalone qualification in the 
list, and not depend on being accessed by USE or host association.  To 
me, the change suggests that dependence exists.

Cheers,
Bill


> 
> 
> David Muxworthy
> 
> _______________________________________________
> J3 mailing list
> J3@j3-fortran.org
> http://j3-fortran.org/mailman/listinfo/j3

-- 
Bill Long                                           longb@cray.com
Fortran Technical Support    &                 voice: 651-605-9024
Bioinformatics Software Development            fax:   651-605-9142
Cray Inc./Cray Plaza, Suite 210/380 Jackson St./St. Paul, MN 55101


