[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <99dead45-e8ff-df89-70f9-97dcb0c4d3ec@wobble.ninja>
Date: Wed, 7 Oct 2020 15:52:14 +0200
From: Ellie <kittens@...ble.ninja>
To: Rich Felker <dalias@...c.org>
Cc: musl@...ts.openwall.com
Subject: Re: Would it to be possible to get strtoll_l?
Just to add this, since I think I could have been clearer on this:
On 10/7/20 3:44 PM, ell1e wrote:
> mostly covered just the ones where the function itself was expected to
> be so small/fast that setting the thread-local locale around the call
> would be relatively expensive
I think as an app dev this just naturally expands to everything, always.
I just don't see a point to ever go uselocale+call, since that is just a
slower way of doing the same. So why bother with a suboptimal way?)And
then there will be the natural point where people try their program on
musl, some *_l() is missing, and the questions start: feature detection?
do we really need this anyway in that case? just use uselocale+call...?
do we care about musl enough to even spend time on this? And it'll cause
friction and thinking time loss. But maintaining all the wrappers will
eat up your time and resources instead. So no easy decision in any case,
I'm afraid, as for what to add or whether anything at all
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.
