From owner-sc22wg5+sc22wg5-dom8=www.open-std.org@open-std.org  Wed Oct 19 05:51:43 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 453C1356910; Wed, 19 Oct 2011 05:51:42 +0200 (CEST)
Delivered-To: sc22wg5@open-std.org
Received: from ns.nag-j.co.jp (218-42-159-107.cust.bit-drive.ne.jp [218.42.159.107])
	by www.open-std.org (Postfix) with ESMTP id 866213568F5
	for <sc22wg5@open-std.org>; Wed, 19 Oct 2011 05:51:42 +0200 (CEST)
Received: from 218-42-159-108.cust.bit-drive.ne.jp ([218.42.159.108] helo=Maru6)
	by ns.nag-j.co.jp with smtp (Exim 4.50)
	id 1RGNBs-0007FU-3T
	for sc22wg5@open-std.org; Wed, 19 Oct 2011 12:51:40 +0900
Message-ID: <CF25C909434449328D24A5755E9CBCB2@Maru6>
From: "Malcolm Cohen" <malcolm@nag-j.co.jp>
To: "WG5" <sc22wg5@open-std.org>
Subject: Re: (SC22WG5.4567) WG5 letter ballot 2 on Fortran 2008interpretations
Date: Wed, 19 Oct 2011 12:51:42 +0900
Organization: =?UTF-8?B?5pel5pysTkFH?=
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="UTF-8";
	reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 15.4.3538.513
X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3538.513
Sender: owner-sc22wg5@open-std.org
Precedence: bulk

Reinhold Bader further writes
<<<

F08/0047  The discussion of the interp (which was rather shortened down
          compared to the original paper) says that
          "The PUBLIC statement at A contradicts the PRIVATE attribute at
           B which violates the standard."

          If this refers to the constraint C514 I conclude that my vote
          must be "NO", since we're talking about two entities here, one
          being the type definition and the other one being the generic.

          It appears that the situation that use-name and generic-spec
          in R525 can be the same has not been adequately addressed.
>>>

You can vote no, but the answer is still that you have specified both PUBLIC FOO
and PRIVATE FOO and that is not allowed.  FOO the identifier is a single entity
no matter how many other entities can be accessed by FOO.

Don't just stop reading when you reach the end of C514, keep going and read
5.3.2p2 - it is explicit stated that accessibility applies to identifiers.

We have had identifiers being usable to access multiple entities since F90, this
is not a new issue and is completely covered by the existing text in the
standard.

Cheers,
-- 
................................Malcolm Cohen, Nihon NAG, Tokyo.

-- 
................................Malcolm Cohen, Nihon NAG, Tokyo. 

