From: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
To: "罗勇刚(Yonggang Luo)"
<luoyonggang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Rich Felker <dalias-8zAoT0mYgF4@public.gmane.org>,
John Sully <john-FZqURIBfT/qw5LPnMra/2Q@public.gmane.org>,
Karsten Blees <blees-x8bNZE/nUJk@public.gmane.org>,
musl-ZwoEplunGu1jrUoiu81ncdBPR1lH4CV8@public.gmane.org,
dplakosh-etTNj8cnB6w@public.gmane.org,
austin-group-l-7882/jkIBncuagvECLh61g@public.gmane.org,
hsutter-0li6OtcxBFHby3iVrkZq2A@public.gmane.org,
Clang Dev <cfe-dev-Tmj1lob9twqVc3sceRu5cw@public.gmane.org>,
James McNellis
<james-5OgNh6/BCtVKcNVKSCbDRAC/G2K4zDHf@public.gmane.org>
Subject: Re: [musl] 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 21:47:01 -0400 [thread overview]
Message-ID: <20150511014701.GN30924@vapier> (raw)
In-Reply-To: <CAE2XoE8ARm6BkarKYspPK_uDkePw8PewHXPWRXmT+mGM5mwEaw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 620 bytes --]
On 10 May 2015 20:31, 罗勇刚(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,
POSIX has no such encoding requirement on the |path| argument:
http://pubs.opengroup.org/onlinepubs/9699919799/functions/open.html
on Linux, that buffer is a standard NUL-terminated C string which is passed
directly to the kernel which more or less passes it directly to the fs driver.
how some FS drivers interpret that string depends on the FS.
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-05-11 1:47 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 ` Mike Frysinger [this message]
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=20150511014701.GN30924@vapier \
--to=vapier-abrp7r+bbdudnm+yrofe0a@public.gmane.org \
--cc=austin-group-l-7882/jkIBncuagvECLh61g@public.gmane.org \
--cc=blees-x8bNZE/nUJk@public.gmane.org \
--cc=cfe-dev-Tmj1lob9twqVc3sceRu5cw@public.gmane.org \
--cc=dalias-8zAoT0mYgF4@public.gmane.org \
--cc=dplakosh-etTNj8cnB6w@public.gmane.org \
--cc=hsutter-0li6OtcxBFHby3iVrkZq2A@public.gmane.org \
--cc=james-5OgNh6/BCtVKcNVKSCbDRAC/G2K4zDHf@public.gmane.org \
--cc=john-FZqURIBfT/qw5LPnMra/2Q@public.gmane.org \
--cc=luoyonggang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=musl-ZwoEplunGu1jrUoiu81ncdBPR1lH4CV8@public.gmane.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).