Re: non-standard const-preserving string APIs

Hi Adhemerval,

On 2026-05-17T09:22:41-0300, Adhemerval Zanella Netto wrote:
> 
> 
> On 16/05/26 15:15, Alejandro Colomar wrote:
> > Hi!
> > 
> > I'm working on documenting the recent API change of strchr(3) et al.
> > to adapt to C23.  While doing that, I've realized that the related APIs
> > that are not standardized by ISO C, such as memrchr(3), have not been
> > changed consistently with their relatives.  Has this been discussed?
> > 
> > I think the inconsistency might be dangerous.  Should we change the
> > other string functions accordingly?
> I think it is reasonable to support const-preserving to the GNU interfaces as
> well. Are you preparing a patch?

Yup, I will.  Thanks!


Have a lovely day!
Alex

P.S.:  Adhemerval, would you mind having a look at my other recent patch
set?  It was 'Add [v]aprintf(3)'.  The message-ID was:

	Message-ID: <[email protected]>

-- 
<https://www.alejandro-colomar.es>

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEES7Jt9u9GbmlWADAi64mZXMKQwqkFAmoJyc4ACgkQ64mZXMKQ
wqm3cg//Z7hmDDTnEFvhjOp7L7cwEbMvCtRwoo9PQvSZnf/ea91dPVgDhgL8ppaG
AV5DTvUihstzbGcRrHpAYPg3o0fR2NPpK3qHlZeeEchfAzpEhXc+gQmcGcDvwuQi
bEclo5xTrav5EIHKmciXWoTdSJQJZdWxVZn0rXdbFgy8CFu7ZMPElRnRXiLslhrr
K5yKCThR0FIJPQF/SF6HkUMFAx4IvNtr8Sza4rtSe0eV7K1OAcPjuKlylmhf2t+X
BsLji0X2pgCdnAERc8eF4mcKlGl2FDLKfVlpIN1dMeDA3L4GWv0svrnrXOZvuKlL
e9D4GuI4Gk9ciJg7NmbZ+Vj9raCa5lTq/3IUtaVVlSjxZ3qi8d7kEpHmu4b3zWJP
mPzoSvtTB0jSwpkZAk9PyF3/VVELbp8ydkW8OZI3YZPr+1Te/0Dz2u+UtSrHojq9
07SkgHH1Wo+0MVjiidTC9r79lPAfVcHedDi3HOhxz39g27VJKoxg+AMc/fIoqhxv
PPMoJx8+rJMKatFRzBOYJgiGnrgnJdjjQcYZYiVIJyjNwnuTCJCeMYIZm0Z87WG8
tv9pT5MySqzyqcYQHSkh4YWswhH7k+bHR2Y18/zvCIObfz0bHVRZjR/q/o/y77Rz
gc1veGLHqWh6Od/kqPCgetRBZebgijUHeK/RzR+swpzOEaGIAl4=
=8E24
-----END PGP SIGNATURE-----