Re: Removing the assignable requirement from stl list elements
mzaytsev2@bloomberg.net wrote:
Kevin Lin wrote:
Denise Kleingeist wrote:
[...]
I would like to provide example of Usefullness:
class Mutex; // with some RAII implementation
std::list< Mutex > mutexes;
// Populate and use on demand
Mutex DOES NOT have copy semantic...
Have Mutexes be organized, allocated and destroyed by the
container I see usefull. For example I would like to iterate
through, and check.
For deadlock detection, for example. Yes, it is useful.
On the other hand, it is a very special use, which doesn't fit
into the concept of the STL in general---you can't make it work
with std::vector, for example. It presupposes that each element
of the list has identity, which is only true for std::list (and,
one could argue, only incidentally true there). I'm not sure
that making a lot of special rules for std::list, just to
support this "unorthodox" use, is a good idea.
--
James Kanze GABI Software
Conseils en informatique orient?e objet/
Beratung in objektorientierter Datenverarbeitung
9 place S?mard, 78210 St.-Cyr-l'?cole, France, +33 (0)1 30 23 00 34
--
[ See http://www.gotw.ca/resources/clcm.htm for info about ]
[ comp.lang.c++.moderated. First time posters: Do this! ]