(j3.2006) J3 Fortran interp letter ballot

[John Reid]

-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

-Y-  ---  F03/0034   IEEE_LOGB()

-Y-  ---  F03/0039   HYPOT()

-Y-  ---  F03/0078   IEEE_SUPPORT_DATATYPE vs. mathematical equivalence

-C-  ---  F03/0090   Polymorphic array constructors

-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

-Y-  ---  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>


Comment on F03/0090.
In 07-231, the function name in (1) is f. This needs to be restored or the other
occurrences of f changed to f1. Similarly in (2), f2 should be changed to f or
all occurences of f and F should be changed to f2.


Comment on F03/0138.
The edit makes a sentence that is very hard to read and may even be ambiguous.
It would be much better as two sentences:
[144:6+] In 7.4.2 Pointer assignment, add at the end of constraint C727:
      "If it is the name of an external procedure, the procedure shall be
       accessed by USE or host association, referenced in the scoping unit as a
       procedure, or have the EXTERNAL attribute".