Home |
Search |
Today's Posts |
#4
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
Deep behind the scenes, Integers are converted to Longs, since a
32-bit integer is the coin of the realm of (32-bit) processors. Memory is so cheap (I recently bought 8 GB for a small fraction of what I originally paid to upgrade 4 MB to 8 MB back in the day) that you don't really have to worry about optimizing memory usage. Moreover, if you are really that concerned about memory usage, VBA is definitely the wrong language to be using in the first place. With rare exceptions, you can completely disregard Integers and Singles and always use Longs and Doubles. Cordially, Chip Pearson Microsoft MVP 1998 - 2010 Pearson Software Consulting, LLC www.cpearson.com [email on web site] On Sat, 13 Feb 2010 05:31:01 -0800, Neal Zimm wrote: Hi All, I come from a day when storage was a LOT dearer than it is today. I use Integer or Long for whole # values 'cuz I read once that Integer takes less memory. It's also kind of self documenting about the size of the #. With memory gigs now about the size of a thumbnail, what are the major pro's and cons of still using As Integer versus As Long. Thanks. |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
VBA code optimization - why using long instead of integer? | Excel Programming | |||
GMT/UTC considerations | Excel Worksheet Functions | |||
Declaring variables (Long, String, Integer) and interpretation spe | Excel Programming | |||
Hash a range, output a Long Integer? | Excel Programming | |||
calculate/concert long/integer to date time | Excel Programming |