apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ivan Zhakov <i...@visualsvn.com>
Subject Re: [vote] Win32 Decision Point
Date Thu, 25 Apr 2019 07:59:01 GMT
On Wed, 24 Apr 2019 at 22:31, William A Rowe Jr <wrowe@rowe-clan.net> wrote:
>
> Some 17 years later we are at a crossroads, because the win32 code
> is somewhat illegible and harder to maintain due to the ANSI-vs-UTF8,
> Win9x-vs-NT code paths.
>
> NT won. The only remaining question is how many apr consumers are
> leveraging ANSI-specific builds for local code page semantics, vs how
> many are willing to treat all system resources as utf-8 names, and for
> ANSI, willing to live on the 1.x branch in perpetuity? These are builds
> that explicitly toggle ANSI in spite of whatever OS the binary runs on.
>
> So the vote is pretty simple, I propose to strip all ANSI 8-bit logic from
> the apr (2.0) trunk/ and leave only the utf8->wide char logic remaining.
> Committers and community both, please choose one below,
>
> [ ] Please retain the ANSI logic in APR 2.0 on Win32
>
> [ ] Please drop 8-bit and focus only on utf-8 resource names on Win32.
>
> Will leave this question open a full 10 days to get the widest sampling
> of opinions.
>
>
[X] Please drop 8-bit and focus only on utf-8 resource names on Win32.

The only problem I see that it would harder to backport fixes to
stable branches. What about release apr 1.8 without ANSI logic?

-- 
Ivan Zhakov

Mime
View raw message