From: Rich Felker <dalias@libc.org>
To: "罗勇刚(Yonggang Luo)" <luoyonggang@gmail.com>
Cc: John Sully <john@csquare.ca>, Karsten Blees <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: 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: Sun, 10 May 2015 09:42:30 -0400 [thread overview]
Message-ID: <20150510134230.GN17573@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAE2XoE8ARm6BkarKYspPK_uDkePw8PewHXPWRXmT+mGM5mwEaw@mail.gmail.com>
On Sun, May 10, 2015 at 08:31:54PM +0800, 罗勇刚(Yonggang Luo) wrote:
> For example, the open function exist both in msvcrt and posix,
> int open(const char *path, int oflag, ...);
>
> But in msvcrt, the path is ANSI encoding, and in posix, path is utf8 encoding,
>
> So if we need to developing a cross-platform application, On Win32,
> the open function should not be used.
> But in fact, there is no openw(const wchar*path) API in posix or Win32,
> So we need to re-implement open function on win32 with the same API,
> and convert to
> the wchar_t version of Window 32 API, _wopen,
> That's would be a chaos for those developers want to use open function
> in both posix and win32.
I assumed you were already planning for your POSIX layer an open
function which takes a UTF-8 string and converts it transparently to
whatever encoding (i.e. UTF-16) the underlying Windows operations
need. If you don't have that, then you're a step behind even Cygwin
and significantly behind midipix in terms of the ability to provide a
POSIX+Unicode environment that can run existing POSIX-targeted
applications unmodified. Anyone wanting Unicode filename support would
have to fill their codebase with Windows-specific openw() calls, which
is basically the same situation you have now on Windows.
> And if we turn the wchar_t to be 32 bit on win32,
> first, posix still have no wide version of open function
> second, to implement open function on win32, we need to consider the
> fact wchar_t is 32bit now, and should re-use the exist _wopen in
> a different way and all other exist wide version of Win32 API.
I don't follow what you're saying here.
Rich
next prev parent reply other threads:[~2015-05-10 13:42 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 [this message]
[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=20150510134230.GN17573@brightrain.aerifal.cx \
--to=dalias@libc.org \
--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).