From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,772ddcb41cd06d5b
X-Google-Attributes: gid103376,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!postnews.google.com!k1g2000prb.googlegroups.com!not-for-mail
From: Adam Beneschan <adam@irvine.com>
Newsgroups: comp.lang.ada
Subject: Re: How to check a Float for NaN
Date: Thu, 1 May 2008 07:38:40 -0700 (PDT)
Organization: http://groups.google.com
Message-ID: <fe6a8cc1-eac7-4b25-bd21-39f9c2015c4a@k1g2000prb.googlegroups.com>
References: 
 <3132e38d-18bb-4890-9cec-31056ac6e3ba@x19g2000prg.googlegroups.com>
	<d2cc5140-75e3-47e3-b26a-7c91880afdcc@a23g2000hsc.googlegroups.com>
	<6f7cd771-16b7-4729-9536-2a7d1c28a9cd@2g2000hsn.googlegroups.com>
	<93b0d930-102a-4ac4-8b85-48e87d9d3df1@j33g2000pri.googlegroups.com>
	<48197575$1_1@glkas0286.greenlnk.net>
NNTP-Posting-Host: 66.126.103.122
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Trace: posting.google.com 1209652720 27892 127.0.0.1 (1 May 2008 14:38:40
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Thu, 1 May 2008 14:38:40 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: k1g2000prb.googlegroups.com; posting-host=66.126.103.122;
	posting-account=duW0ogkAAABjRdnxgLGXDfna0Gc6XqmQ
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.12)
	Gecko/20050922 Fedora/1.7.12-1.3.1,gzip(gfe),gzip(gfe)
Xref: g2news1.google.com comp.lang.ada:21162
Date: 2008-05-01T07:38:40-07:00
List-Id: <comp.lang.ada>

On May 1, 1:04 am, "Stuart" <stu...@0.0> wrote:
> "Adam Beneschan" <a...@irvine.com> wrote in message

> > 13.9.2(4-11) lists the ways
> > that invalid data could be created, and the "result of a floating-
> > point operation that cannot return a valid result" is not one of those
> > listed.  Yes, I know that this is a NOTE and is not normative.)
>
> Would not 13.9.2(10) cover this:
>    "disrupting an assignment due to the failure of a language-defined check
> (see 11.6)"

Did you read 11.6?

I think all this says is that if an assignment statement raises an
exception (due to a language-defined check), then in the exception
handler and further on in the code, you can't count on the value of
the target object being normal.  You can't count on it being abnormal,
either.  But if no exception is raised, then this doesn't apply.

                               -- Adam