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++/61057] [C++11] operator . considered part of User Defined Literal invocation. Date: Wed, 09 Jul 2014 15:58:00 -0000 [thread overview] Message-ID: <bug-61057-4-1oZAolgEIO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61057-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61057 emsr at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #2 from emsr at gcc dot gnu.org --- As someone who has dabbled in Ruby I am sympathetic to the request to have this work. After looking at the standard language and our implementation I must conclude that your code is invalid. I then tried to imagine a way, for example, if the stuff after a dot could not be a mantissa stop processing chars at the dot so the remainder can become an invocation or access. Unfortunately, 123. is a valid double so this idea can't work even as an extension. FWIW, character and string user-defined literals can have invocations like "Hello, World!!!"s.length(). Perhaps two dots could signal a termination of a literal as was tried for '_' as digit separator. This would require much noodling by the standards folks though. I'll ponder this last idea but I'll mark this as resolved invalid.
next prev parent reply other threads:[~2014-07-09 15:58 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 ` [Bug c++/61057] " redi at gcc dot gnu.org 2014-07-09 15:58 ` emsr at gcc dot gnu.org [this message] 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-1oZAolgEIO@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).