This is the mail archive of the
mailing list for the libstdc++ project.
Re: [libstdc++-v3] Remove std::construct and std::destroy
- To: Benjamin Kosnik <bkoz at redhat dot com>
- Subject: Re: [libstdc++-v3] Remove std::construct and std::destroy
- From: Phil Edwards <pedwards at disaster dot jaj dot com>
- Date: Mon, 2 Jul 2001 14:35:40 -0400
- Cc: "Stephen M. Webb" <stephen at bregmasoft dot com>, libstdc++ at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
- References: <01070108464800.00282@umbriel> <Pine.SOL.3.91.1010702124707.3859Aemail@example.com>
On Mon, Jul 02, 2001 at 12:48:57PM -0700, Benjamin Kosnik wrote:
> Hey Stephen. This is in, thanks.
> > Bootstrapped on an i686-pc-linux-gnu system, no regressions. Targetted at the
> > trunk but is good for the 3.01 branch, too.
> I just checked it in to the trunk. I'm uncertain what to do with patches
> that remove functions from std:: or otherwise change the library
> significantly. (Say this patch, or the iterator work.) Right now I'm now
> checking them into the branch, although this might be a mistake.
I think it's okay. Users who have been using 'std::<something nonstandard>'
are going to get bitten by their practices no matter what happens.
Would I had phrases that are not known, utterances that are strange, in
new language that has not been used, free from repetition, not an utterance
which has grown stale, which men of old have spoken.
- anonymous Egyptian scribe, c.1700 BC