(j3.2006) Unlimited polymorphic and LOCK_TYPE (and EVENT_TYPE)

Bill Long longb
Sat May 31 18:02:59 EDT 2014


On May 30, 2014, at 7:01 PM, Van Snyder <Van.Snyder at jpl.nasa.gov> wrote:

> There needs to be a constraint against the <source-expr> being of type
> LOCK_TYPE (or EVENT_TYPE in the TS) if any <allocate-object> is
> unlimited polymorphic.

If the <source-expr> is type  X  does that not make the <allocate-object> also type X, and no longer unlimited polymorphic?    Seems like an issue needing an opinion from /DATA.    Not that the suggested constraint would be wrong - just whether it is necessary.  And whether we are setting ourselves up for similar patches in the future.


> 
> For LOCK_TYPE, this needs an interp.
> 
> There needs to be a constraint against the <data-target> being of type
> LOCK_TYPE (or EVENT_TYPE in the TS) if the <data-pointer-object> is
> unlimited polymorphic.
> 

POINTER attribute is not allowed for coarrays.  So how is it possible for the dynamic type of an unlimited polymorphic pointer to be EVENT_TYPE or LOCK_TYPE?

Cheers,
Bill




> For LOCK_TYPE, this needs an interp.
> 
> 
> _______________________________________________
> J3 mailing list
> J3 at mailman.j3-fortran.org
> http://mailman.j3-fortran.org/mailman/listinfo/j3

Bill Long                                                                       longb at cray.com
Fortran Technical Suport  &                                  voice:  651-605-9024
Bioinformatics Software Development                     fax:  651-605-9142
Cray Inc./ Cray Plaza, Suite 210/ 380 Jackson St./ St. Paul, MN 55101





More information about the J3 mailing list