From: "罗勇刚(Yonggang Luo) " <luoyonggang@gmail.com>
To: Joerg Schilling <Joerg.Schilling@fokus.fraunhofer.de>
Cc: vapier@gentoo.org, musl@lists.openwall.com,
John Sully <john@csquare.ca>,
James McNellis <james@jamesmcnellis.com>,
hsutter@microsoft.com, dplakosh@cert.org,
Rich Felker <dalias@libc.org>, Clang Dev <cfe-dev@cs.uiuc.edu>,
Karsten Blees <blees@dcon.de>,
austin-group-l@opengroup.org
Subject: Re: 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: Tue, 12 May 2015 11:21:31 +0800 [thread overview]
Message-ID: <CAE2XoE9oaeyH_KQ8pYufM9qMN9ur2uNCe2VAejCWX_TW3gENfQ@mail.gmail.com> (raw)
In-Reply-To: <5550842c.kMHzeizlOZv+0r6r%Joerg.Schilling@fokus.fraunhofer.de>
>
> I remember that a while ago (probably around 2001), Microsoft tried to reword
> POSIX to permit 16 bit characters by default to make their interface POSIX
> compliant. This caused a long discussion that ended with the conclusion, that
> we cannot do that.
That's really a long time ago, things are changed time to time.
Suppose we drop the support for wchar_t for POSIX, then there is still
a cross-platform subset we could use. And that's truly we want.
In real world, there is so much Compromise, I was intent to developing
a cross-platform subset C runtime API to makes some app development
ease.
Such as git. There is a large set of application and libraries that
suffering there is a cross-platfrom subset POSIX C runtime to use, so
for the cross-platform support, they have to sacrifice the code
elegance and using all kinds of tricks to work around
for those APIs.
--
此致
礼
罗勇刚
Yours
sincerely,
Yonggang Luo
next prev parent reply other threads:[~2015-05-12 3:21 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 ` [cfe-dev] " Szabolcs Nagy
[not found] ` <20150509103645.GG29035-4P1ElwuDYu6sTnJN9+BGXg@public.gmane.org>
2015-05-09 11:19 ` 罗勇刚(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) [this message]
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=CAE2XoE9oaeyH_KQ8pYufM9qMN9ur2uNCe2VAejCWX_TW3gENfQ@mail.gmail.com \
--to=luoyonggang@gmail.com \
--cc=Joerg.Schilling@fokus.fraunhofer.de \
--cc=austin-group-l@opengroup.org \
--cc=blees@dcon.de \
--cc=cfe-dev@cs.uiuc.edu \
--cc=dalias@libc.org \
--cc=dplakosh@cert.org \
--cc=hsutter@microsoft.com \
--cc=james@jamesmcnellis.com \
--cc=john@csquare.ca \
--cc=musl@lists.openwall.com \
--cc=vapier@gentoo.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.
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).