🚀 go-pugleaf

This should have been posted to gnu.g++.help.  Followups are directed
there.

dietmar.kuehl@uni-konstanz.de writes:
>The current implementation of STL in libg++ is filled with many
>workarounds for g++ bugs or missing g++ features.

To be fair, the original HP STL source is filled with workarounds for
other compilers' limitations (like bool.h for compilers that don't support
bool, etc).

>These workarounds
>will become obsolete as soon as g++ support more of the features of C++
>described in the C++ Standard Proposal.
>
>I have found a bug in STL which is likely to disappear with the
>workarounds (objects get constructed/destructed twice in lists). Is
>there a point in reporting such bugs?

I think that such things should be reported, simply so we're sure that
they will eventually get crossed off the list (when Rohan, Gordon, or
one of the other folks goes through the lists).  At least unless the
g++ maintainers disagree.

As an alternative, we could build a list of known limitations of the
libg++ STL version, and I could add it to the gnu.g++.help FAQ.  Ideally
I'd like for someone else who's used it more than I have to assemble
the list.


-- 
-- Joe Buck 	<jbuck@synopsys.com>	(not speaking for Synopsys, Inc)
Phone: +1 415 694 1729