This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [Patch] My proposal for _Alloc_traits-free rope
- From: Phil Edwards <phil at codesourcery dot com>
- To: Benjamin Kosnik <bkoz at redhat dot com>
- Cc: pcarlini at suse dot de, libstdc++ at gcc dot gnu dot org, austern at apple dot com
- Date: Sat, 10 Jan 2004 10:32:11 -0500
- Subject: Re: [Patch] My proposal for _Alloc_traits-free rope
- References: <3FF0020A.7060804@suse.de> <20040106215201.2a9b0aa1.bkoz@redhat.com> <20040109184027.72990aca.bkoz@redhat.com>
On Fri, Jan 09, 2004 at 06:40:27PM -0600, Benjamin Kosnik wrote:
>
> >>Well, perhaps, 'rope' isn't really used that much these days and we had
> >>better
> >>spending our time elsewhere...
> >
> >I wonder about this too. It seems to be the single-biggest user of
> >deprecated bits. Should we just kill it?
>
> Any thoughts on this? The more I think about it, the more I think rope should go.
If basic_string performs comparably well on huge data, then I completely
agree.
If basic_string performs only tolerably well on huge data, then I still
mostly agree. Everyone knows it's an extension by now; portable users
don't use it.
Suggest we deprecate the whole thing for 3.4 (along with slist? hmmm)
and kill it in 3.5.
Phil
--
"What attribute do you consider most valuable to the politician?"
"To be able to raise a cause which shall produce an effect, and
then *fight the effect*."
- Captain T.W.S. Kidd and Senatorial candidate Abraham Lincoln