[RFC v4 2/4] string: Add streq,memeq,wcseq,wmemeq,strcaseeq[_l],wcscaseeq[_l] APIs

[Alejandro Colomar]

On Mon, Sep 15, 2025 at 09:01:05PM +0200, Alejandro Colomar wrote:
> Hi Paul,
> 
> On Mon, Sep 15, 2025 at 09:41:29AM -0700, Paul Eggert wrote:
> > On 2025-09-15 00:18, Alejandro Colomar wrote:
> > > I gave up on static inline because of that.  TBH, I'd like to avoid
> > > doing tricks where users have a hard time understanding what glibc is
> > > doing.  I have enough trouble reading glibc sources myself already.
> > 
> > OK, if we want to keep things absolutely simple in the headers, then we
> > should not use inline.
> > 
> > It's too bad that glibc never uses C99-or-later inline in its headers, due
> > to portability hassles and inertia, particularly since Gnulib has been doing
> > it for many years. But I suppose this can be put off still further into the
> > future.
> 
> I wonder if gcc would agree to remove GNU inline.  That would open the
> door for using C99 inline eventually in glibc.
> 
> Of course, there's a problem in glibc, as it currently uses GNU inline
> extensively.  I'm not entirely sure how a transition period would look
> like; but we should have a look at that.
> 
> I would volunteer to work on trying to improve this in glibc if there's
> interest.  I certainly want to be able to use the standard inline here
> some day.
> 
> Also, I could volunteer to remove a lot of obsolete code that's there to
> support ancient versions of GCC, as Zack showed recently (IIRC it was
> Zack).

Sorry; it was Wilco.

> 
> 
> Have a lovely night!
> Alex
> 
> -- 
> <https://www.alejandro-colomar.es>
> Use port 80 (that is, <...:80/>).



-- 
<https://www.alejandro-colomar.es>
Use port 80 (that is, <...:80/>).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://sourceware.org/pipermail/libc-alpha/attachments/20250916/08b7815c/attachment.sig>