All container constructors should have a variant taking an allocator as a final parameter

[Erik Jensen <Erik.Jensen@…>]

I am attempting to use the new allocator_traits functionality to facilitate a scoped_pointer work-alike. However, I am running into difficulties because there are a number of constructors that do not have a variant taking an allocator as a final parameter. For example, basic_string does not have a copy-constructor taking an allocator.

Thanks, Erik Jensen

[Ion Gaztañaga]

Sorry, the scoped allocator model is not implemented yet, let's see if I can find time to bring it in Boost 1.50. Thanks for the ticket.

[Erik Jensen <Erik.Jensen@…>]

Replying to igaztanaga:

Sorry, the scoped allocator model is not implemented yet, let's see if I can find time to bring it in Boost 1.50. Thanks for the ticket.

I know the model itself is not supported, but the new C++11 constructors are useful for more than just that, and it seems like implementation should be pretty simple. For example,

basic_string(const basic_string& s, const allocator_type& a) 
   :  base_t(a)
{ this->priv_range_initialize(s.begin(), s.end()); }

or

vector(const vector &x, const allocator_type &a)
: base_t(a)
{
   this->assign( container_detail::to_raw_pointer(x.members_.m_start)
               , container_detail::to_raw_pointer(x.members_.m_start + x.members_.m_size));
}

Of course, there are probably more complications that I am overlooking.

Thanks again for you consideration.

[Ion Gaztañaga]

Fixed in Boost 1.50