Re: C++ is Slow?

The array versus vector discussion seems more problematic. A couple
of people made the point that actually it's not down to using
vectors, it's how you use them, it's basically down to allocating
large blocks versus lots of small ones. It's a good point and I'll
keep it in mind.

The point was also made that if I decide to allocate large blocks
and calculate indexes then I should wrap this functionally in a
class.

I guess it would also make sense to wrap it in a class that has a
similar interface to vector, assuming this can be done? This way I
could pass vector or my own object as a template parameter and
easily switch between the two.

For my own VectorContiguous, I guess operator[] would have to
return a dummy object which could be automatically type converted
to the storage type of the VectorContiguous object? Has this
already been done?

It sounds like if pushed I should be able to create a drop in
replacement for vector that contiguously allocates memory. Whither
this is valuable or not seems to be an open question, and probably
architecture dependent.