(j3.2006) (SC22WG5.4930) J3/13-xxxr1 interp letter ballot #28 - due 19-Apr-2013

[Van Snyder]

> Yes  No   Number     Title 
> 
> -Y-  ---  F03/0030   IEEE divide by zero
> 
> -Y-  ---  F03/0047   Polymorphic arguments to intrinsic
> 
>                                 procedures
> 
> -Y-  ---  F03/0064   Recursive declaration of procedure interfaces
> 
> -Y-  ---  F03/0100   Error in field width for special cases of signed
> 
>                                 INFINITY output
> 
> -Y-  ---  F03/0139   Functions returning procedure pointers
> 
> -Y-  ---  F08/0071   Vector subscript target
> 
> -Y-  ---  F08/0085   Problems with PARAMETERs
> 
> -Y-  ---  F08/0086   Implied-shape and separate PARAMETER statement
> 
> ---  -N-  F08/0087   Mixed-kind character assignment

            I prefer answer 2 and edits 2 from 13-204.  My ballot
            on this question would be marked yes if it is not out of
            order to consider adding this to the work plan at 201.

> -Y-  ---  F08/0088   Can ALLOCATE with SOURCE= have side-effects in a
>                                 PURE proc?
> 
> -C-  ---  F08/0089   Variable-denoting functions change existing
>                                 semantics

            The title should be changed to "Variable-denoting
            function references change existing semantics."

> ---  -N-  F08/0090   What restrictions apply to initialization and
>                                  PARAMETER?

            I prefer that the requirements be made constraints now,
            rather than putting a vague hope that they might someday
            be constraints.  We appeared not to have qualms about
            introducing constraints in answers to other
            interpretation requests, so why not this one?  My ballot
            on this question would marked be yes if it is not out of
            order to add this to the work plan at 201.