From owner-sc22wg5+sc22wg5-dom8=www.open-std.org@open-std.org  Thu Jun 12 20:06:36 2014
Return-Path: <owner-sc22wg5+sc22wg5-dom8=www.open-std.org@open-std.org>
X-Original-To: sc22wg5-dom8
Delivered-To: sc22wg5-dom8@www.open-std.org
Received: by www.open-std.org (Postfix, from userid 521)
	id C2AA2357246; Thu, 12 Jun 2014 20:06:36 +0200 (CEST)
Delivered-To: sc22wg5@open-std.org
Received: from moene.org (moene.org [80.101.130.238])
	by www.open-std.org (Postfix) with ESMTP id 8117935698F
	for <sc22wg5@open-std.org>; Thu, 12 Jun 2014 20:06:30 +0200 (CEST)
Received: from localhost ([::1])
	by moene.org with esmtp (Exim 4.82_1-5b7a7c0-XX)
	(envelope-from <toon@moene.org>)
	id 1Wv9ON-0005mT-C3; Thu, 12 Jun 2014 20:06:27 +0200
Message-ID: <5399EC23.9030704@moene.org>
Date: Thu, 12 Jun 2014 20:06:27 +0200
From: Toon Moene <toon@moene.org>
Organization: Moene Computational Physics, Maartensdijk, The Netherlands
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Icedove/24.5.0
MIME-Version: 1.0
To: fortran standards email list for J3 <j3@mailman.j3-fortran.org>, 
 WG5 <sc22wg5@open-std.org>
CC: "Whitlock, Stan" <stan.whitlock@intel.com>
Subject: Re: (j3.2006) (SC22WG5.5239) J3 Fortran interp letter ballot #30
 - due 13-Jun-2014
References: <20140508012644.679DF3586F5@www.open-std.org>
In-Reply-To: <20140508012644.679DF3586F5@www.open-std.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-sc22wg5@open-std.org
Precedence: bulk

On 05/08/2014 03:26 AM, Whitlock, Stan wrote:

[ Just in case Karla, to whom I am an alternate, doesn't vote ]

> 8 Fortran interpretations are currently "Passed by J3 meeting" after
>
> J3 meeting #203.  This is the letter ballot phase to go from "Passed
>
> by J3 meeting" to "Passed by J3 letter ballot".
>
> The following Fortran interpretations are being balloted:
>
> Yes  No   Number     Title
>
> -Y-  ---  F08/0099   VOLATILE in specification expressions
>
> -Y-  ---  F08/0100   IMPORT statement and prior explicit declaration
>
> -Y-  ---  F08/0101   NAMELIST and multiple occurrences of a variable
>
> -Y-  ---  F08/0102   MERGE and polymorphism
>
> -Y-  ---  F08/0103   Pointers to internal procedures with different host
>                                  instances
>
> -Y-  ---  F08/0104   IEEE Inquiry Functions
>
> ---  -N-  F08/0105   Is the ASYNCHRONOUS attribute allowed with the
>                                  VALUE attribute?
>
> -Y-  ---  F08/0106   MOVE_ALLOC for a remote array

F08/0105 Is the ASYNCHRONOUS attribute allowed with the VALUE attribute?

Allowing this would make the meaning of the program depend on when the 
processor decides to make the copy inherent in the VALUE attribute. 
This seems a dangerous introduction of non-determinism in the Standard 
to me.

Kind regards,

-- 
Toon Moene - e-mail: toon@moene.org - phone: +31 346 214290
Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands
At home: http://moene.org/~toon/; weather: http://moene.org/~hirlam/
Progress of GNU Fortran: http://gcc.gnu.org/wiki/GFortran#news
