From owner-sc22wg5@open-std.org Mon Dec 8 20:44:31 2008 Return-Path: X-Original-To: sc22wg5-dom7 Delivered-To: sc22wg5-dom7@www2.open-std.org Received: by www2.open-std.org (Postfix, from userid 521) id 4DE13C178DA; Mon, 8 Dec 2008 20:44:31 +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.0.111]) by www2.open-std.org (Postfix) with ESMTP id 3402EC178D6 for ; Mon, 8 Dec 2008 20:44:29 +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 mB8JiDTH008504 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 8 Dec 2008 13:44:21 -0600 (CST) Received: from CFEXFE01.us.cray.com (cfexfe01.us.cray.com [172.30.74.93]) by beaver.us.cray.com (8.13.8/8.13.3/hub-5273) with ESMTP id mB8JiCoA001664; Mon, 8 Dec 2008 13:44:12 -0600 Received: from mh-dhcp-172-31-16-160.us.cray.com ([172.31.16.160]) by CFEXFE01.us.cray.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Mon, 8 Dec 2008 13:44:12 -0600 Message-ID: <493D798F.9020308@cray.com> Date: Mon, 08 Dec 2008 13:46:23 -0600 From: Bill Long Reply-To: longb@cray.com Organization: Cray Inc. User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: fortran standards email list for J3 Cc: "Undisclosed.Recipients: ;"@cray.com, WG5 Subject: Re: (j3.2006) (SC22WG5.3762) Response on the TR29113 draft N1761 References: <20081207203535.92039C178D6@www2.open-std.org> <493D5649.3000706@cray.com> <20081208182510.DA417C178E4@www2.open-std.org> In-Reply-To: <20081208182510.DA417C178E4@www2.open-std.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 08 Dec 2008 19:44:12.0385 (UTC) FILETIME=[5842CD10:01C9596D] X-Cray-VirusStatus: clean Sender: owner-sc22wg5@open-std.org Precedence: bulk Aleksandar Donev wrote: > On Monday 08 December 2008 09:15, Bill Long wrote: > >> Issue 6 - referencing or defining assumed rank entities: >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> >> We need some rules to deal with this. >> >> There are rules currently - basically that the only thing allowed on >> the Fortran side is to pass an assumed-rank dummy as an actual >> argument to another procedure. Are you saying that the scope of the >> TR needs to be expanded to specify ways for things like this to be >> used in Fortran? >> > Reinhold suggested a SELECT RANK construct. It does seem reasonable and > not hard for either vendors or the standard, and it is safe to use. > I did not intend to suggest that this was a bad idea. However, I'm concerned about adding features at this stage, unless the argument is especially strong. There is a possibility of pitfalls not seen right away, and a general need to reach closure on the TR content. Something like this seems like a reasonable proposal for Fortran 2013. Cheers, Bill -- Bill Long longb@cray.com Fortran Technical Support & voice: 651-605-9024 Bioinformatics Software Development fax: 651-605-9142 Cray Inc., 1340 Mendota Heights Rd., Mendota Heights, MN, 55120