➜

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 yselivanov
Recipients Yury.Selivanov, casevh, josh.r, lemburg, mark.dickinson, pitrou, rhettinger, serhiy.storchaka, skrah, vstinner, yselivanov, zbyrne
Date 2016-02-05.16:18:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1454689139.54.0.847757149171.issue21955@psf.upfronthosting.co.za>
In-reply-to
Content 
> Between fastintfloat_alt.patch and fastint5.patch, I prefer fastintfloat_alt.patch which is much easier to read, so probably much easier to debug. I hate huge macro when I have to debug code in gdb :-( I also like very much the idea of *reusing* existing functions, rather than duplicating code.

I disagree.

fastintfloat_alt exports a lot of functions from longobject/floatobject, something that I really don't like.  Lots of repetitive code in ceval.c also make it harder to make sure everything is correct.
History
Date User Action Args
2016-02-05 16:18:59yselivanovsetrecipients: + yselivanov, lemburg, rhettinger, mark.dickinson, pitrou, vstinner, casevh, skrah, Yury.Selivanov, serhiy.storchaka, josh.r, zbyrne
2016-02-05 16:18:59yselivanovsetmessageid: <1454689139.54.0.847757149171.issue21955@psf.upfronthosting.co.za>
2016-02-05 16:18:59yselivanovlinkissue21955 messages
2016-02-05 16:18:59yselivanovcreate