[Python-Dev] Caching float(0.0) (original) (raw)
Nick Craig-Wood nick at craig-wood.com
Tue Oct 3 10:17:26 CEST 2006
- Previous message: [Python-Dev] Caching float(0.0)
- Next message: [Python-Dev] Caching float(0.0)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, Oct 02, 2006 at 07:53:34PM -0500, skip at pobox.com wrote:
Terry> "Kristján V. Jónsson" <kristjan at ccpgames.com> wrote: >> Anyway, Skip noted that 50% of all floats are whole numbers between >> -10 and 10 inclusive,
Terry> Please, no. He said something like this about Terry> non-floating-point applications (evidence unspecified, that I Terry> remember). But such applications, by definition, usually don't Terry> have enough floats for caching (or conversion time) to matter too Terry> much. Correct. The non-floating-point application I chose was the one that was most immediately available, "make test". Note that I have no proof that regrtest.py isn't terribly floating point intensive. I just sort of guessed that it was.
For my application caching 0.0 is by far the most important. 0.0 has ~200,000 references - the next highest reference count is only about ~200.
-- Nick Craig-Wood <nick at craig-wood.com> -- http://www.craig-wood.com/nick
- Previous message: [Python-Dev] Caching float(0.0)
- Next message: [Python-Dev] Caching float(0.0)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]