From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.3 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 31924 invoked from network); 7 Oct 2020 19:37:45 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 7 Oct 2020 19:37:45 -0000 Received: (qmail 31763 invoked by uid 550); 7 Oct 2020 19:37:39 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 30719 invoked from network); 7 Oct 2020 19:37:38 -0000 Date: Wed, 7 Oct 2020 15:37:25 -0400 From: Rich Felker To: ell1e Cc: musl@lists.openwall.com Message-ID: <20201007193725.GX17637@brightrain.aerifal.cx> References: <47f2d2dc-0f18-5d86-8206-1196502b60e0@wobble.ninja> <20201001023528.GM17637@brightrain.aerifal.cx> <03e1484f-0f66-b86a-d717-45ee1eb32790@wobble.ninja> <805b0ccb-5f71-afdf-8898-6d5a9435d10b@wobble.ninja> <20201001154702.GQ17637@brightrain.aerifal.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [musl] Would it to be possible to get strtoll_l? 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