From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/7627 Path: news.gmane.org!not-for-mail From: =?UTF-8?B?572X5YuH5YiaKFlvbmdnYW5nIEx1bykg?= Newsgroups: gmane.linux.lib.musl.general,gmane.comp.compilers.clang.devel,gmane.comp.standards.posix.austin.general 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 Message-ID: References: <20150509103645.GG29035@port70.net> <20150509200535.GK17573@brightrain.aerifal.cx> <20150511014701.GN30924@vapier> <5550842c.kMHzeizlOZv+0r6r%Joerg.Schilling@fokus.fraunhofer.de> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1431400929 3919 80.91.229.3 (12 May 2015 03:22:09 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 12 May 2015 03:22:09 +0000 (UTC) Cc: vapier@gentoo.org, musl@lists.openwall.com, John Sully , James McNellis , hsutter@microsoft.com, dplakosh@cert.org, Rich Felker , Clang Dev , Karsten Blees , austin-group-l@opengroup.org To: Joerg Schilling Original-X-From: musl-return-7639-gllmg-musl=m.gmane.org@lists.openwall.com Tue May 12 05:22:07 2015 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1Ys0lj-0006uG-FF for gllmg-musl@m.gmane.org; Tue, 12 May 2015 05:22:07 +0200 Original-Received: (qmail 32605 invoked by uid 550); 12 May 2015 03:22:04 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 32587 invoked from network); 12 May 2015 03:22:03 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; bh=kPQMvNAXbVu+rBZ12FML8MSmhOud3RvxNLbmuaO09n0=; b=JggwB/LpdMjWmg/6pOrRNHShiA+ywl43kzRbd7+9CZnxSUzbp6J5tlD/uK6SSq+6TR KphHxMRwcSm8jCO2jqsb8OkkCF79dBlS6jxg3sNHR0Ca4Wu3Mj+JYRJ7pJOBSXj+yUcb heSLVq+g9ctIikCkaouS+RB6nCeO9soJ0Z6Mta1BhaVZEFM14LecF4gMFj2+4dMoKkz5 z+tXmy3xOaiDn9Mnu4NrIKjQMi/tyO5ymjAnAGwxg8D6veOkSeYpn25tf6PIqZZDwJ2z VVnpPNRB607SlV9bwRuwo897I7vvpZOthMggnYlOxM5WE7wHpFbTGZ2ieueQYwcihZTK HyPw== X-Received: by 10.107.10.201 with SMTP id 70mr17172641iok.0.1431400912349; Mon, 11 May 2015 20:21:52 -0700 (PDT) In-Reply-To: <5550842c.kMHzeizlOZv+0r6r%Joerg.Schilling@fokus.fraunhofer.de> Xref: news.gmane.org gmane.linux.lib.musl.general:7627 gmane.comp.compilers.clang.devel:42720 gmane.comp.standards.posix.austin.general:10780 Archived-At: > > I remember that a while ago (probably around 2001), Microsoft tried to re= word > POSIX to permit 16 bit characters by default to make their interface POSI= X > 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. --=20 =E6=AD=A4=E8=87=B4 =E7=A4=BC =E7=BD=97=E5=8B=87=E5=88=9A Yours sincerely, Yonggang Luo