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++/61038] g++ -E is unusable with UDL strings
Date: Mon, 12 May 2014 21:32:00 -0000	[thread overview]
Message-ID: <bug-61038-4-OCRPfS1ESk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61038-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61038

--- Comment #8 from Ben Longbons <b.r.longbons at gmail dot com> ---
(In reply to Ed Smith-Rowland from comment #7)
> Note to self: you DO need to take care of char...

What about multi-char constants, or are they not permitted in C++ UDLs?
Normally they get converted to int, so they're not *meaningful*, but ...

Also, remember the different prefixes: L for wchar_t, u8 for char-but-utf8, u
for char16_t, and U for char32_t

unsigned int fourcc = 'ABCD';


  parent reply	other threads:[~2014-05-12 21:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-02 20:11 [Bug c++/61038] New: " b.r.longbons at gmail dot com
2014-05-11  9:33 ` [Bug c++/61038] " paolo.carlini at oracle dot com
2014-05-12 14:12 ` emsr at gcc dot gnu.org
2014-05-12 14:12 ` emsr at gcc dot gnu.org
2014-05-12 14:49 ` emsr at gcc dot gnu.org
2014-05-12 17:59 ` 3dw4rd at verizon dot net
2014-05-12 18:50 ` paolo.carlini at oracle dot com
2014-05-12 21:22 ` 3dw4rd at verizon dot net
2014-05-12 21:32 ` b.r.longbons at gmail dot com [this message]
2014-05-12 21:37 ` daniel.kruegler at googlemail dot com
2014-05-21  0:36 ` emsr at gcc dot gnu.org
2014-05-21  0:56 ` emsr at gcc dot gnu.org
2014-06-05 11:12 ` emsr at gcc dot gnu.org
2014-06-05 11:18 ` 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-61038-4-OCRPfS1ESk@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).