(j3.2006) (SC22WG5.3562) Letter ballot 5 on F2003 interpretations

[Bill Long]

John Reid wrote:


The following Fortran 2003 interpretations are being balloted:

Yes   No   Number     Title
---   -N-  F03/0003 Referencing deferred bindings  
---   -N-  F03/0004 Type-bound procedures and undefined association status
-Y-   ---  F03/0079 Value of decimal exponent for a real zero value
-Y-   ---  F03/0080 Formatted output of a negative real zero value
-Y-   ---  F03/0100 Error in field width for special cases of signed 
                    INFINITY output
-Y-   ---  F03/0104 Deallocation and finalization of bounds-remapped
                    pointers
-Y-   ---  F03/0106 Inquire by unit inconsistencies
-Y-   ---  F03/0107 Are the IEEE_* elemental routines required
-Y-   ---  F03/0108 Is IEEE_SUPPORT_NAN consistent with the other
                    IEEE_SUPPORT functions



Reasons for No vote on F03/0003:

In the paragraph above the ANSWER:, there is a reference to 
"x%nondeferred_proc".  There is no such entity in the program example.  
I suspect this should be "x%deferred_proc".

The edit covers 3 of the 4 possible cases. It seems like the 4th should 
be covered as well.  We should disallow an undefined pointer, a 
disassociated pointer, an unallocated allocatable variable (all 
covered), as well as a pointer with an undefined association status.  
It's not clear why the last one was left off.


Reasons for No vote on F03/0004:

In the DISCUSSION:  The first sentence is of the form "Access to 
<undefined concept> (a.k.a. <well defined concept>) always ...".  I have 
multiple problems with this sentence.

1) It is confusing to introduce a new, undefined term, "object-bound 
procedures" when we have a clear, defined term already "procedure 
pointer component".

2) Slang like "a.k.a" might be avoided, as a consideration to readers 
whose native language is not English.

3) The sentence runs afoul of f08 where procedure pointer components can 
have default initialization to a non-NULL target.  In that case, the 
question in the interp applies to procedure pointer components  with the 
NOPASS attribute as well as type-bound procedures.  To head off another 
interp in the future, I'd prefer to just delete the whole DISCUSSION: 
section.

Finally, the edit is the same as in F03/0003, and thus I have the same 
issue as above.

Cheers,
Bill










-- 
Bill Long                                   longb at cray.com
Fortran Technical Support    &              voice: 651-605-9024
Bioinformatics Software Development         fax:   651-605-9142
Cray Inc., 1340 Mendota Heights Rd., Mendota Heights, MN, 55120