public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pacoarjonilla at yahoo dot es" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/108717] New: pasting """_" and "µm" does not give a valid preprocessing token in user-defined literal operator Date: Wed, 08 Feb 2023 12:54:47 +0000 [thread overview] Message-ID: <bug-108717-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108717 Bug ID: 108717 Summary: pasting """_" and "µm" does not give a valid preprocessing token in user-defined literal operator Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: pacoarjonilla at yahoo dot es Target Milestone: --- The following code is accepted by clang and MSVC, but not GCC: $ g++-13 --std=c++2b ''' int operator""_µm(long double magnitude) noexcept // Micro sign, unicode 0x00b5 { return magnitude; } ''' But character 'µ' is unicode XID_Start, so it should be accepted. Compiler output: <source>:1:16: error: expected initializer before '\U000000b5m' 1 | int operator""_µm(long double magnitude) noexcept \ | ^~ Compiler returned: 1
next reply other threads:[~2023-02-08 12:54 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-08 12:54 pacoarjonilla at yahoo dot es [this message] 2023-02-08 13:57 ` [Bug c++/108717] Greek letters not accepted as part of identifier in user-defined literal operators redi at gcc dot gnu.org 2023-02-08 17:32 ` pinskia at gcc dot gnu.org 2023-02-08 17:38 ` pinskia at gcc dot gnu.org 2023-02-08 17:42 ` [Bug c++/108717] Greek letters not accepted as part of identifier in user-defined literal operators without a space pinskia 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-108717-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).