From: Alejandro Colomar <alx@kernel.org>
To: libc-alpha@sourceware.org
Cc: linux-man@vger.kernel.org
Subject: non-standard const-preserving string APIs
Date: Sat, 16 May 2026 20:15:47 +0200 [thread overview]
Message-ID: <agizh06CdDnhDvAB@devuan> (raw)
[-- Attachment #1: Type: text/plain, Size: 472 bytes --]
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?
Have a lovely day!
Alex
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2026-05-16 18:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-16 18:15 Alejandro Colomar [this message]
2026-05-17 12:22 ` non-standard const-preserving string APIs Adhemerval Zanella Netto
2026-05-17 13:59 ` Alejandro Colomar
2026-05-18 17:19 ` Adhemerval Zanella Netto
[not found] ` <CAJYzjmezHCPUUpE+w35+TB_70V3=BGq7uD3geEdywP5-OXSU-g@mail.gmail.com>
2026-05-18 18:27 ` Adhemerval Zanella Netto
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=agizh06CdDnhDvAB@devuan \
--to=alx@kernel.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox