Tim,
Thanks for reminding me that this all varies from machine to machine.
I guess that what I was trying to say in my message is this:
On my platform, I get the same result. Here's why.
The term "unordered" came from me reading an x86 architecture reference
and trying to use the same words the grown-ups use.
It's too bad you can get infinity and nan other than by using
float('os-specific mumbo-jumbo'), because if that weren't the case we
could just force Python's syntax for floating-point literals on the
argument to float(), never passing it to the platform atof() if it
doesn't conform. That would, uh, completely solve all problems python
programmers ever encounter with floats.
Jeff
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