From: Joe Buck <jbuck@synopsys.com>
To: mroth@arago.de (Michael Roth)
Cc: egcs@cygnus.com
Subject: Re: std::auto_ptr bugs
Date: Mon, 06 Apr 1998 15:25:00 -0000 [thread overview]
Message-ID: <199804061628.JAA04166@atrus.synopsys.com> (raw)
In-Reply-To: <Pine.SGI.3.96.980405203848.2680E-100000@newton.arago.de>
> First, the std::auto_ptr is commented out in "memory" (egcs 1.0.*)
> and their is a note that the class is still discussed by the C++
> standardization committee. Is this really true ?
It's no longer true ... the standardization committee made a final
decision, at the very end of '97 just in time for the vote (this final
decision is not the same as the CD2 draft that you can find everywhere on
the web, unfortunately). I haven't checked to see if the commented-out
version matches that decision or not.
But you're right, there are multiple errors in the commented-out version.
That file comes unmodified from SGI's STL, so we need to pass bug reports
on to them.
next prev parent reply other threads:[~1998-04-06 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-05 17:27 Michael Roth
1998-04-06 15:25 ` Joe Buck [this message]
1998-04-13 12:16 Thomas Hoyt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199804061628.JAA04166@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=egcs@cygnus.com \
--cc=mroth@arago.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).