(j3.2006) (SC22WG5.5258) J3 Fortran interp letter ballot #30 - due 13-Jun-2014
Toon Moene
toon
Thu Jun 12 14:06:27 EDT 2014
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 at 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
More information about the J3
mailing list