(j3.2006) J3/09-292 - J3 Fortran interp letter ballot #19 - due 19-Oct-2009

Whitlock, Stan stan.whitlock
Thu Sep 17 23:28:50 EDT 2009


To:           J3 Members
From:       Stan Whitlock
Subject:   J3 Fortran interp letter ballot #19 - due 19-Oct-2009
Date: 2009 September 17


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.

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

---  ---  F95/0098   Are dummy functions returning assumed-length
                            character legal?
---  ---  F03/0022   Coexistence of IEEE and non-IEEE kinds
---  ---  F03/0024   DEALLOCATE and array pointers
---  ---  F03/0034   IEEE_LOGB()
---  ---  F03/0039   HYPOT()
---  ---  F03/0078   IEEE_SUPPORT_DATATYPE vs. mathematical equivalence
---  ---  F03/0090   Polymorphic array constructors
---  ---  F03/0130   Elemental specific intrinsic procedure
                            characteristics
---  ---  F03/0131   SAVE attribute and EQUIVALENCE
---  ---  F03/0132   Unformatted i/o and private components
---  ---  F03/0133   Is unlimited polymorphic allowed in COMMON?
---  ---  F03/0134   Implicit typing of procedure pointers
---  ---  F03/0135   Interaction between RESULT, recursion, and host
                            generic
---  ---  F03/0136   Are subroutines distinguishable from arrays?
---  ---  F03/0137   Dummy procedure type compatibility
---  ---  F03/0138   External <procedure-name> as <proc-target>

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, Monday, 19-Oct-2009, in order to be counted.


Thanks                         /Stan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://j3-fortran.org/pipermail/j3/attachments/20090917/2ea90db3/attachment-0001.htm>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 09-292 LB #19 due 19-Oct-2009.txt
URL: <http://j3-fortran.org/pipermail/j3/attachments/20090917/2ea90db3/attachment-0001.txt>



More information about the J3 mailing list