This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [C++0x] nullptr
- From: Paolo Carlini <paolo dot carlini at oracle dot com>
- To: Jason Merrill <jason at redhat dot com>
- Cc: Magnus Fromreide <magfr at lysator dot liu dot se>, gcc-patches at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org
- Date: Thu, 06 May 2010 23:04:06 +0200
- Subject: Re: [C++0x] nullptr
- References: <1268546192.2028.32.camel@sara.home> <4BA46E77.6080507@redhat.com> <1269813166.2249.8.camel@sara.home> <4BB12B74.80703@redhat.com> <4BDD0915.2020301@redhat.com> <1272842221.2000.26.camel@sara.home> <4BE32BEA.9010208@redhat.com>
Hi,
> Incidentally, library folks: does my change to gnu.ver look right? I
> noticed that the stuff I put there before was redundant.
you are exporting new symbols, and we released already something with
CXXABI_1.3.4, thus I think the new symbols should go in a new CXXABI_1.3.5.
About the old patterns, it depends what you mean by "redundant": in
general, certainly you cannot un-export symbols at a version #
corresponding to an already released library, but if you mean that those
patterns were essentially dead, weren't actually matching any real
symbols in the library, then can be certainly removed. Anyway,
make-check should be tight enough today to tell you.
Paolo.