Re: [Boost-users] [containers] defining the insertion point of non-unique keys

Subject: Re: [Boost-users] [containers] defining the insertion point of non-unique keys
From: Joaquin M Lopez Munoz (joaquin_at_[hidden])
Date: 2009-12-18 10:30:31

Olaf Krzikalla <olaf.krzikalla <at> tu-dresden.de> writes:

> 
> Hi again,
> 
> I think I got it. I overread the "prior" in:
> 
> "t is inserted as close as possible to the position just prior to p."
> 
> To a certain degree the position described above can be seen as the 
> position between p and its predecessor (if it exists), can't it?

No, it's more general than this: assume we've got a container
with elements

  a1, a2, ... , an, k1, k2, ... , km, b1, b2, ... , bl

where k1, ... , km are equivalent (and the rest are not
equivalent to these). Put A=[a1,k1), K=[k1,b1), B=[b1,end]. Now
if we insert an element equivalent to these in K using hint p,
then:

* if p is in A, insertion takes place before k1,
* if p is in K, insertion takes place before p,
* if p is in B, insertion takes place before b1.

> Thus boost:multindex complies to N1780(?).

Yes.

Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo