(j3.2006) J3 Fortran interp letter ballot #22 - due 19-Nov-2010

[Whitlock, Stan]

                                                           10-254

To:        J3 Members
From:      Stan Whitlock
Subject:   J3 Fortran interp letter ballot #22 - due 19-Nov-2010
Date: 2010 October 14


Enclosed in the next letter ballot on Fortran interpretations.

The rules 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.

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

---  ---  F03/0030   IEEE divide by zero
---  ---  F03/0048   Control edit descriptors in UDDTIO
---  ---  F03/0085   Finalizing targets of pointer or allocatable
                            actual arguments
---  ---  F03/0091   Array components cannot depend on length type
                            parameters
---  ---  F03/0096   Can a read statement change the unit value?
---  ---  F03/0105   SIZE= specifier and UDDTIO
---  ---  F03/0110   Error in field width for special cases of signed
                            INFINITY output
---  ---  F03/0121   Precise FP semantics of the REAL intrinsic
---  ---  F03/0123   Implicit typing in derived types
---  ---  F03/0124   definition is poorly defined
---  ---  F03/0128   Subobjects in namelist output
---  ---  F08/0006   generic resolution with banned argument
                            combinations
---  ---  F08/0040   MOVE_ALLOC for coarrays
---  ---  F08/0041   Segment ordering rules
---  ---  F08/0042   SOURCE= questions
---  ---  F08/0043   Executing a type-bound procedure on a coindexed
                             object
---  ---  F08/0044   Resolving the type of a coarray or coindexed object
---  ---  F08/0045   constraints on entities of type LOCK_TYPE
---  ---  F08/0046   VALUE attribute restrictions
---  ---  F08/0047   public generic with same name as private type
---  ---  F08/0048   Sequence association for coarrays
---  ---  F08-0049   ELEMENTAL functions with nonconstant type parameters


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

by 11:59:59PM, PDT, Friday, 19-Nov-2010, in order to be counted.


Thanks                         /Stan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://j3-fortran.org/pipermail/j3/attachments/20101014/b53752a5/attachment-0001.htm>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 10-254 interp LB #22 - due 19-Nov-2010.txt
URL: <http://j3-fortran.org/pipermail/j3/attachments/20101014/b53752a5/attachment-0001.txt>