Re: [Boost-users] [multi-index] Container not safe against reentrant clear() / erase() ?

Subject: Re: [Boost-users] [multi-index] Container not safe against reentrant clear() / erase() ?
From: Sebastian Theophil (stheophil_at_[hidden])
Date: 2009-06-05 03:55:03

> [long explanation snipped]
> 
> OK, thank you very much for the explanation. Sorry about
> having kept challenging your design, but I really couldn't
> see how you were in the situation you are. Now it's clear
> to me.

I'm glad I convinced you :-)
 
> But you can circumvent this simply by using
> 
>   erase(begin(),end())

Thanks for the information, I can live with that. How big is the performance impact when using erase(begin(), end()) vs clear()? Now I guess I'm challenging your design ;-) My only point is that in the few cases where the C++ standard defines the behavior of clear() for the STL containers, it simply says clear() should be equivalent to erase(begin(), end()). It is a bit surprising if the multi_index_container behaves differently in that regard.  

Thanks for your patience
Sebastian

--
Sebastian Theophil · stheophil_at_[hidden]
Software Engineer
 
think-cell Software GmbH · Invalidenstr. 34 · 10115 Berlin, Germany 
http://www.think-cell.com · phone [phone] · toll-free (US) [phone]
Directors: Dr. Markus Hannebauer, Dr. Arno Schoedl · Amtsgericht Berlin-Charlottenburg, HRB 85229