[Python-Dev] Caching float(0.0)
nmm1 at cus.cam.ac.uk
Tue Oct 3 13:38:35 CEST 2006
skip at pobox.com wrote:
> Doesn't that presume that optimizing just 0.0 could be done easily? Suppose
> 0.0 is generated all over the place in EVE?
Yes, and it isn't, respectively! The changes in floatobject.c would
be trivial (if tedious), and my recollection of my scan is that
floating values are not generated elsewhere.
It would be equally easy to add a general caching algorithm, but
that would be a LOT slower than a simple floating-point comparison.
The problem (in Python) isn't hooking the checks into place,
though it could be if Python were implemented differently.
University of Cambridge Computing Service,
New Museums Site, Pembroke Street, Cambridge CB2 3QH, England.
Email: nmm1 at cam.ac.uk
Tel.: +44 1223 334761 Fax: +44 1223 334679
More information about the Python-Dev