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 belopolsky
Recipients belopolsky, drj, ggenellina, mark.dickinson, vstinner
Date 2008-12-09.18:27:17
SpamBayes Score 1.34152e-06
Marked as misclassified No
Message-id <>
In-reply-to <>
On Tue, Dec 9, 2008 at 12:39 PM, Mark Dickinson <> wrote:
> What would using Python's integer type solve, that isn't already solved by
> the patch?

Speaking for myself, it would alleviate the irrational fear of
anything involving the FPU. :-)

Seriously, it is not obvious that your algorithm is correct and does
not depend on x being stored in an extended precision register.
Floating point experts are in short supply, so it may take a while for
your patch to be thoroughly reviewed by one of them.  If you could
produce a formal proof of correctness of your algorithm, that would be
more helpful than code comments.

On the other hand, an implementation that uses only integer
arithmetics plus bit shifts is likely to be much easier to understand.
 I don't think the performance will suffer much.  We can even start
with a pure python prototype using struct.pack or ctypes to produce
the double result.
Date User Action Args
2008-12-09 18:27:19belopolskysetrecipients: + belopolsky, mark.dickinson, ggenellina, vstinner, drj
2008-12-09 18:27:18belopolskylinkissue3166 messages
2008-12-09 18:27:17belopolskycreate