public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/52485] [c++11] add an option to disable c++11 user-defined literals
Date: Sun, 04 Mar 2012 22:56:00 -0000	[thread overview]
Message-ID: <bug-52485-4-YJ0zpo8dJI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52485-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52485

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-03-04 22:56:18 UTC ---
I think we should not have an option to disable user-defined literals at all. 
Since their code is not C++11, they should fix their code to be C++11 if they
use the -std=c++11/-std++0x option.


  reply	other threads:[~2012-03-04 22:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-04 20:58 [Bug c++/52485] New: " eu at doxos dot eu
2012-03-04 22:56 ` pinskia at gcc dot gnu.org [this message]
2012-03-05  8:55 ` [Bug c++/52485] " eu at doxos dot eu
2012-03-05  9:07 ` jakub at gcc dot gnu.org
2012-03-05  9:20 ` eu at doxos dot eu
2012-11-12 15:00 ` paolo.carlini at oracle dot com

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=bug-52485-4-YJ0zpo8dJI@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).