From owner-sc22wg5@open-std.org  Thu Jan 22 22:42:02 2009
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 18BD3CA5FED; Thu, 22 Jan 2009 22:42:02 +0100 (CET)
X-Original-To: sc22wg5@open-std.org
Delivered-To: sc22wg5@open-std.org
Received: from mail.jpl.nasa.gov (sentrion2.jpl.nasa.gov [128.149.139.106])
	by www2.open-std.org (Postfix) with ESMTP id EAF82CA5FE6
	for <sc22wg5@open-std.org>; Thu, 22 Jan 2009 22:42:00 +0100 (CET)
Received: from mprox2.jpl.nasa.gov (mprox2.jpl.nasa.gov [137.78.160.141])
	by mail.jpl.nasa.gov (Switch-3.3.2mp/Switch-3.3.2mp) with ESMTP id n0MLfnL3011510;
	Thu, 22 Jan 2009 21:41:49 GMT
Received: from [137.79.7.57] (math.jpl.nasa.gov [137.79.7.57])
	(authenticated bits=0)
	by mprox2.jpl.nasa.gov (Switch-3.2.6/Switch-3.2.6) with ESMTP id n0MLflEv004849
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Thu, 22 Jan 2009 13:41:48 -0800
Subject: Re: (j3.2006) (SC22WG5.3891) [MPI3 Fortran] [ukfortran] [MPI3
	Fortran] MPI non-blocking transfers
From: Van Snyder <Van.Snyder@jpl.nasa.gov>
Reply-To: Van.Snyder@jpl.nasa.gov
To: "longb@cray.com" <longb@cray.com>,
	fortran standards email list for J3 <j3@j3-fortran.org>
Cc: WG5 <sc22wg5@open-std.org>,
	"mpi3-fortran@lists.mpi-forum.org" <mpi3-fortran@lists.mpi-forum.org>
In-Reply-To: <4978C20F.2070207@cray.com>
References: <Prayer.1.3.1.0901211104060.5654@hermes-2.csi.cam.ac.uk>
	 <20090122100652.C31E9CA3434@www2.open-std.org>	<4978A8A0.8090407@cray.com>
	 <20090122175730.8BA1BCA3439@www2.open-std.org>  <4978C20F.2070207@cray.com>
Content-Type: text/plain
Organization: Yes
Date: Thu, 22 Jan 2009 13:41:47 -0800
Message-Id: <1232660507.15119.842.camel@math.jpl.nasa.gov>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.3 (2.12.3-8.el5_2.3) 
Content-Transfer-Encoding: 7bit
X-Source-IP: math.jpl.nasa.gov [137.79.7.57]
X-Source-Sender: Van.Snyder@jpl.nasa.gov
X-AUTH: Authorized
Sender: owner-sc22wg5@open-std.org
Precedence: bulk


On Thu, 2009-01-22 at 10:59 -0800, Bill Long wrote:
> When we're talking about a Fortran's asynchronous
> attribute, it seems reasonable to relate it to Fortran's concept of
> I/O.

When a Fortran program invokes an external procedure with an actual
argument that has the ASYNCHRONOUS attribute, and all you have for the
external procedure is a .o file, how does the compiler know whether the
procedure does Fortran I/O, or something else?