[Python-Dev] small floating point number problem (original) (raw)
Tim Peters tim.peters at gmail.com
Wed Feb 8 20:07:58 CET 2006
- Previous message: [Python-Dev] small floating point number problem
- Next message: [Python-Dev] Make error on solaris 9 x86 - error: parse error before "upad128_t"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[Raymond Hettinger]
... The asymmetric handling of denormals by the atof() and ftoa() functions is why you see a difference. A consequence of that asymmetry is the breakdown of the expected eval(repr(f))==f invariant:
Just noting that such behavior is a violation of the 754 standard for string->double conversion. But Microsoft's libraries don't claim to support the 754 standard, so good luck suing them ;-). Python doesn't promise anything here either.
- Previous message: [Python-Dev] small floating point number problem
- Next message: [Python-Dev] Make error on solaris 9 x86 - error: parse error before "upad128_t"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]