Re: std::map of differente std::vectors

From:

Ulrich Eckhardt <eckhardt@satorlaser.com>

Newsgroups:

microsoft.public.vc.stl

Date:

Mon, 14 Apr 2008 09:38:06 +0200

Message-ID:

<08ebd5-d3i.ln1@satorlaser.homedns.org>

Andre Casteliano wrote:

Well, doing this I can loop through items of my map

... and do what with them? What do you need to do generically?

Well, basically operations that check for the state of the object and
perform some serialization under certain circunstances.

Okay, so I'd simply assume that you have a common interface for
serialisation, which means a baseclass typically. Further, you have a kind
of registry, where "all objects" are stored, so you can iterate over all of
them in order to store them.

Please note that it?s already working today, I just want to make it
more 'smart' and less error prone (lots of code that look almost identical
don?t seems 'right' to me).

You might be able to use a template function to serialise different kinds of
objects. Then, you neither have to derive from a common baseclass (you only
need a common interface) nor do you have to store all of them in the same
container, only make one function call per object type.

Now I need to write lots of similar functions like:

ControllerClass::GetCustomerVector() { return m_vecCustomers; }

Well, all these functions have a different return type (which I can't
help but notice you are conveniently omitting in your examples).

Yeah, I just omitted the return types, but they are implicit.
std::vector<Customer>

O RLY? Aren't they sometimes vector<Supplier> or vector<Product> for
GetSupplierVector() and GetProductVector()?

Uli