From owner-sc22wg5@open-std.org Tue Dec 9 20:23:47 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 86089CA343D; Tue, 9 Dec 2008 20:23:47 +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 10340CA3439 for ; Tue, 9 Dec 2008 20:23:44 +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 mB9JNgxD020390 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 9 Dec 2008 13:23:42 -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 mB9JNfuF016622; Tue, 9 Dec 2008 13:23:41 -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); Tue, 9 Dec 2008 13:23:41 -0600 Message-ID: <493EC640.1060304@cray.com> Date: Tue, 09 Dec 2008 13:25:52 -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: WG5 Subject: Re: (j3.2006) (SC22WG5.3799) [ukfortran] N1761, TYPE(*), BIND(C) and arrays References: <20081127193527.EF00DC178D9@www2.open-std.org> <20081209172327.D05AFC178D6@www2.open-std.org> <20081209184656.288E8CA3439@www2.open-std.org> <20081209185450.B4B95CA3439@www2.open-std.org> In-Reply-To: <20081209185450.B4B95CA3439@www2.open-std.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 09 Dec 2008 19:23:41.0192 (UTC) FILETIME=[A4D36880:01C95A33] X-Cray-VirusStatus: clean Sender: owner-sc22wg5@open-std.org Precedence: bulk Aleksandar Donev wrote: > On Tuesday 09 December 2008 10:46, N.M. Maclaren wrote: > >> In other words, N1761 has started to use the term "assumed-shape" to >> refer to actual arguments, without specifying what it means when used >> like that. >> > I only found this one sentence where that was the case, and that > sentence simply needs to be fixed by replacing "object" with "dummy > argument". All the other appearences of "assumed-shape" in N1761 are > prefixed or suffixed with dummy argument. I just grepped. > "A <> is an structure used by the processor to > describe an object that is assumed-shape, assumed-rank, allocatable, > or a data pointer." > The "object" here is intentional. Assumed-shape and assumed-rank objects are automatically dummy arguments; it's not really necessary to restate that fact. However, C programmers can create new allocatable or pointer arrays that are then passed as actual arguments to a Fortran library routine, for example. In this case, the associated Fortran descriptor is representing an actual argument, not a dummy argument. The C programmer can also create a descriptor for an array section that could be passed to a Fortran library routine that has a corresponding assumed-shape dummy. Perhaps more examples would be helpful. Indeed, when we get to actual edits, I think healthy additions to Annex C would be useful. (As suggested by Reinhold.) Cheers, Bill > Is this one mistaken sentence really the cause of such alarm? It is very > easy to find issues with something you dislike and blow them out of > proportion. It is not constructive. Notice how my answers to Reinhold's > posts are much more cooperative---at least I can understand what he is > asking and why. I have yet to understand exactly what you are irked > about. > > Best, > Aleks > _______________________________________________ > 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., 1340 Mendota Heights Rd., Mendota Heights, MN, 55120