(j3.2006) (SC22WG5.5407) RE: J3/14-279: J3 Fortran interp letter ballot #32 revised - due 9-Jan-2015

[Whitlock, Stan]

J3 members, please vote.  WG5 members, your comments are appreciated.

Thanks                                               /Stan

From: Whitlock, Stan
Sent: Tuesday, November 25, 2014 11:42 AM
To: WG5
Cc: Whitlock, Stan
Subject: J3/14-279: J3 Fortran interp letter ballot #32 revised - due 9-Jan-2015

                                                        J3/14-279
To:        J3 Members
From:      Stan Whitlock
Subject:   J3 Fortran interp letter ballot #32 revised - due 9-Jan-2015
Date: 2014 November 25

Enclosed in the next letter ballot on Fortran interpretations.

The rules for interpretation handling by which we operate say:

    o   J3 votes on the answer at a J3 meeting; a simple majority
        vote marks the answer as "passed by J3 meeting".

    o   Between J3 meetings the chair of /interp sends a J3 letter
        ballot to J3 to approve interp answers that have been "passed
        by J3 meeting".  The letter ballot runs for 30 days.  Not
        voting on three of four consecutive J3 letter ballots is
        grounds to terminate J3 membership.  An interp answer passes
        by a 2/3rds vote;  a no vote must be accompanied by an
        explanation of the changes necessary to change the member's
        vote to yes.

        J3/interp reserves the right to recall an interp answer for
        more study even if the answer passes.

12 Fortran interpretations are currently "Passed by J3 meeting" after
J3 meeting #205.  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

---  ---  F08/0105  Is the ASYNCHRONOUS attribute allowed with the
                     VALUE attribute?
---  ---  F08/0110  Interdependence of specifier values in input/output
                     statements
---  ---  F08/0115  ASYNCHRONOUS and argument passing
---  ---  F08/0116  Interoperable procedures
---  ---  F08/0117  TARGET and coindexed arguments
---  ---  F08/0118  Subobject of variable in variable definition context
---  ---  F08/0119  Branching to END BLOCK and END CRITICAL
---  ---  F08/0120  Is the name of a procedure pointer a local identifier?
---  ---  F08/0121  Add to introduction defined operations in
                     specification exprs
---  ---  F08/0122  Types with coarray components
---  ---  F08/0123  SPACING intrinsic
---  ---  F08/0124  Coindexed object with polymorphic subcomponent

The text of these interpretations is attached.  Each interpretation
starts with a row of "-"s.

Please mark the above -Y- in the Yes column for "yes", -C- in the Yes
column for "yes with comment", or -N- in the No column for a "no"
answer {be sure to include your reasons with "no"} and send only the
above text {not this entire mail message} with any comments to

        j3 at j3-fortran.org<mailto:j3 at j3-fortran.org>

by 11:59:59PM, PDT, Friday, 9-Jan-2015, in order to be counted.


Thanks                         /Stan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.j3-fortran.org/pipermail/j3/attachments/20150109/77abfc92/attachment-0001.html 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 14-279 Stan - J3 Fortran interp	LB #32 revised - due 9-Jan-2015 - m206.txt
Url: http://mailman.j3-fortran.org/pipermail/j3/attachments/20150109/77abfc92/attachment-0001.txt