From: Szabolcs Nagy <nsz@port70.net>
To: John Sully <john@csquare.ca>
Cc: luoyonggang@gmail.com, blees@dcon.de, musl@lists.openwall.com,
dplakosh@cert.org, austin-group-l@opengroup.org,
hsutter@microsoft.com, Clang Dev <cfe-dev@cs.uiuc.edu>,
James McNellis <james@jamesmcnellis.com>
Subject: Re: [cfe-dev] Is that getting wchar_t to be 32bit on win32 a good idea for compatible with Unix world by implement posix layer on win32 API?
Date: Sat, 9 May 2015 12:36:45 +0200 [thread overview]
Message-ID: <20150509103645.GG29035@port70.net> (raw)
In-Reply-To: <CACVf4-6i_PNsetdeeY0nW=uASVGp=_yox40vL-iL4U8KWMoyXA@mail.gmail.com>
* John Sully <john@csquare.ca> [2015-05-09 00:55:12 -0700]:
> In my opinion you almost never want 32-bit wide characters once you learn
> of their limitations. Most people assume that if they use them they can
> return to the one character -> one glyph idiom like ASCII. But Unicode is
wchar_t must be at least 21 bits on a system that spports unicode
in any locale: it has to be able to represent all code points of the
supported character set.
in practice this means that the only conforming definition to iso c
(and thus posix, c++ and other standards based on c) is a 32bit wchar_t
(the signedness can be choosen freely).
so the definition is not based on what "you almost never want" or what
"most people assume".
if the goal is to provide a posix implementation then 16bit wchar_t
is not an option (assuming the system wants to be able to communicate
with the external world that uses unicode text).
next prev parent reply other threads:[~2015-05-09 10:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-09 3:16 罗勇刚(Yonggang Luo)
2015-05-09 3:32 ` Rich Felker
2015-05-09 3:36 ` 罗勇刚(Yonggang Luo)
[not found] ` <CAE2XoE_vO83dVqmJ3xRb9md8H=EO0j723Ycwqijo1To88iGueA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-09 7:55 ` John Sully
2015-05-09 10:36 ` Szabolcs Nagy [this message]
[not found] ` <20150509103645.GG29035-4P1ElwuDYu6sTnJN9+BGXg@public.gmane.org>
2015-05-09 11:19 ` [cfe-dev] " 罗勇刚(Yonggang Luo)
2015-05-09 20:05 ` Rich Felker
2015-05-10 12:19 ` 罗勇刚(Yonggang Luo)
2015-05-10 12:31 ` 罗勇刚(Yonggang Luo)
2015-05-10 13:42 ` Rich Felker
[not found] ` <20150510134230.GN17573-C3MtFaGISjmo6RMmaWD+6Sb1p8zYI1N1@public.gmane.org>
2015-05-10 14:15 ` [musl] " 罗勇刚(Yonggang Luo)
2015-05-10 15:30 ` Rich Felker
[not found] ` <CAE2XoE8ARm6BkarKYspPK_uDkePw8PewHXPWRXmT+mGM5mwEaw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-11 1:47 ` [musl] " Mike Frysinger
2015-05-11 3:25 ` 罗勇刚(Yonggang Luo)
2015-05-11 10:27 ` [musl] " Joerg Schilling
2015-05-12 3:21 ` 罗勇刚(Yonggang Luo)
2015-05-10 18:47 ` Karsten Blees
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=20150509103645.GG29035@port70.net \
--to=nsz@port70.net \
--cc=austin-group-l@opengroup.org \
--cc=blees@dcon.de \
--cc=cfe-dev@cs.uiuc.edu \
--cc=dplakosh@cert.org \
--cc=hsutter@microsoft.com \
--cc=james@jamesmcnellis.com \
--cc=john@csquare.ca \
--cc=luoyonggang@gmail.com \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).