From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] comparisons with NaN
Date: Wed, 21 Aug 2013 13:47:56 -0400 [thread overview]
Message-ID: <461015d88dcdc89a3697e2e1d01a926c@kw.quanstro.net> (raw)
In-Reply-To: <2FEB81A6-7D40-427D-BF9B-07D90872E307@bitblocks.com>
On Wed Aug 21 13:43:54 EDT 2013, bakul@bitblocks.com wrote:
> On Aug 21, 2013, at 9:55 AM, erik quanstrom <quanstro@quanstro.net> wrote:
>
> > On Wed Aug 21 12:09:26 EDT 2013, 9fans@hamnavoe.com wrote:
> >>> at least in terms of passing floating point test suites
> >>> (like python's) the NaN issue doesn't come up
> >>
> >> Actually it was a test suite that revealed the NaN errors.
> >> I wouldn't think it's something anyone needs in normal
> >> day-to-day computation, but sometimes boxes must be ticked.
> >
> > :-) it is hard to imagine how this is useful. it's not like
> > ∑{i→∞}-0 is interesting. at least ∏{i→∞}-0 has an alternating
> > sign. (so does it converge with no limit?)
> >
> > the difference i have seen is a situation like
> > atan2(-0, x) ≡ -π
> > atan2(+0, x) ≡ pi, ∀ x<0.
> >
> > any ideas on how this is useful?
>
>
> See comments by Stephen Canon in
> http://stackoverflow.com/questions/1565164/what-is-the-rationale-for-all-comparisons-returning-false-for-ieee754-nan-values
i think you selected a different antecedent for "this" than
i did. by "this" i ment to refer to -0.
- erik
next prev parent reply other threads:[~2013-08-21 17:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 13:17 Richard Miller
2013-08-21 14:34 ` erik quanstrom
2013-08-21 16:08 ` Richard Miller
2013-08-21 16:55 ` erik quanstrom
2013-08-21 17:42 ` Bakul Shah
2013-08-21 17:47 ` erik quanstrom [this message]
2013-08-21 18:00 ` Bakul Shah
2013-08-21 18:00 ` Richard Miller
2013-08-21 18:24 ` Charles Forsyth
2013-08-22 14:05 ` Richard Miller
2013-08-22 14:25 ` Charles Forsyth
2013-09-20 9:05 ` Richard Miller
2013-08-21 14:36 ` erik quanstrom
2013-08-21 18:24 ` lucio
2013-08-21 18:27 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=461015d88dcdc89a3697e2e1d01a926c@kw.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).