(j3.2006) (SC22WG5.4157) Urgent: letter ballot on interps

[David Muxworthy]

Yes  No Number     Title
-Y- --- F95/0098 Are dummy functions returning assumed-length  
character legal?
-Y- --- F03/0022 Coexistence of IEEE and non-IEEE kinds
-Y- --- F03/0024 DEALLOCATE and array pointers
-C- --- F03/0034 IEEE_LOGB()
-Y- --- F03/0039 HYPOT()
-C- --- F03/0063 Procedure pointers in BLOCK DATA program units
-Y- --- F03/0071 Subroutine/function ambiguity in generics
-Y- --- F03/0078 IEEE_SUPPORT_DATATYPE vs. mathematical equivalence
-Y- --- F03/0090 Polymorphic array constructors
-Y- --- F03/0112 Attributes allowed for dummy arguments in defined  
assignments
-Y- --- F03/0119 Elemental procedures and deferred length character  
components
-Y- --- F03/0122 When do objects of sequence derived type have the  
same type?
-Y- --- F03/0125 Definitions of EXTENDS_TYPE_OF and SAME_TYPE_AS
-Y- --- F03/0126 References to VOLATILE variables in pure procedures
-Y- --- F03/0127 Duration of procedure execution
-Y- --- F03/0129 C_LOC of character substrings
-Y- --- F03/0130 Elemental specific intrinsic procedure characteristics
-Y- --- F03/0131 SAVE attribute and EQUIVALENCE
-Y- --- F03/0132 Unformatted i/o and private components
-Y- --- F03/0133 Is unlimited polymorphic allowed in COMMON?
-Y- --- F03/0134 Implicit typing of procedure pointers
-C- --- F03/0135 Interaction between RESULT, recursion, and host generic
-Y- --- F03/0136 Are subroutines distinguishable from arrays?
-Y- --- F03/0137 Dummy procedure type compatibility
-C- --- F03/0138 External <procedure-name> as <proc-target>
-Y- --- F03/0139 Functions returning procedure pointers
-Y- --- F03/0140 Type of nested construct entities
-Y- --- F03/0141 More than one specific interface for a procedure



F03/0034 IEEE_LOGB()
The style of the two new cases would be more consistent with that of
the existing cases if the order of the conditions were reversed ("If X
is infinite and IEEE_SUPPORT_INF(X) is true ..." etc).  This applies
also to F2008.

F03/0063 Procedure pointers in BLOCK DATA program units
Nit-pick: In the edit for [98:21] "allocatable" should read
"allocatable,"

F03/0135 Interaction between RESULT, recursion, and host generic
The edit at [276:36+] should read "that scoping unit" rather than "the
scoping unit" for consistency with the other cases.

F03/0138 External <procedure-name> as <proc-target>
The proposed edit results in rather opaque English.  Changing
"association, referenced" to "association and is referenced" gives a
slight improvement.  The constraint would then be:

   A <procedure-name> shall be the name of a module or dummy procedure,
   a specific intrinsic function listed in 13.6 and not marked with a
   bullet (?), a procedure pointer, or an external procedure that is
   accessed by USE or host association and is referenced in the scoping
   unit as a procedure, or that has the EXTERNAL attribute.


David Muxworthy