public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/61057] [C++11] operator . considered part of User Defined Literal invocation. Date: Sun, 04 May 2014 20:25:00 -0000 [thread overview] Message-ID: <bug-61057-4-kzHE7znxOQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61057-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61057 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |emsr at gcc dot gnu.org --- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> --- Reduced: class Int { public: constexpr Int(long long unsigned value) : m_value(value) {} const long long unsigned m_value; }; constexpr Int operator "" _i(long long unsigned i) { return Int(i); } auto x = 1_i.m_value; I think G++ is correct, the grammar in the standard defines 1_i.m_value as a pp-number, i.e. a single preprocessing token, which is treated as a literal, so _i.m_value is looked up as the suffix. Clang gives the same error.
next prev parent reply other threads:[~2014-05-04 20:25 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-05-04 18:18 [Bug c++/61057] New: " isupeene at ualberta dot ca 2014-05-04 20:25 ` redi at gcc dot gnu.org [this message] 2014-07-09 15:58 ` [Bug c++/61057] " emsr at gcc dot gnu.org 2014-07-09 16:04 ` emsr 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-61057-4-kzHE7znxOQ@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).