From owner-sc22wg5@open-std.org  Fri Jul 30 17:58:39 2010
Return-Path: <owner-sc22wg5@open-std.org>
X-Original-To: sc22wg5-dom8
Delivered-To: sc22wg5-dom8@www2.open-std.org
Received: by www2.open-std.org (Postfix, from userid 521)
	id 5846FC3BA11; Fri, 30 Jul 2010 17:58:39 +0200 (CEST)
X-Original-To: sc22wg5@open-std.org
Delivered-To: sc22wg5@open-std.org
X-Greylist: delayed 1173 seconds by postgrey-1.18 at www2.open-std.org; Fri, 30 Jul 2010 17:58:38 CEST
Received: from smtp.cims.nyu.edu (SMTP.CIMS.NYU.EDU [128.122.80.9])
	by www2.open-std.org (Postfix) with ESMTP id 81B94C3BA0E
	for <sc22wg5@open-std.org>; Fri, 30 Jul 2010 17:58:38 +0200 (CEST)
Received: from [192.168.0.100] (cpe-69-76-186-24.kc.res.rr.com [69.76.186.24] (may be forged))
	(authenticated bits=0)
	by smtp.cims.nyu.edu (8.14.3/8.13.8) with ESMTP id o6UFd12x019076
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Fri, 30 Jul 2010 11:39:02 -0400 (EDT)
Message-ID: <4C52F218.6010706@courant.nyu.edu>
Date: Fri, 30 Jul 2010 08:39:04 -0700
From: Aleksandar Donev <donev@courant.nyu.edu>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: J3 <j3@j3-fortran.org>, SC22WG5 <sc22wg5@open-std.org>
Subject: Re: (j3.2006) (SC22WG5.4305) Executing a type-bound procedure on
 a coindexed object
References: <20100729154103.E2BD3C3BA01@www2.open-std.org> <4C51AC7D.2000805@lrz.de>
In-Reply-To: <4C51AC7D.2000805@lrz.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-sc22wg5@open-std.org
Precedence: bulk

Reinhold Bader wrote:
>  This does not seem to make sense. The case you mention can also happen
>   in a non-polymorphic scenario, but there are no restrictions there.
Which is a hint that the size of the allocatable components is not the
issue. There are restrictions to ensure that the sizes match so that
remote reallocation never happens. The issue, as I recall, was that
there could be other components of unknown types, shapes, etc. In a
heterogeneous environment, copying such things may be harder than just
getting an integer size of an allocatable array.
In general, it is likely it is all implementable even without some of
the restrictions, but someone asked to add a restriction to facilitate
implementation, and we listened unless it took away what was seen as a
critical functionality. Polymorphic coarrays were not in general seen as
"critical" :-)
Best,
Aleks

-- 
Aleksandar Donev
Assistant Professor of Mathematics
Courant Institute of Mathematical Sciences, New York University
E-mail: donev@courant.nyu.edu
Phone: (510) 910-0891
Address: 251 Mercer St, New York, NY 10012
Web: http://cims.nyu.edu/~donev/


