This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: C++: STL 3.2

To: mark at codesourcery dot com
Subject: Re: C++: STL 3.2
From: "Martin v. Loewis" <martin at mira dot isdn dot cs dot tu-berlin dot de>
Date: Sun, 25 Apr 1999 22:01:49 +0200
CC: law at cygnus dot com, pfeifer at dbai dot tuwien dot ac dot at, egcs at egcs dot cygnus dot com
References: <1253.924996368@upchuck.cygnus.com> <199904250614.XAA13315@adsl-206-170-148-33.dsl.snfc21.pacbell.net>

> It *may be* that the 3.11 update in our current sources didn't break
> anything, but I don't think we can know that without a careful audit
> of what changed.  It's probably safest just to say that 1.2 is not
> binary compatible with 1.1.x, and, if possible, *enforce* that.

For the CVS, I did a little testing and found that every container
gives a link error. For example, allocating a vector<int> object with
the development branch will emit a call to

_._t6vector2ZiZt9allocator1Z

In the 1.1 branch, the same object will require a call to

_._t6vector2ZiZt24__default_alloc_template2b1i0

Same goes for functions expecting vectors, etc.

Regards,
Martin

References:
- Re: C++: STL 3.2
  - From: Jeffrey A Law
- Re: C++: STL 3.2
  - From: Mark Mitchell

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]