[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE2XoE8k8Dm3xexNVwNksRcjncUaHGvCA0aqFOL_UXS1K4ma+A@mail.gmail.com>
Date: Fri, 8 May 2015 23:41:59 +0800
From: 罗勇刚(Yonggang Luo) <luoyonggang@...il.com>
To: musl@...ts.openwall.com
Subject: Re: There is no tests for musl,
>> > solution, I think there is no one would use
>> > wchar_t for cross text processing, cause, on some system, wchar_t is
>> > just 8bit width!
>>
>> anybody would use wchar_t who cares about standard conformant
>> implementations.
>>
>> non-standard broken platforms may get an unmaintained #ifdef
>> as usual..
>
> I think we (and midipix) have a different perspective from Yonggang
> Luo on portable development. Our view is that you write to a POSIX (or
> nearly-POSIX) target with fully working Unicode support and fix the
> small number of targets (i.e. just Windows) that don't already provide
Small is relative, if counting the distribution count, well, Unix wins.
> these things. Yonggang Luo's perspective seems to be more of a
> traditional Windows approach with #ifdef and lots of OS-specific code,
> but just making the Windows branch of the #ifdefs less hideous than it
> was before. :)
If getting wchar_t to be 32 bit on win32, then truly will be a lot of
#ifdef, I am not so sure
if you have experience on Win32 API development, I hope we discussing
the problems in a
more objective way.
>
> Rich
--
此致
礼
罗勇刚
Yours
sincerely,
Yonggang Luo
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
