public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "eu at doxos dot eu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/52485] New: [c++11] add an option to disable c++11 user-defined literals Date: Sun, 04 Mar 2012 20:58:00 -0000 [thread overview] Message-ID: <bug-52485-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52485 Bug #: 52485 Summary: [c++11] add an option to disable c++11 user-defined literals Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: eu@doxos.eu Some upstream code (e.g. #50917 for Mozilla, I have issues with Qt4's SLOT(...) macros) is broken because of the support for c++11 literals in 4.7. In all cases I've seen the cause was missing space between constructs like #define FOO(a) "0"#a. Sine this feature is little used, but lot of code, it would be reasonable to provide a switch to disable user-defined literals, so that code which needs c++11 but at the same time links to (technically broken) libs can be compiled, until those libs get fixed upstream.
next reply other threads:[~2012-03-04 20:58 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-04 20:58 eu at doxos dot eu [this message] 2012-03-04 22:56 ` [Bug c++/52485] " pinskia at gcc dot gnu.org 2012-03-05 8:55 ` 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@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: linkBe 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).