Prev: Function lookup as metaprogramming
Next: Why you should never use a const& parameter to initialize a const& member variable!
From: Goran on 5 Feb 2010 02:47
On Feb 5, 11:34 am, Brian <c...(a)mailvault.com> wrote:
> > ...Note also that for small values of numFoo, you're mightily wasting
> > storage (that's IMO the number 2 reason why one should never use fixed-
> > size storage, number 1 being "what if you need element 5001 and there
> > __indeed is__ space for it on the heap?").
>
> I think you're going overboard here. Fixed-size storage is one way
> to describe a uint32_t. I don't think you would suggest avoiding
> fixed-size integer types.

Haha, good one. Yes, of course, my thoughts above apply to containers
(to data containing multiples of uint32_t).

Goran.


--
[ See http://www.gotw.ca/resources/clcm.htm for info about ]
[ comp.lang.c++.moderated. First time posters: Do this! ]

First  |  Prev  | 
Pages: 1 2 3
Prev: Function lookup as metaprogramming
Next: Why you should never use a const& parameter to initialize a const& member variable!