mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: ell1e <kittens@wobble.ninja>
Cc: musl@lists.openwall.com
Subject: Re: [musl] Would it to be possible to get strtoll_l?
Date: Wed, 7 Oct 2020 15:37:25 -0400	[thread overview]
Message-ID: <20201007193725.GX17637@brightrain.aerifal.cx> (raw)
In-Reply-To: <c127ba0d-ced6-a248-7484-6a5e378b102b@wobble.ninja>

On Wed, Oct 07, 2020 at 03:44:11PM +0200, ell1e wrote:
> Hi Rich,
> 
> I admit I have a very biased view. Let me first preface this with saying
> that for my program, this issue is now solved. However, I think there
> might be some use if I explain further where I am coming from, and what
> I think about adding more *_l() functions:
> 
> This is how I came to here, asking about strtoll_l():
> 
> [...]
> 
> I don't think I can give you further insight than this. Nevertheless, I
> hope that wall of text had something of use for you.

Really all I'm looking for is some investigation into what the set of
potentially-wanted extended *_l functions that other implementations
have looks like -- whether you think you/users would want all of those
or some clearly-scoped subset of them that makes sense -- rather than
just asking for one random function at a time with no clear idea of
where that will go.

Rich

      parent reply	other threads:[~2020-10-07 19:37 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)
2020-10-07 15:41             ` Ariadne Conill
2020-10-07 19:37             ` Rich Felker [this message]

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=20201007193725.GX17637@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=kittens@wobble.ninja \
    --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).