public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "b.r.longbons at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/64626] New: C++14 single quote should not always be a digit separator Date: Fri, 16 Jan 2015 08:12:00 -0000 [thread overview] Message-ID: <bug-64626-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64626 Bug ID: 64626 Summary: C++14 single quote should not always be a digit separator Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: b.r.longbons at gmail dot com Created attachment 34459 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34459&action=edit informative testcase During preprocessing, single quote (') should only be considered a digit separator if it is followed by a digit or nondigit. If it is followed by any other character, it should be considered as the start of a new character-literal, not part of the current pp-number. I am aware of exactly 2 other cases where a preprocessing-token needs to consume 2 characters or none at all (. -> ... and %: -> %:%:), and gcc seems to handle them correctly. (There is also the <:: case which looks ahead two characters to *not* consume a character). Unimplemented: gcc 4.8 Bad: Debian gcc 4.9.1-19 Bad: gcc 5.0.0 snapshot from 20141228 Good: Debian clang 3.4, 3.5, and svn snapshot of 3.6
next reply other threads:[~2015-01-16 8:12 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-16 8:12 b.r.longbons at gmail dot com [this message] 2015-01-16 8:22 ` [Bug c++/64626] " b.r.longbons at gmail dot com 2015-03-05 23:52 ` emsr at gcc dot gnu.org 2015-03-17 0:51 ` emsr at gcc dot gnu.org 2015-03-17 23:39 ` 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-64626-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).