[Python-Dev] Int FutureWarnings and other 2.4 TODOs (original) (raw)
Delaney, Timothy C (Timothy) tdelaney at avaya.com
Sun Dec 7 17:57:18 EST 2003
- Previous message: [Python-Dev] Where to report PyPI problem?
- Next message: [Python-Dev] Int FutureWarnings and other 2.4 TODOs
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
From: Aahz
Hmmmm... How important is the "less memory" angle versus the "faster" angle? Why not just add a few bytes to the long type to store an int? If you're using the int, the pointer is NULL, and you're saving that memory, at least. The only harm is some extra memory in the type object.
One thing I can immediately think of is that you're likely to see cache effects much sooner. In that case, you'll probably find that you've ended up with higher memory usage and lower performance. The best of both worlds :)
Tim Delaney
- Previous message: [Python-Dev] Where to report PyPI problem?
- Next message: [Python-Dev] Int FutureWarnings and other 2.4 TODOs
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]