[Python-Dev] Python 2.6/3.0, IEEE 754 floating point semantics and S60

Torne Wuff torne-pythondev at wolfpuppy.org.uk
Fri Nov 28 17:48:07 CET 2008

On Thu, Nov 27 08 at  7:27:03PM +0000, Mark Dickinson wrote:
> Many thanks for your input!

No problem! I don't like hearing folks from Nokia implying that our code
is rubbish :)

> I think IEEE 754 is relevant. :-)

Thanks for hunting down all that information! I'm in agreement: we
should fix this so that it works for 17 digits. I've had a chat with our
team's architect and it's not as awkward as I had assumed: the hardware
floating point doesn't actually get in the way as the function in
question only uses our software-implemented high precision real class,
not float/double types.

Whether our implementation is actually *correct* if you ask it for more
digits is an interesting question, though. It might be already :)

Are you aware of any compliance suite, test vectors, etc we could
'borrow' to verify our implementation? We would certainly like to verify
this. I'm going to raise a defect for the binary<->decimal conversion
issue, and see what we can do about sorting this out for future OS

Torne Wuff
torne at wolfpuppy.org.uk

More information about the Python-Dev mailing list