A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2010-March/098930.html below:

[Python-Dev] Why is nan != nan?

[Python-Dev] Why is nan != nan? [Python-Dev] Why is nan != nan?Greg Ewing greg.ewing at canterbury.ac.nz
Fri Mar 26 03:25:30 CET 2010
Curt Hagenlocher wrote:

> Wait, what? I haven't been paying much attention, but this is backwards.
> There are multiple representations of NaN in the IEEE encoding;

I think Nick's point is that there aren't enough bits
to give the result of every operation its own unique
NaN.

The payload of a NaN in typical hardware implementations
is quite small, because it has to fit into the exponent
field.

-- 
Greg
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4