public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Zdenko Bacik <zdenko.bacik@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: C++11 support
Date: Tue, 26 Feb 2013 09:10:00 -0000	[thread overview]
Message-ID: <CAH6eHdTrfwOh3nJZaKD8AG=cVoF-a_1e2Kg1zBVDgL5C309zKw@mail.gmail.com> (raw)
In-Reply-To: <CAGeENnxsXzaZS1kVUJH4fn_NzwWQaKcSg5M=YZ-fXipVS9M5uQ@mail.gmail.com>

On 26 February 2013 09:04, Zdenko Bacik wrote:
> Dear GCC team,
>
> I would like to ask you, if you have any time schedule plan to support
> for C++11 as a non-experimental version ?
> I couldn't find this kind of information on your website.

There is no schedule.

See http://gcc.gnu.org/ml/gcc/2013-01/msg00247.html and
http://gcc.gnu.org/ml/gcc/2013-01/msg00265.html

There are some important standard library changes that won't be done
before GCC 4.9, such as switching to a std::string that doesn't use
reference-counting.

      reply	other threads:[~2013-02-26  9:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-26  9:05 Zdenko Bacik
2013-02-26  9:10 ` Jonathan Wakely [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='CAH6eHdTrfwOh3nJZaKD8AG=cVoF-a_1e2Kg1zBVDgL5C309zKw@mail.gmail.com' \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=zdenko.bacik@gmail.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).