From owner-sc22wg5+sc22wg5-dom8=www.open-std.org@open-std.org  Thu Mar 17 14:07:45 2016
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 E98A93571CA; Thu, 17 Mar 2016 14:07:44 +0100 (CET)
Delivered-To: sc22wg5@open-std.org
X-Greylist: delayed 671 seconds by postgrey-1.34 at www5.open-std.org; Thu, 17 Mar 2016 14:07:43 CET
Received: from esa2.cray.iphmx.com (esa2.cray.iphmx.com [68.232.143.164])
	(using TLSv1 with cipher RC4-SHA (128/128 bits))
	(No client certificate requested)
	by www.open-std.org (Postfix) with ESMTP id D710D356D1C
	for <sc22wg5@open-std.org>; Thu, 17 Mar 2016 14:07:43 +0100 (CET)
DomainKey-Signature: s=cray1024; d=cray.com; c=nofws; q=dns;
  h=X-IronPort-AV:X-Cray-OBMMKR:Received:Received:Received:
   From:To:CC:Subject:Thread-Topic:Thread-Index:Date:
   Message-ID:References:In-Reply-To:Accept-Language:
   Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator:
   x-originating-ip:Content-Type:Content-ID:
   Content-Transfer-Encoding:MIME-Version:Return-Path;
  b=ibKtqFgDzbDi1QAy/g+geyt9MPaDZ12CWSzTW+A9sB73hkz5D0LT6QDr
   uk8iivxTAeZ4ynlKr4Lf9mKvu7zK98emnSTwZ2FATa/nGIvl6kDFvdd/I
   uauaHbtOZ4QMp3A+BZe8ZBUaawaIR77AGIwmS6EfquNVImu9WdP3dQku/
   8=;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;
  d=cray.com; i=@cray.com; q=dns/txt; s=cray1024;
  t=1458220064; x=1489756064;
  h=from:to:cc:subject:date:message-id:references:
   in-reply-to:content-id:content-transfer-encoding:
   mime-version;
  bh=I07vYlU7X+ee1nKYf+nCuAhLB+qXKhrG+GUsF8/nJmA=;
  b=odIp2e/6vTItI6TXPlcdwNbde8imCRZu7FEycNgAW4HHQY+zrgtmq0Ce
   3IL8x7q1aTy4srhYqUT1v99CIk1CinGItceWbDvpP3rFfCF+LeBr62qXB
   OCXqN2isEJbnP54iQWHoXpL++tUeNNtiXkpyH/Nz8DMlp+CwREsnLXzGj
   k=;
X-IronPort-AV: E=Sophos;i="5.24,350,1454976000"; 
   d="scan'208";a="7756091"
X-Cray-OBMMKR: 1433258124 7756091
Received: from cray-smtp-2.cray.com (HELO CFWEX01.americas.cray.com) ([136.162.34.11])
  by esa2.cray.iphmx.com with ESMTP/TLS/AES256-SHA; 17 Mar 2016 12:56:23 +0000
Received: from CFWEXHYBRID.americas.cray.com (172.30.88.178) by
 CFWEX01.americas.cray.com (172.30.88.25) with Microsoft SMTP Server (TLS) id
 14.3.224.2; Thu, 17 Mar 2016 07:56:22 -0500
Received: from CFWEX01.americas.cray.com ([169.254.1.224]) by
 cfwexhybrid.americas.cray.com ([::1]) with mapi id 14.03.0224.002; Thu, 17
 Mar 2016 07:56:21 -0500
From: Bill Long <longb@cray.com>
To: fortran standards email list for J3 <j3@mailman.j3-fortran.org>
CC: WG5 <sc22wg5@open-std.org>
Subject: Re: (j3.2006) (SC22WG5.5689) [ukfortran]  AW: RE:  F08/C201
Thread-Topic: (j3.2006) (SC22WG5.5689) [ukfortran]  AW: RE:  F08/C201
Thread-Index: AQHRgBFoUNqshxAgXUKJjsgaiUBI4p9d7IgA
Date: Thu, 17 Mar 2016 12:56:20 +0000
Message-ID: <EAE9828B-FDE6-4C17-BA0F-FBA4B093DA65@cray.com>
References: <20160314163910.3E1A035730E@www.open-std.org><20160315002027.D448E3582CC@www.open-std.org><20160315200858.1DA5E3587BB@www.open-std.org><20160316075309.C2B803571CA@www.open-std.org>
 <20160316131948.4819C357127@www.open-std.org>
 <20160317055338.21A253584A2@www.open-std.org>
In-Reply-To: <20160317055338.21A253584A2@www.open-std.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.31.22.59]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <81D29273B82FB743B56E9FF97A7EAC05@cray.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Sender: owner-sc22wg5@open-std.org
Precedence: bulk

When I first read through this, it appeared that C201 was just not adjusted=
 to account for the new BLOCK construct.  It seems like the simplest fix, w=
ith the least danger of causing problems elsewhere, would be minimal exclus=
ion:  Change the beginning of C201 to =93Except as part of an <interface-bl=
ock> contained in a <block-construct>, an <execution-part>...=94

Cheers,
Bill


On Mar 17, 2016, at 12:54 AM, Cohen Malcolm <malcolm@nag-j.co.jp> wrote:

> The way that the end statements are counted in <action-stmt> and C201=20
> excludes them from appearing as executable constructs is at best confusin=
g,=20
> whether it is technically wrong or not.
>=20
> FWIW, on close examination I do think it probably is technically wrong, a=
s=20
> the end statement (does not need "subroutine" - that is an optional keywo=
rd=20
> in this context) in the interface body in the BLOCK construct is indeed=20
> reached via executable-construct.
>=20
> Not that a compiler is likely to take that interpretation.
>=20
> This could be patched by modifying C201, but since this looks like a very=
=20
> confusing way of describing the grammer anyway, I would be more in favour=
 of=20
> getting the end statements out of action-stmt and inserting them as=20
> necessary elsewhere, unless that turns out to be more difficult than it=20
> looks.  We would certainly want to be very careful how we change this=20
> otherwise the chance of incidental BNF breakage would be quite high.
>=20
> Cheers,
>=20
> -----Original Message-----=20
> From: Robert Corbett
> Sent: Wednesday, March 16, 2016 9:04 PM
> To: fortran standards email list for J3
> Cc: Forcheck ; Bader, Reinhold ; 'WG5'
> Subject: [ukfortran] (SC22WG5.5686) (j3.2006) AW: RE: F08/C201
>=20
> On 03/16/16 00:46, Bader, Reinhold wrote:
>> Hi Erik,
>>=20
>> my impression is that C201 only closes a hole that would otherwise permi=
t=20
>> improper nesting of statements with respect to executable constructs,=20
>> e.g.,
>>=20
>> block
>>    ...
>>    end subroutine
>> end block
>>=20
>> Cheers
>> Reinhold
>>=20
>=20
> You and Erik raise a fair point.  Constraint C201 has the same effect on =
the
> syntax as would be achieved by deleting the alternatives=20
> /end-function-stmt/,
> /end-mp-subprogram-stmt/, /end-program-stmt/, and /end-subroutine-stmt/ f=
rom
> rule R214 (rule R215 of 16-007), which is the syntax definition of an
> /action-stmt/.  I suspect that the intended purpose of including those
> alternatives is to indicate that those forms of END statements are=20
> executable
> constructs.  That does not work, because none of the cases where one of=20
> those
> forms of END statements is produced by the grammar are derived (indirectl=
y)=20
> from
> the syntax term /executable-construct/ because of the constraint.
>=20
> Robert Corbett
>=20
> _______________________________________________
> ukfortran mailing list
> http://lists.accu.org/mailman/listinfo/ukfortran
>=20
> --=20
> ........................Malcolm Cohen, Nihon NAG, Tokyo.=20
>=20
> _______________________________________________
> J3 mailing list
> J3@mailman.j3-fortran.org
> http://mailman.j3-fortran.org/mailman/listinfo/j3

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


