"JOAQUIN LOPEZ MU?Z" <joaquin@tid.es> wrote in message news:1d38bf1d2e77.1d2e771d38bf@tid.es...
[...] Then again, not even the general feel of a std::set has to be met. Imagine a bunch of sequenced indices (like a lot of std::list without duplicate storage): this is not just a degenerate case (it might be useful) and it is definitely not a set.
On the other hand, you admitted yourself that none of the reviewers found the sequenced indices useful, so you're going to have a challenge coming up with a realistic use case for this "multi-list".
I agree "Multi" is probably too generic, and clashes with, for instace, multi_array. What about CompositeContainer for the lib (and composite_container for the class)? it matches the name of the concept it satisfies, it *is* some sort of container and it's certainly composite. Admittedly a bimap could be also a considered a composite container, but composite_container is *the* composite container, if you know what I mean.
I guess "composite_container" isn't too bad. However, it seems that indexing is the key concept (no pun intended), so it's too bad that it can't fit into the name nicely. "composite_index" just doesn't give you a good feel for what it does. Dave --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.581 / Virus Database: 368 - Release Date: 2/9/2004