mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "罗勇刚(Yonggang Luo) " <luoyonggang@gmail.com>
To: musl@lists.openwall.com
Subject: Re: There is no tests for musl,
Date: Fri, 8 May 2015 21:10:14 +0800	[thread overview]
Message-ID: <CAE2XoE8zGe-Pk41V7aLnA9x3o-J2fq5VvwCe8PWK52y4k2rhpg@mail.gmail.com> (raw)
In-Reply-To: <20150508124942.GV17573@brightrain.aerifal.cx>

I've seen all the codes of midipix, it's seems not active developing now.
I was trying to the other way, that getting musl can be compiled with msvc.
For easily debugging on win32 and preserve the wchar_t  on Win32.

I know the advantage of wchar_t to be 32bit, but I think this would be
double-edged.
Cause 16 bit wchar_t doesn't not good for Linux, but also 32bit
wchar_t doesn't good for
Win32.
We should leave the all of Unicode to the work of char32_t. That's my design.


2015-05-08 20:49 GMT+08:00 Rich Felker <dalias@libc.org>:
> On Fri, May 08, 2015 at 04:52:28PM +0800, 罗勇刚(Yonggang Luo)  wrote:
>> That's looks good, except the wchar_t part.
>> I am not so sure that's was a good idea, cause all Windows API wchar_t
>> are UTF16...
>
> It's necessary to support all of Unicode and not just the BMP.
>
> On midipix you still have all the raw Windows API functions that need
> UTF-16 "WCHAR" arrays as input, so you can convert manually to WCHAR
> (which happens to also match the standard C type char16_t) and call
> them. But there's also a wrapper layer that lets you pass UTF-8
> strings to WinAPI wrappers, so you never have to deal with wchar_t or
> WCHAR at all. I don't know all the details but you could ask on
> #midipix.
>
> Rich



-- 
         此致
礼
罗勇刚
Yours
    sincerely,
Yonggang Luo


  reply	other threads:[~2015-05-08 13:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08  7:38 罗勇刚(Yonggang Luo) 
2015-05-08  8:01 ` Szabolcs Nagy
2015-05-08  8:03   ` 罗勇刚(Yonggang Luo) 
2015-05-08  8:36     ` Szabolcs Nagy
2015-05-08  8:52       ` 罗勇刚(Yonggang Luo) 
2015-05-08 12:49         ` Rich Felker
2015-05-08 13:10           ` 罗勇刚(Yonggang Luo)  [this message]
2015-05-08 13:35             ` Rich Felker
2015-05-08 14:02               ` 罗勇刚(Yonggang Luo) 
2015-05-08 14:10                 ` Rich Felker
2015-05-08 14:17                   ` 罗勇刚(Yonggang Luo) 
2015-05-08 15:20                     ` Szabolcs Nagy
2015-05-08 15:23                       ` 罗勇刚(Yonggang Luo) 
2015-05-08 15:36                       ` Rich Felker
2015-05-08 15:41                         ` 罗勇刚(Yonggang Luo) 
2015-05-08 15:58                           ` 罗勇刚(Yonggang Luo) 
2015-05-08 20:01 writeonce

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=CAE2XoE8zGe-Pk41V7aLnA9x3o-J2fq5VvwCe8PWK52y4k2rhpg@mail.gmail.com \
    --to=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).