This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author christian.heimes
Recipients christian.heimes, collinwinter, facundobatista, mark.dickinson, richardh2003, tim.peters
Date 2008-01-20.08:57:22
SpamBayes Score 0.0009030523
Marked as misclassified No
Message-id <1200819443.55.0.0212512893037.issue705836@psf.upfronthosting.co.za>
In-reply-to
Content
Sounds like a good idea to me. Although all major platforms support IEEE
Python should guarantee a stable behavior on all platforms.

The lines should be a safe replacement of the downcast:
double fromd;
float tof;
tof = abs(fromd) >= FLT_MAX ? FLT_MAX : fromd;
tof = (float)copysign((double)tof, fromd);

By the way the release notes of Python should mention the our work on
better IEEE-754 and numeric support in bold letters. "Python 2.6 - now
with even better support for professional math in the core". It's a good
advertisement.  :)
History
Date User Action Args
2008-01-20 08:57:23christian.heimessetspambayes_score: 0.000903052 -> 0.0009030523
recipients: + christian.heimes, tim.peters, collinwinter, facundobatista, mark.dickinson, richardh2003
2008-01-20 08:57:23christian.heimessetspambayes_score: 0.000903052 -> 0.000903052
messageid: <1200819443.55.0.0212512893037.issue705836@psf.upfronthosting.co.za>
2008-01-20 08:57:22christian.heimeslinkissue705836 messages
2008-01-20 08:57:22christian.heimescreate