versioning C++ includes

Rainer Orth ro@TechFak.Uni-Bielefeld.DE
Tue Jun 25 16:03:00 GMT 2002


Phil Edwards writes:

> > Agreed.  I think the only option is for libstdc++ to get it's act together
> > and finally define and implement a stable ABI.  Vendor compilers have been
> > doing this for years, so it's certainly feasible,
> 
> Nobody has ever argued otherwise.
> 
> If you'd like to /help/ libstdc++ "get its act together," then feel free
> to submit patches addressing the ABI situation.  Preaching doesn't help.

Sorry if I sounded offensive.  But spending effort on workarounds for the
current situation (especially if this means intricate schemes with shared
libraries in ABI subdirs and some such, when shared library problems have
bitten me too much already and produce lots of user confusion) really seems
conterproductive, so I'd like to warn against them.

I'll probably provide patches (support interface versioning on Solaris 2),
but right now I'm working on a couple of other projects (and determining
the causes of various bootstrap and testsuite failures on non-GNU/Linux
platforms ;-).

So much to do, so little time :-)

	Rainer



More information about the Libstdc++ mailing list