From owner-sc22wg5+sc22wg5-dom8=www.open-std.org@open-std.org  Thu Sep  5 20:51:22 2013
Return-Path: <owner-sc22wg5+sc22wg5-dom8=www.open-std.org@open-std.org>
X-Original-To: sc22wg5-dom8
Delivered-To: sc22wg5-dom8@www.open-std.org
Received: by www.open-std.org (Postfix, from userid 521)
	id E3328357298; Thu,  5 Sep 2013 20:51:22 +0200 (CEST)
Delivered-To: sc22wg5@open-std.org
Received: from exprod6og111.obsmtp.com (exprod6og111.obsmtp.com [64.18.1.27])
	by www.open-std.org (Postfix) with ESMTP id 9F5F8356FDB
	for <sc22wg5@open-std.org>; Thu,  5 Sep 2013 20:51:03 +0200 (CEST)
Received: from CFWEX01.americas.cray.com ([136.162.34.11]) (using TLSv1) by exprod6ob111.postini.com ([64.18.5.12]) with SMTP
	ID DSNKUijSl/sd/pHqPz+6Kxi86V9rT/3z8RAw@postini.com; Thu, 05 Sep 2013 11:51:19 PDT
Received: from fortran.us.cray.com (172.31.19.200) by
 CFWEX01.americas.cray.com (172.30.88.25) with Microsoft SMTP Server id
 14.2.347.0; Thu, 5 Sep 2013 13:50:11 -0500
Message-ID: <5228D413.6060501@cray.com>
Date: Thu, 5 Sep 2013 13:57:23 -0500
From: Bill Long <longb@cray.com>
Reply-To: <longb@cray.com>
Organization: Cray Inc.
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: sc22wg5 <sc22wg5@open-std.org>
Subject: Re: (j3.2006) (SC22WG5.5088) Interp ballot
References: <20130905063636.C5949357207@www.open-std.org>
In-Reply-To: <20130905063636.C5949357207@www.open-std.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-sc22wg5@open-std.org
Precedence: bulk



On 9/5/13 1:36 AM, Malcolm Cohen wrote:
> COMMENT on F03/0047:
>    (a) Although Bill Long correctly points out that MERGE is slightly assymetric
> if only one argument is polymorphic, but if only one argument is polymorphic the
> result type is known precisely and is always the declared type, so this is not a
> polymorphism that makes a difference other than allowing one to use it in SELECT
> TYPE.  And why do SELECT TYPE when you know the answer.
>    One might imagine that also the standard is clear and unambiguous, the answer
> for MERGE is unhelpful.  There are at least two reasonable, symmetric and
> consistent things to do here:
> (i) MERGE is polymorphic if and only if both TSOURCE and FSOURCE are
> polymorphic;
> (ii) the "types should be the same" should apply only to the declared type, and
> MERGE should be polymorphic if either or both of TSOURCE and FSOURCE are the
> same; this would seem to be the most useful definition, but it would require an
> edit.
>
> Either of these would result in edits to the standard.  Perhaps we should pull
> Q5 and A5 out of this interp, and make a new interp of it.  Note that it is too
> late to change F2003 though!

I think that Malcolm's alternatives deserve further consideration, so 
agree with the idea of separating this issue to a new (thankfully 
smaller) interp.   Since the interp currently does not have edits, this 
does not disrupt the schedule for a new Corrigendum.

Cheers,
Bill

-- 
Bill Long                                           longb@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


