non-standard const-preserving string APIs

[Alejandro Colomar]

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: <cover.1776882798.git.alx@kernel.org>

-- 
<https://www.alejandro-colomar.es>
-------------- 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/20260517/e2635fa2/attachment.sig>