(j3.2006) (SC22WG5.3882) WG5 Ballot 6 (N1765)

Van Snyder Van.Snyder
Thu Jan 22 03:30:31 UTC 2009


The following Fortran 2003 interpretations are being balloted:

Yes   No   Number     Title
-C-   ---  F95/0074   TARGET dummy arguments and POINTER expressions
-Y-   ---  F95/0102   mask-expr evaluated only once
-Y-   ---  F03/0049   Separators in list-directed output involving UDDTIO
-Y-   ---  F03/0073   C interop of dummy procedures
-Y-   ---  F03/0074   Type mismatch for C character arguments
-Y-   ---  F03/0075   C interop of derived types with array components
-C-   ---  F03/0076   Scope of Fortran names of procedures with binding
                      labels
-Y-   ---  F03/0077   LBOUND of array structure component
-Y-   ---  F03/0081   F edit descriptor with field width 0
-C-   ---  F03/0082   VALUE in place of INTENT for pure procedure dummy
                      arguments
-C-   ---  F03/0087   Entry names as dummy procedure arguments
-Y-   ---  F03/0098   Does allocate with source= define subcomponents?
-Y-   ---  F03/0099   Clause 16 does not account for volatile variable
-Y-   ---  F03/0102   Evaluation of bound-expr in data pointer assignment
-Y-   ---  F03/0109   Referencing deferred binding via absent dummy argument
-C-   ---  F03/0111   Is defined assignment to a vector subscripted
                      array allowed?
-Y-   ---  F03/0113   Size and uniqueness considerations for ID=
-Y-   ---  F03/0114   Inconsistent restrictions on i/o specifiers
-C-   ---  F03/0117   STOP executed via function in input/output list

F95/0074: I'm pleased we reached the opposite conclusion in 2008.
F03/0076: I'm pleased we reached the opposite conclusion in 2008.
F03/0082: I'm pleased we reached the opposite conclusion in 2008.
F03/0087: I'm pleased we removed 04-007:C1255 in 2008.
F03/0111: The answer doesn't address the submitter's contention that
elemental assignments are expanded into scalar assignments before
consideration whether they are defined or intrinsic.  Nothing wrong with
the edits, however.
F03/0117: Making the whole file undefined seems a bit harsh.  Couldn't
this have been "the record being written when the program is
terminated?"





More information about the J3 mailing list