From: Samuel Thibault <samuel.thibault@gnu.org>
To: Markus Armbruster <armbru@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Gerd Hoffmann <kraxel@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] curses: build with -std=gnu99
Date: Fri, 28 Oct 2016 09:40:39 +0200 [thread overview]
Message-ID: <20161028074039.GN6263@var.home> (raw)
In-Reply-To: <87mvhp55lj.fsf@dusky.pond.sub.org>
Markus Armbruster, on Fri 28 Oct 2016 08:51:20 +0200, wrote:
> Samuel Thibault <samuel.thibault@gnu.org> writes:
>
> > Peter Maydell, on Thu 27 Oct 2016 17:52:17 +0100, wrote:
> >> http://www.thecodingforums.com/threads/wchar_t-is-useless.806149/#post-4398211
> >
> > UURrgll... So we can't use L'\u23bd' on such systems, it would just not
> > work either, we have to use iconv to get these right...
>
> I guess we can if they actually bother to conform to C99. 6.4.3
> Universal character names:
>
> The universal character name \Unnnnnnnn designates the character
> whose eight-digit short identifier (as specified by ISO/IEC 10646)
> is nnnnnnnn. Similarly, the universal character name \unnnn
> designates the character whose four-digit short identifier is nnnn
> (and whose eight-digit short identifier is 0000nnnn).
>
> Note that it doesn't say here that L'\u23bd' should be equal to 0x23bd.
I know, but as discussed in the thread, that could only work if gcc
embeds something like calls to nl_langinfo and iconv to properly convert
from the unicode value to the proper wchar_t according to the locale. I
wouldn't be surprised that they don't.
Samuel
next prev parent reply other threads:[~2016-10-28 7:40 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
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 [this message]
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=20161028074039.GN6263@var.home \
--to=samuel.thibault@gnu.org \
--cc=armbru@redhat.com \
--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).