public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "emsr at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/60209] Declaration of user-defined literal operator cause error
Date: Mon, 12 May 2014 13:52:00 -0000	[thread overview]
Message-ID: <bug-60209-4-HX7YfyyGRv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60209-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from emsr at gcc dot gnu.org ---
Created attachment 32779
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32779&action=edit
Just parse a whole string instread of consuming one token.

This builds and tests clean on x86_64-linux.

I would like to hold out for a slightly better design that could simplifiy code
a tiny bit and handle maybe these:

void operator "" "" _x(unsigned long long); // This patch diagnoses this.

void operator "" "boo" _y(unsigned long long); // I'd like to diagnose this.

void operator "" u"" _u(unsigned long long); // I'd like to diagnose this.

void operator u"" "" _v(unsigned long long); // Diagnosed correctly now.

void operator "" ""_w(unsigned long long); // This might be harder/messier and
may be out of scope.


  parent reply	other threads:[~2014-05-12 13:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-15  4:29 [Bug c++/60209] New: " kariya_mitsuru at hotmail dot com
2014-02-16 17:30 ` [Bug c++/60209] " daniel.kruegler at googlemail dot com
2014-05-11 14:44 ` paolo.carlini at oracle dot com
2014-05-12 13:52 ` emsr at gcc dot gnu.org [this message]
2014-05-12 13:54 ` emsr at gcc dot gnu.org
2014-07-13 13:37 ` emsr at gcc dot gnu.org
2014-07-13 13:40 ` 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-60209-4-HX7YfyyGRv@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).