From: Ed Smith-Rowland <3dw4rd@verizon.net>
To: Jason Merrill <jason@redhat.com>,
Andrew Sutton <andrew.n.sutton@gmail.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
Braden Obrzut <admin@maniacsvault.net>
Subject: Re: [c++-concepts] Fix assertion failure with cp_maybe_constrained_type_specifier
Date: Fri, 27 Jun 2014 13:41:00 -0000 [thread overview]
Message-ID: <53AD747E.2080700@verizon.net> (raw)
In-Reply-To: <53ACE4CD.5030104@redhat.com>
On 06/26/2014 11:28 PM, Jason Merrill wrote:
> On 06/26/2014 09:38 PM, Ed Smith-Rowland wrote:
>> So is C++14 a done deal with a __cplusplus date and all?
>
> The C++14 draft was finalized at the February meeting in Issaquah; the
> ratification process isn't quite done, but I haven't heard any reason
> to doubt that it will be done soon. The __cplusplus date is 201402L.
I guess we should set this correctly in libcpp/init.c or wherever. Do
you see a problem with changing it from its current value of 201300? We
don't use the actual number AFAICT. I guess we could also use a fake
date for c++1z/c++17. Say 201500?
>
>> I've been thinking of adding a thing or two to C++1z like clang has -
>> The Disabling trigraph expansion by default looks easy.
>
> Aren't trigraphs off by default already?
>
They are *off* by default with gnu++NN and *on* by default with c++NN.
We want them *off* by default for all (gnu|c)++(1z|17). But -trigraphs
will restore them for all versions.
> Jason
>
>
next prev parent reply other threads:[~2014-06-27 13:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 19:27 Ed Smith-Rowland
2014-06-25 14:03 ` Andrew Sutton
2014-06-26 15:15 ` Ed Smith-Rowland
2014-06-26 16:23 ` Jason Merrill
2014-06-26 18:16 ` Jason Merrill
2014-06-27 1:38 ` Ed Smith-Rowland
2014-06-27 3:28 ` Jason Merrill
2014-06-27 13:41 ` Ed Smith-Rowland [this message]
2014-06-27 20:41 ` Jason Merrill
-- strict thread matches above, loose matches on Subject: below --
2014-06-24 12:07 Ed Smith-Rowland
2014-06-24 12:28 ` Andrew Sutton
2014-06-24 15:31 ` Ed Smith-Rowland
2014-06-24 15:43 ` Ed Smith-Rowland
2014-06-24 16:16 ` Andrew Sutton
2014-06-17 8:54 Braden Obrzut
2014-06-24 11:40 ` Andrew Sutton
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=53AD747E.2080700@verizon.net \
--to=3dw4rd@verizon.net \
--cc=admin@maniacsvault.net \
--cc=andrew.n.sutton@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.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).