From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Wed, 21 Aug 2013 12:55:31 -0400 To: 9fans@9fans.net Message-ID: In-Reply-To: <04891ed00c35de2583c1da9a017dd7e2@hamnavoe.com> References: <04891ed00c35de2583c1da9a017dd7e2@hamnavoe.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] comparisons with NaN Topicbox-Message-UUID: 733068c2-ead8-11e9-9d60-3106f5b1d025 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 >=20 > 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 =E2=88=91{i=E2=86=92=E2=88=9E}-0 is interesting. at least =E2=88=8F{i=E2= =86=92=E2=88=9E}-0 has an alternating sign. (so does it converge with no limit?) the difference i have seen is a situation like atan2(-0, x) =E2=89=A1 -=CF=80 atan2(+0, x) =E2=89=A1 pi, =E2=88=80 x<0. any ideas on how this is useful? - erik