From: Alejandro Colomar <alx@kernel.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: linux-man@vger.kernel.org
Subject: Re: QChar and QVoid for strchr(3), memchr(3), et al.
Date: Tue, 24 Feb 2026 22:31:35 +0100 [thread overview]
Message-ID: <aZ4YhDCzMOnokXH9@devuan> (raw)
In-Reply-To: <67824728-313a-4f73-be2c-ad41697925b5@cs.ucla.edu>
[-- Attachment #1: Type: text/plain, Size: 708 bytes --]
Hi Paul,
On 2026-02-24T09:14:04-0800, Paul Eggert wrote:
> On 2026-02-24 06:28, Alejandro Colomar wrote:
> > - In the SYNOPSIS, do you prefer QChar/QVoid or overload style?
> >
> > QChar *strchr(QChar *s, int c);
> > vs
> > char *strnul(char *s);
> > const char *strnul(const char *s);
> One documents strchr, the other strnul.
D'oh! Copy/paste error. I forgot to replace the function name.
> And strchr and strnul do differ:
> strchr has an underlying obsolescent function, and strnul does not. This
> suggests strchr should be documented differently from strnul.
How would you document strchr(3)?
Have a lovely night!
Alex
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-02-24 21:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 14:28 QChar and QVoid for strchr(3), memchr(3), et al Alejandro Colomar
2026-02-24 16:56 ` Mark Harris
2026-02-24 17:14 ` Paul Eggert
2026-02-24 21:31 ` Alejandro Colomar [this message]
2026-02-24 23:04 ` Paul Eggert
2026-02-24 23:05 ` Alejandro Colomar
2026-02-24 23:19 ` Paul Eggert
2026-02-24 23:34 ` Alejandro Colomar
2026-02-25 1:03 ` Mark Harris
2026-02-25 1:15 ` Alejandro Colomar
2026-02-24 18:52 ` Rene Kita
2026-02-24 21:41 ` Alejandro Colomar
2026-02-25 15:48 ` Rene Kita
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=aZ4YhDCzMOnokXH9@devuan \
--to=alx@kernel.org \
--cc=eggert@cs.ucla.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.