public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "3dw4rd at verizon dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/54413] Option for turning off compiler extensions for -std=c++11 with respect to complex/fixed-point numbers missing
Date: Mon, 01 Oct 2012 18:47:00 -0000	[thread overview]
Message-ID: <bug-54413-4-eWeOpb1jVd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54413-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #5 from Ed Smith-Rowland <3dw4rd at verizon dot net> 2012-10-01 18:47:33 UTC ---
If I remember correctly, we are supposed to parse compiler-specific extensions
before UDLs - i.e.  The compiler extensions get dibs.  

I guess that's not the issue.  You propose being able to turn off (presumably
all?) gcc-specific suffix extensions.  Presumably, these should be on by
default for C++1*?  I agree we should have something like this.

Detecting at the level of c-family or the lexer whether c++ has seen a
definition of operator"" r or i could be ... real interesting.

Perhaps we could "move" these gnu extensions to:
namespace __gnucxx{
  operator"" r()
}
somehow.


  parent reply	other threads:[~2012-10-01 18:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-30  8:19 [Bug c++/54413] New: " p4spam at hispeed dot ch
2012-08-30  9:11 ` [Bug c++/54413] " jakub at gcc dot gnu.org
2012-08-30  9:55 ` redi at gcc dot gnu.org
2012-08-30 10:04 ` jakub at gcc dot gnu.org
2012-10-01 16:52 ` paolo.carlini at oracle dot com
2012-10-01 18:47 ` 3dw4rd at verizon dot net [this message]
2012-10-15 21:08 ` 3dw4rd at verizon dot net
2012-10-15 21:17 ` peter.sommerlad at hsr dot ch
2012-10-15 21:19 ` redi at gcc dot gnu.org
2012-10-15 21:21 ` peter.sommerlad at hsr dot ch
2012-10-15 21:25 ` 3dw4rd at verizon dot net
2012-11-05  4:50 ` 3dw4rd at verizon dot net
2012-11-05  4:56 ` 3dw4rd at verizon dot net
2012-11-06 17:55 ` 3dw4rd at verizon dot net
2012-11-12  5:39 ` 3dw4rd at verizon dot net
2012-11-12  9:12 ` redi at gcc dot gnu.org
2012-11-12 17:48 ` 3dw4rd at verizon dot net
2012-11-12 18:30 ` redi at gcc dot gnu.org
2012-11-14 13:07 ` 3dw4rd at verizon dot net
2012-11-14 13:18 ` paolo.carlini at oracle dot com
2012-11-14 13:21 ` redi at gcc dot gnu.org

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-54413-4-eWeOpb1jVd@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).