This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
RE: breaking compatibility
- To: <libstdc++ at gcc dot gnu dot org>
- Subject: RE: breaking compatibility
- From: "Loren Osborn" <loren at reflexive dot net>
- Date: Tue, 13 Feb 2001 18:58:05 -0800
This would be fine... How do I go about including the old headers (without
adding any compiler specific code... hopefully)...
Best regards,
Loren
-P.S. Thanks for the quick response.
-----Original Message-----
From: libstdc++-owner@gcc.gnu.org [mailto:libstdc++-owner@gcc.gnu.org]On
Behalf Of Nathan Myers
Sent: Tuesday, February 13, 2001 6:49 PM
To: libstdc++@gcc.gnu.org
Subject: Re: breaking compatibility
On Tue, Feb 13, 2001 at 06:16:52PM -0800, Loren Osborn wrote:
> I hate to write in and complain, because I know that gcc is a great piece
of
> software, and know how much it has plowed the way for other open-sourced
> projects, but I've run into some persisting issues with gcc (as it is in
> CVS) that are really starting to annoy me.
> ... most of the reason why our code doesn't
> compile with the current CVS gcc has to do with the folding of
> libstdc++v3 that's begun to be folded into the mainstream over
> the last few months.
>
> It frustrates me greatly that either I'm forced to use old, broken
> versions of gcc, or port our code-base to gcc once again.
You have a third choice: the old, buggy libstdc++-v2 is (IINM) still there.
Nathan Myers
ncm at cantrip dot org