From owner-sc22wg5+sc22wg5-dom8=www.open-std.org@open-std.org Tue May 28 08:43:12 2013 Return-Path: X-Original-To: sc22wg5-dom8 Delivered-To: sc22wg5-dom8@www.open-std.org Received: by www.open-std.org (Postfix, from userid 521) id 8DEB4356EBF; Tue, 28 May 2013 08:43:11 +0200 (CEST) Delivered-To: sc22wg5@open-std.org Received: from postout.lrz.de (postout.lrz.de [129.187.254.115]) by www.open-std.org (Postfix) with ESMTP id 162593568E8 for ; Tue, 28 May 2013 08:42:54 +0200 (CEST) Received: from lxmhs51.srv.lrz.de (localhost [127.0.0.1]) by postout3.mail.lrz.de (Postfix) with ESMTP id D55402009E for ; Tue, 28 May 2013 08:42:53 +0200 (CEST) X-Virus-Scanned: by amavisd-new at lrz.de in lxmhs51.srv.lrz.de Received: from postout3.mail.lrz.de ([127.0.0.1]) by lxmhs51.srv.lrz.de (lxmhs51.srv.lrz.de [127.0.0.1]) (amavisd-new, port 20024) with LMTP id xh0Gtx2gecni for ; Tue, 28 May 2013 08:42:53 +0200 (CEST) Received: from BADWLRZ-SWHBT2.ads.mwn.de (BADWLRZ-SWHBT2.ads.mwn.de [IPv6:2001:4ca0:0:108::126]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "BADWLRZ-SWHBT2", Issuer "BADWLRZ-SWHBT2" (not verified)) by postout3.mail.lrz.de (Postfix) with ESMTPS id 2AA1E2007B for ; Tue, 28 May 2013 08:42:53 +0200 (CEST) Received: from BADWLRZ-SWMBX11.ads.mwn.de ([fe80::6de5:ff8b:1900:b1a1]) by BADWLRZ-SWHBT2.ads.mwn.de ([fe80::5951:9dc3:7b2b:14ba%13]) with mapi id 14.03.0123.003; Tue, 28 May 2013 08:42:52 +0200 From: "Bader, Reinhold" To: WG5 Subject: AW: (j3.2006) (SC22WG5.5001) Corrections to TS29113 Thread-Topic: (j3.2006) (SC22WG5.5001) Corrections to TS29113 Thread-Index: Ac5bEYgUanoOou6iQ5eLKlUSgXFEov///qqA//9IO7A= Date: Tue, 28 May 2013 06:42:52 +0000 Message-ID: <166ED263DF83324D9A3BA67FB6772B2B59F9F38C@BADWLRZ-SWMBX11.ads.mwn.de> References: <20130527194800.755D0356E40@www.open-std.org> In-Reply-To: Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [2001:4ca0:0:300::79] Content-Type: multipart/related; boundary="_004_166ED263DF83324D9A3BA67FB6772B2B59F9F38CBADWLRZSWMBX11a_"; type="multipart/alternative" MIME-Version: 1.0 Sender: owner-sc22wg5@open-std.org Precedence: bulk --_004_166ED263DF83324D9A3BA67FB6772B2B59F9F38CBADWLRZSWMBX11a_ Content-Type: multipart/alternative; boundary="_000_166ED263DF83324D9A3BA67FB6772B2B59F9F38CBADWLRZSWMBX11a_" --_000_166ED263DF83324D9A3BA67FB6772B2B59F9F38CBADWLRZSWMBX11a_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello Daniel, Von: j3-bounces@mailman.j3-fortran.org [mailto:j3-bounces@mailman.j3-fortra= n.org] Im Auftrag von Daniel C Chen Gesendet: Montag, 27. Mai 2013 23:32 An: fortran standards email list for J3 Cc: WG5; j3-bounces@mailman.j3-fortran.org; Bill Long Betreff: Re: (j3.2006) (SC22WG5.5001) Corrections to TS29113 "(A) Assumed rank entities. The Fortran lower bounds of an assumed-rank dummy argument that does not ha= ve the POINTER or ALLOCATABLE attribute should be one. EDIT to TS29113: In section 6.3, end of para 1, insert "If the actual argument is a non-pointer non-allocatable array, the lower b= ounds of the dummy argument have the value one." FIXME: corresponding edit in section 9.7 is needed." An assumed-rank entity is a nonallocatable and nonpointer entity. No, it is also permitted for it to have the POINTER or ALLOCATABLE attribut= e. As long as the corresponding actual argument is an array, the lower bounds = of the assumed-rank dummy argument have the value one. I am not sure if the proposed edit to 6.3 covers this as if the dummy argum= ent is not assumed-rank, for instance, it can be explicit shape with low bo= unds declared other than one. To my understanding, all restrictions in paragraph 1 of 6.3 presuppose assu= med-rank dummy entities. Daniel XL Fortran Development - IBM Toronto Software Lab Phone: 905-413-3056 Tie: 969-3056 Email: cdchen@ca.ibm.com http://www.ibm.com/software/awdtools/fortran/xlfortran [Inactive hide details for "Bader, Reinhold" ---05/27/2013 15:50:16---Hello= Bill, based on Tobias' implementation experience as]"Bader, Reinhold" ---= 05/27/2013 15:50:16---Hello Bill, based on Tobias' implementation experien= ce as well as observations by others, I have as From: "Bader, Reinhold" > To: Bill Long >, Cc: WG5 > Date: 05/27/2013 15:50 Subject: (j3.2006) (SC22WG5.5001) Corrections to TS29113 Sent by: j3-bounces@mailman.j3-fortran.org ________________________________ Hello Bill, based on Tobias' implementation experience as well as observations by other= s, I have assembled a "fix paper draft" for a number of glitches and omissions to the interop T= S. Since you were going to write a paper on a minor extension anyway (cf. item "D" in the attached draft), the= question is whether to put all this into one paper, or to write a number of separate ones. Further= more, feedback on the suggestions in the draft is welcome. Best wishes Reinhold [attachment "ts29113_corrections.txt" deleted by Daniel C Chen/Toronto/IBM]= _______________________________________________ J3 mailing list J3@mailman.j3-fortran.org http://mailman.j3-fortran.org/mailman/listinfo/j3 --_000_166ED263DF83324D9A3BA67FB6772B2B59F9F38CBADWLRZSWMBX11a_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello Daniel,

&nbs= p;

Von: j3-bounces@mailman.j3-fortran.org [mailto:j3-bounces@mailman.j3-fortran.or= g] Im Auftrag von Daniel C Chen
Gesendet: Montag, 27. Mai 2013 23:32
An: fortran standards email list for J3
Cc: WG5; j3-bounces@mailman.j3-fortran.org; Bill Long
Betreff: Re: (j3.2006) (SC22WG5.5001) Corrections to TS29113

&nbs= p;

"(A) Assumed rank entities. The Fortran lower bounds of an = assumed-rank dummy argument that does not have the POINTER or ALLOCATABLE a= ttribute should be one.
EDIT to TS29113:
In section 6.3, end of para 1, = insert
"If the actual argument is= a non-pointer non-allocatable array, the lower bounds of the dummy argumen= t have the value one."
FIXME: corresponding edit in se= ction 9.7 is needed."


An assumed-rank entity is a non= allocatable and nonpointer entity.

No, it is also permitted for it to have the POINTER or ALLOCATABLE attribute.<= o:p>

 

As long as the corresponding actual argument is an array, the lower bou= nds of the assumed-rank dummy argument have the value one.
I am not sure if the proposed edit to 6.3 covers this = as if the dummy argument is not assumed-rank, for instance, it can be expli= cit shape with low bounds declared other = than one.

To my understanding, all restrictions in paragraph 1 of 6.3 presuppose assume= d-rank dummy entities.



Daniel


XL Fortran Development - IBM Toronto Software Lab
Phone: 905-413-3056  
Tie: 969-3056  
Email: cdchen@ca.ibm.com=
h= ttp://www.ibm.com/software/awdtools/fortran/xlfortran

3D"Inactive= "Bader, Reinhold" ---05/27/2013 15:50:16---Hello Bill,  based on Tobias'= implementation experience as well as observations by others, I have as

From: "Bader, Reinhold" <Reinhold.Bader@lrz.de>
To: Bill Long <longb@cray.com>,
Cc: WG5 <sc22wg5@open-std.org>
Date: 05/27/2013 15:50
Subject: (j3.2006) (SC22WG5.5001) Corrections to TS29= 113
Sent by: j3-bounces@mailm= an.j3-fortran.org<= /span>




Hello Bill,

based on Tobias' implementation experience as well as observations by o= thers, I have assembled
a "fix paper draft" for a number of glitches and omissions to= the interop TS. Since you were going to write a
paper on a minor extension anyway (cf. item "D" in the attach= ed draft), the question is whether to
put all this into one paper, or to write a number of separate ones. Fur= thermore, feedback on the
suggestions in the draft is welcome.

Best wishes
Reinhold


[attachment "ts29113_corrections.txt" deleted by Daniel C Che= n/Toronto/IBM] _______________________________________________
J3 mailing list
J3@mailman.j3-fortran.org<= span style=3D"mso-bookmark:_MailOriginal">
http://mailman.j3-fortr= an.org/mailman/listinfo/j3

--_000_166ED263DF83324D9A3BA67FB6772B2B59F9F38CBADWLRZSWMBX11a_-- --_004_166ED263DF83324D9A3BA67FB6772B2B59F9F38CBADWLRZSWMBX11a_ Content-Type: image/gif; name="image001.gif" Content-Description: image001.gif Content-Disposition: inline; filename="image001.gif"; size=105; creation-date="Tue, 28 May 2013 06:42:52 GMT"; modification-date="Tue, 28 May 2013 06:42:52 GMT" Content-ID: Content-Transfer-Encoding: base64 R0lGODlhEAAQAKECAMzMzAAAAP///wAAACH5BAEAAAIALAAAAAAQABAAAAIXlI+py+0PopwxUbpu ZRfKZ2zgSJbmSRYAIf4fT3B0aW1pemVkIGJ5IFVsZWFkIFNtYXJ0U2F2ZXIhAAA7 --_004_166ED263DF83324D9A3BA67FB6772B2B59F9F38CBADWLRZSWMBX11a_--