From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: Joe Buck <Joe.Buck@synopsys.com>,
Jason Merrill <jason@redhat.com>,
Nathan Ridge <zeratul976@hotmail.com>,
gcc@gcc.gnu.org
Subject: Re: C++11 no longer experimental
Date: Sun, 30 Oct 2011 14:50:00 -0000 [thread overview]
Message-ID: <CAH6eHdQqG_wgozcxFgVSxQ0cJzVESutpBwF+OgvXGcv0+27tGg@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1110301411500.3250@gerinyyl.fvgr>
On 30 October 2011 13:14, Gerald Pfeifer wrote:
> @@ -9,11 +9,11 @@
> </head>
>
> <body>
> - <h1>C++0x Support in GCC</h1>
> + <h1>C++0x/C++11 Support in GCC</h1>
>
> - <p>C++0x is the working name of the next ISO C++ standard, due by
> - the end of this decade, which introduces a host of new features into
> - the standard C++ language and library. This project seeks to
> + <p>C++0x was the working name of a new ISO C++ standard, which then
> + was released in 2011 as C++11 and introduces a host of new features
> + into the standard C++ language and library. This project seeks to
> implement new C++0x features in GCC and to make it one of the first
> compilers to bring C++0x to C++ programmers.</p>
Just a small point of style: I think "which was then released" reads
a bit more naturally than "which then was released"
next prev parent reply other threads:[~2011-10-30 13:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 17:51 Nathan Ridge
2011-09-21 17:58 ` James Dennett
2011-09-21 18:01 ` Jonathan Wakely
2011-09-21 18:07 ` Jonathan Wakely
2011-09-21 18:26 ` Joe Buck
2011-09-21 18:34 ` Jonathan Wakely
2011-09-21 19:52 ` Jonathan Wakely
2011-10-30 14:04 ` Gerald Pfeifer
2011-10-30 14:50 ` Jonathan Wakely [this message]
2011-10-30 18:27 ` Oleg Endo
2011-10-31 5:37 ` Gerald Pfeifer
2011-10-31 9:36 ` Jason Merrill
2011-11-01 3:56 ` Jason Merrill
2011-10-30 19:20 ` Jonathan Wakely
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=CAH6eHdQqG_wgozcxFgVSxQ0cJzVESutpBwF+OgvXGcv0+27tGg@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=Joe.Buck@synopsys.com \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=jason@redhat.com \
--cc=zeratul976@hotmail.com \
/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).