Hi all,

Sorry to interrupt in the middle of the discussion, but it seems there are
quite a few GC methods, and everybody is fighting for the one he feels is
right... But why fight, when we can integrate all these things and let the
user choose?

There's already such a possible choice, at a different level: standard
containers. If the user needs to store a sequence of values, there's a
choice between many containers, and depending on the intended use, there are
better choices than others. I usually have a look at the table in Stroustrup
TC++PL 3ed 17.1.2, which lists pros and cons of each container, before I
make my choice.

My uninformed guess is that GC could be a set of allocator-based classes,
and there could be many choices, with differences such as with/without
finalizers, single/multi-threaded, with/without cross-links, etc., and
include smart pointers solutions as well...

Well, I guess there will still be fights to know which ones to include, but
at least, it should be more livable than trying to force *one* standard GC
down everybody's throats...

Comments, ideas?

Have a good day,
Gerald.


---
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://www.jamesd.demon.co.uk/csc/faq.html                       ]