From owner-sc22wg5@open-std.org Fri Feb 12 01:41:16 2010 Return-Path: X-Original-To: sc22wg5-dom8 Delivered-To: sc22wg5-dom8@www2.open-std.org Received: by www2.open-std.org (Postfix, from userid 521) id 26425C3BA29; Fri, 12 Feb 2010 01:41:16 +0100 (CET) X-Original-To: sc22wg5@open-std.org Delivered-To: sc22wg5@open-std.org Received: from ns.nag-j.co.jp (218-42-159-107.cust.bit-drive.ne.jp [218.42.159.107]) by www2.open-std.org (Postfix) with ESMTP id 07B93C3BA25 for ; Fri, 12 Feb 2010 01:41:11 +0100 (CET) Received: from 218-42-159-108.cust.bit-drive.ne.jp ([218.42.159.108] helo=Marucomputer) by ns.nag-j.co.jp with smtp (Exim 4.50) id 1NfjYI-0001ka-80; Fri, 12 Feb 2010 09:38:34 +0900 Message-ID: <32C1F39D51964BCAB7EB9BAF77B2F8CC@Marucomputer> From: "Malcolm Cohen" To: Cc: "WG5" References: <20100201122928.54FB8C178E4@www2.open-std.org><20100210005356.4ABF5C3BA23@www2.open-std.org> <20100210185846.34028C178DA@www2.open-std.org> In-Reply-To: <20100210185846.34028C178DA@www2.open-std.org> Subject: Re: [ukfortran] (SC22WG5.4174) (j3.2006) Urgent: letter ballot on interps Date: Fri, 12 Feb 2010 09:41:50 +0900 Organization: ??NAG MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="ISO-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8089.726 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726 Sender: owner-sc22wg5@open-std.org Precedence: bulk Bill Long wrote: > N.M. Maclaren wrote: >> On Feb 10 2010, Bill Long wrote: >>> Comment for F03/0039 - HYPOT() >>> >>> Nick's comments about the IEEE nonconformance of the proposed change >>> might be considered for 13.7.69 "HYPOT (X, Y)" in F08 >>> 09-007r3[353:18-27]. The HYPOT defined in Note 14.7 is not really >>> claimed to be the official IEEE HYPOT, but rather is a contrivance to >>> illustrate the setting and getting of IEEE flags. >> >> Ah! That confused me. >> >>> would result in a NaN result. It might also make Fred Tydeman happier >>> if the Note pointed out that the example is not an implementation of >>> the IEEE HYPOT function (at least it's not a valid one). I believe >>> that Fred (and maybe Nick) would be happy of the name of the function >>> were something other than HYPOT, to avoid confusion with the IEEE >>> HYPOT function. >> >> It would assuredly be less confusing. > > The potential for confusion is greater in F08. No, the potential for confusion is zero in F08. > In the context of the F03 standard (against which the interp is formally > filed), one could argue that only "experts" who knew about HYPOT from > elsewhere would be confused. In F08 we actually have an intrinsic function > with this name and the same argument list. The temptation to assume the Note > is referring to the same function as the one specified in Clause 13 seems > quite high to me. No, there is no temptation and no possibility for confusion. That is because the Note in question does not exist in F08. We deleted it specifically because it created more confusion than enlightenment. Cheers, -- ................................Malcolm Cohen, Nihon NAG, Tokyo.