From: "罗勇刚(Yonggang Luo)" <luoyonggang@gmail.com>
To: Musl <musl@lists.openwall.com>
Cc: Rich Felker <dalias@libc.org>
Subject: Re: [musl] Would it to be possible to get strtoll_l?
Date: Wed, 7 Oct 2020 22:58:50 +0800 [thread overview]
Message-ID: <CAE2XoE_0uVA9jfdxcQF7nH36zu7xXzb3UygmkCk66Rbpe0v0Bg@mail.gmail.com> (raw)
In-Reply-To: <99dead45-e8ff-df89-70f9-97dcb0c4d3ec@wobble.ninja>
[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]
I may suggest maintain an downstream library that contains musl along with
glibc compat, and there is such a
library
On Wed, Oct 7, 2020 at 9:52 PM Ellie <kittens@wobble.ninja> wrote:
>
> 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
--
此致
礼
罗勇刚
Yours
sincerely,
Yonggang Luo
[-- Attachment #2: Type: text/html, Size: 1488 bytes --]
next prev parent reply other threads:[~2020-10-07 14:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 0:34 ell1e
2020-10-01 2:35 ` Rich Felker
2020-10-01 4:36 ` ell1e
2020-10-01 5:24 ` Ellie
2020-10-01 8:08 ` Ellie
2020-10-01 15:47 ` Rich Felker
2020-10-07 13:44 ` ell1e
2020-10-07 13:52 ` Ellie
2020-10-07 14:58 ` 罗勇刚(Yonggang Luo) [this message]
2020-10-07 15:41 ` Ariadne Conill
2020-10-07 19:37 ` Rich Felker
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=CAE2XoE_0uVA9jfdxcQF7nH36zu7xXzb3UygmkCk66Rbpe0v0Bg@mail.gmail.com \
--to=luoyonggang@gmail.com \
--cc=dalias@libc.org \
--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).