From: Samuel Thibault <samuel.thibault@gnu.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] curses: build with -std=gnu99
Date: Thu, 27 Oct 2016 18:36:56 +0200 [thread overview]
Message-ID: <20161027163656.GA6263@var.home> (raw)
In-Reply-To: <CAFEAcA-33S9Mb-bDxxHdBhJW14MwxCyuJJKYsFPZk+YXLc2+qw@mail.gmail.com>
Peter Maydell, on Thu 27 Oct 2016 17:14:52 +0100, wrote:
> On 27 October 2016 at 16:58, Samuel Thibault <samuel.thibault@gnu.org> wrote:
> > Gerd Hoffmann, on Thu 27 Oct 2016 17:55:47 +0200, wrote:
> >> /home/kraxel/projects/qemu/ui/curses.c:627:18: error: universal
> >> character names are only valid in C++ and C99 [-Werror]
> >> case L'\u23bd':
> >
> > Another way could be to assume unicode encoding of wchar_t characters
> > (which looks very reasonable to me) and just write "case 0x23bd:".
>
> Does this still work if you're using curses on mingw32?
Windows' wchar_t uses unicode encoding, yes (and its limitation to 16bit
doesn't pose problem to the values we care about).
Samuel
next prev parent reply other threads:[~2016-10-27 16:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 11:46 [Qemu-devel] [PATCH] curses: build with -std=gnu99 Gerd Hoffmann
2016-10-27 15:04 ` Peter Maydell
2016-10-27 15:55 ` Gerd Hoffmann
2016-10-27 15:58 ` Samuel Thibault
2016-10-27 16:14 ` Peter Maydell
2016-10-27 16:36 ` Samuel Thibault [this message]
2016-10-27 16:52 ` Peter Maydell
2016-10-27 17:02 ` Samuel Thibault
2016-10-28 6:51 ` Markus Armbruster
2016-10-28 7:40 ` Samuel Thibault
2016-10-28 8:37 ` Markus Armbruster
2016-10-28 9:45 ` Gerd Hoffmann
[not found] <mailman.13406.1477569887.22738.qemu-devel@nongnu.org>
2016-10-27 14:51 ` G 3
2016-10-27 15:07 ` Gerd Hoffmann
2016-10-27 15:12 ` G 3
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=20161027163656.GA6263@var.home \
--to=samuel.thibault@gnu.org \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).