(j3.2006) (SC22WG5.4692) J3/12-147 for meeting #198: interp letter ballot #25 due 8-Jun-2012

Whitlock, Stan stan.whitlock
Sun May 6 20:10:30 EDT 2012


I am sending this interp letter ballot to WG5 as well as J3.  After J3 votes on these interps, they may show up in a WG5 ballot.  Your comments now are welcome.  We will finalize the results at the Toronto WG5/J3 meeting in June so get your comments in by 8-Jun so they can be addressed in June.

Thanks                                                              /Stan

                                                           12-147

To:        J3 Members
From:      Stan Whitlock
Subject:   J3 Fortran interp letter ballot #25 - due 8-Jun-2012
Date: 2012 May 06


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.

43 Fortran interpretations are currently "Passed by J3 meeting" after
J3 meeting #197.  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/0017   Dummy procedure pointers and PRESENT
---  ---  F03/0018   Multiple identical specific procedures in type-bound generic interfaces
---  ---  F03/0019   Multiple identical specific procedures in generic interface blocks
---  ---  F03/0021   What kind of token is a stop code?
---  ---  F03/0046   Unlimited polymorphic pointers in common blocks
---  ---  F03/0053   The BIND attribute for C_PTR and C_FUNPTR
---  ---  F03/0065   Relational equivalence
---  ---  F03/0084   IEEE_SET_ROUNDING_MODE in a subroutine
---  ---  F03/0096   Can a read statement change the unit value?
---  ---  F03/0103   Restrictions on dummy arguments not present for  polymorphic type or parameterized derived type
---  ---  F03/0116   indistinguishable specifics for a generic interface with use association
---  ---  F03/0118   Are lower bounds of assumed-shape arrays assumed?
---  ---  F03/0120   When are parameterized sequence types the same type?
---  ---  F03/0121   Precise FP semantics of the REAL intrinsic
---  ---  F08/0004   Is TARGET argument of ASSOCIATED a pointer or nonpointer dummy?
---  ---  F08/0008   IEEE exceptions for intrinsic functions
---  ---  F08/0031   PURE INTENT(OUT) finalization
---  ---  F08/0032   PURE FUNCTION result finalization
---  ---  F08/0038   Are pointless restrictions on DIM arguments intended?
---  ---  F08/0040   MOVE_ALLOC for coarrays
---  ---  F08/0042   SOURCE= questions
---  ---  F08/0043   Executing a type-bound procedure on a coindexed object
---  ---  F08/0048   Sequence association for coarrays
---  ---  F08/0054   Requirements for needing an explicit interface
---  ---  F08/0055   G editing for reals
---  ---  F08/0056   Non-polymorphic ALLOCATE with polymorphic SOURCE=
---  ---  F08/0057   Interoperability with empty types
---  ---  F08/0058   ENTRY point RESULT variable
---  ---  F08/0059   Auto-targetting requirements
---  ---  F08/0060   Procedure pointer assignment with an EXTERNAL target
---  ---  F08/0061   Description of the CONTIGUOUS attribute misworded?
---  ---  F08/0062   Mixing default initialization with DATA initialization
---  ---  F08/0063   G editing to a narrow output field
---  ---  F08/0064   STATUS of GET_ENVIRONMENT_VARIABLE
---  ---  F08/0065   Should certain procedures in intrinsic modules be pure?
---  ---  F08/0066   Are certain expressions with pointer initialization constant?
---  ---  F08/0067   Passing arrays of extended type objects
---  ---  F08/0068   Pointer association and extended type arrays
---  ---  F08/0069   Which part of an effective argument becomes undefined?
---  ---  F08/0070   Finalization of INTENT(OUT) arguments
---  ---  F08/0071   Vector subscript target
---  ---  F08/0072   Final subroutines with corank
---  ---  F08/0073   Polymorphic auto-targetting

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, 8-Jun-2012, in order to be counted.


Thanks                         /Stan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://j3-fortran.org/pipermail/j3/attachments/20120507/cc96844e/attachment-0001.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 12-147 m198 interp LB #25 due 8-Jun-2012.txt
URL: <http://j3-fortran.org/pipermail/j3/attachments/20120507/cc96844e/attachment-0001.txt>



More information about the J3 mailing list