Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 6 Jun 2015 19:10:57 -0400
From: Rich Felker <>
Subject: Re: [PATCH] Byte-based C locale, draft 1

On Sun, Jun 07, 2015 at 12:39:00AM +0200, Harald Becker wrote:
> Hi Rich !
> On 06.06.2015 23:40, Rich Felker wrote:
> >Attached is the first draft of a proposed byte-based C locale. The
> >patch is about 400 lines but most of it is context, because it's
> >basically a lot of tiny changes spread out over lots of files.
> Sorry for my hopping in. I like  musl, but I really dislike all this
> wchar_t and locale management. Ok, I see it is required for POSIX
> compatibility, so I have to accept the existence of this stuff. If
> linking statically, I'm able to avoid most of this and this code
> never gets in, but when linking shared it makes all into the shared
> library (which is my point of criticism).
> So I like to see a build switch to disable all this locale stuff,
> assuming just bare char type and sole only C / UTF-8 locale, with a
> minimum on locale overhead (all locale functions should just fail
> except for there very simple / standard usage cases). Is there any
> chance to see such a build switch in the main stream, or do I really
> need to create an maintain a separate patch for this (the hard way)?

I'm not clear whether your comments are about the proposed byte-based
C locale (the patch you're replying to) or about existing code in
musl. Could you be more specific?


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.