(j3.2006) (SC22WG5.4342) [ukfortran] 10-208r1

Bill Long longb
Thu Oct 14 12:17:34 EDT 2010

Reinhold Bader wrote:
>   Am 14.10.2010 04:12, schrieb malcolm at nag-j.co.jp:
> [...]
>>> (2) copy object from remote image to invoking image
>> That's the problem.  You can't do that.  You can't do that because it has a polymorphic allocatable subcomponent.  On another image.  Copying the object involves copying the allocatable subcomponent.  Which requires knowing what *its* type is - not just how big it is itself but also whether *it* has any further allocatable subcomponents.
> I understand that. What I don't understand is how the restriction makes the problem go 
> away. Presumably,
>   SELECT TYPE(o_foo)

Checking on the dynamic type of o_foo in THIS image here.

>    TYPE IS (badfoo)
> !----------******  (sorry for the cut-and-paste sloth from previous mail)
>      CALL o_foo[2]%op(1)

Need to know the type on image 2 here.  Not clear how that relates to 
the SELECT TYPE above.


> is legal, but also would require the above-mentioned copying of unknown amounts of data.
> If it isn't legal for some other reason - why then do we need the restriction?
> [...]
> Regards
> Reinhold
> _______________________________________________
> J3 mailing list
> J3 at j3-fortran.org
> http://j3-fortran.org/mailman/listinfo/j3

Bill Long                                           longb at cray.com
Fortran Technical Support    &                 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