On Sun, 27 Aug 2000 06:14:00 -0700, Matt Youell wrote: >So an int gets stored as two bytes and not >four or eight. Gee, I thought it was more like 30. The savings in bytes don't look too impressive in this case. 4 byte addition is as fast as 2 byte addition on most pmodern platforms -- and you definitely may ignore any difference with regards to Perl's general overhead. Actually I wouldn't mind a variable-length integer, BigInt, as a standard type. Take no more bytes than you need. But expand if it's necessary. -- Bart.
- Re: RFC 161 (v2) OO Integration/Migration Path Nathan Wiger
- Re: RFC 161 (v2) OO Integration/Migration Path Matt Youell
- Re: RFC 161 (v2) OO Integration/Migration Path Nathan Wiger
- Re: RFC 161 (v2) OO Integration/Migration ... Nathan Torkington
- Re: RFC 161 (v2) OO Integration/Migrat... Nathan Wiger
- Re: RFC 161 (v2) OO Integration/Migrat... Randal L. Schwartz
- Re: RFC 161 (v2) OO Integration/M... Nathan Wiger
- Re: RFC 161 (v2) OO Integration/M... Matt Youell
- Re: RFC 161 (v2) OO Integration/Migration ... Matt Youell
- Re: RFC 161 (v2) OO Integration/Migrat... Nathan Wiger
- Re: RFC 161 (v2) OO Integration/Migrat... Bart Lateur
- Re: RFC 161 (v2) OO Integration/Migration Path Nathan Torkington
- Re: RFC 161 (v2) OO Integration/Migration ... Matt Youell
- Re: RFC 161 (v2) OO Integration/Migrat... Nathan Wiger
- Re: RFC 161 (v2) OO Integration/M... Matt Youell
- Re: RFC 161 (v2) OO Integration/Migration Path Nathan Torkington
- Re: RFC 161 (v2) OO Integration/Migration Path Dan Sugalski
- Re: RFC 161 (v2) OO Integration/Migration Path Steve Fink
- Re: RFC 161 (v2) OO Integration/Migration ... Dan Sugalski
- Re: RFC 161 (v2) OO Integration/Migration ... Nathan Wiger
- Re: RFC 161 (v2) OO Integration/Migration Path Nathan Wiger