From: Paolo Carlini <pcarlini@suse.de>
To: Joe Buck <Joe.Buck@synopsys.COM>
Cc: chris jefferson <caj@cs.york.ac.uk>,
Ed Smith-Rowland <3dw4rd@verizon.net>,
gcc@gcc.gnu.org
Subject: Re: Mention addition of TR1 to C++ for GCC-4.0.0
Date: Tue, 07 Dec 2004 22:38:00 -0000 [thread overview]
Message-ID: <41B63123.4010305@suse.de> (raw)
In-Reply-To: <20041207143316.A16598@synopsys.com>
Joe Buck wrote:
>Nevertheless, we could use a note documenting the parts of TR1 that will
>be in 4.0.0, how to use it, etc., and make sure to warn people that it is
>experimental (meaning that the libstdc++ team makes no promises about
>backward compatibility, so the users might have to revise their programs
>later on should the committee make changes).
>
>
I concur and would like to add that some facilities, like <tuple>
prepared by
Chris, are already rather close to the final form!
Paolo.
prev parent reply other threads:[~2004-12-07 22:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-07 13:52 Ed Smith-Rowland
2004-12-07 13:59 ` chris jefferson
2004-12-07 22:33 ` Joe Buck
2004-12-07 22:38 ` Paolo Carlini [this message]
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=41B63123.4010305@suse.de \
--to=pcarlini@suse.de \
--cc=3dw4rd@verizon.net \
--cc=Joe.Buck@synopsys.COM \
--cc=caj@cs.york.ac.uk \
--cc=gcc@gcc.gnu.org \
/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).