From owner-sc22wg5@open-std.org  Mon Dec  8 19:17:14 2008
Return-Path: <owner-sc22wg5@open-std.org>
X-Original-To: sc22wg5-dom7
Delivered-To: sc22wg5-dom7@www2.open-std.org
Received: by www2.open-std.org (Postfix, from userid 521)
	id A1023C178E5; Mon,  8 Dec 2008 19:17:14 +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 CB813C178E4
	for <sc22wg5@open-std.org>; Mon,  8 Dec 2008 19:17:12 +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 mB8IHAog004956
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
	Mon, 8 Dec 2008 12:17:11 -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 mB8IH9xS030020;
	Mon, 8 Dec 2008 12:17:09 -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 12:17:09 -0600
Message-ID: <493D6527.7080908@cray.com>
Date: Mon, 08 Dec 2008 12:19:19 -0600
From: Bill Long <longb@cray.com>
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 <j3@j3-fortran.org>
Cc: WG5 <sc22wg5@open-std.org>
Subject: Re: (j3.2006) (SC22WG5.3760) Ballot on the technical content of the
 TR
References: <20081127193527.EF00DC178D9@www2.open-std.org>	<20081208024650.76234C4596C@www2.open-std.org> <20081208175729.BE32FC178E4@www2.open-std.org>
In-Reply-To: <20081208175729.BE32FC178E4@www2.open-std.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 08 Dec 2008 18:17:09.0294 (UTC) FILETIME=[2F0E5CE0:01C95961]
X-Cray-VirusStatus: clean
Sender: owner-sc22wg5@open-std.org
Precedence: bulk



Aleksandar Donev wrote:
> On Sunday 07 December 2008 18:46, Jim Xia wrote:
>
>
>   
>>  Furthermore allowing
>> updates on Fortran descriptors from C programs will likely cause
>> safety issues and also be problematic in consistency check by some
>> vendors.  This becomes a sure way to introduce bugs difficult to
>> diagnose.
>>     
> I do not understand this. You don't want a descriptor TR at all or not? 
> You want something that is "safe"---can you propose such a design 
> please? I find it impossible to imagine how C can pass things to 
> Fortran by descriptor without being allowed to modify the descriptor??? 
> Perhaps you have something else in mind, but the above does not make 
> sense.
>
>
>   

I would add that, intentionally,  the only way provided to change the 
Fortran descriptor is through functions supplied by the vendor.   It is 
allowed, even expected, that the vendor will include error checks in 
these functions to prevent the creation of an invalid Fortran descriptor. 

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