From: Alejandro Colomar <alx@kernel.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: linux-man@vger.kernel.org, bug-gnulib@gnu.org
Subject: Re: [PATCH v1 1/1] man/man3/strnul.3: New page
Date: Sun, 22 Feb 2026 14:46:02 +0100 [thread overview]
Message-ID: <aZsIJhUxHa1L1cme@devuan> (raw)
In-Reply-To: <aZrmh5XLcUcKJz4b@devuan>
[-- Attachment #1: Type: text/plain, Size: 1579 bytes --]
On 2026-02-22T12:21:34+0100, Alejandro Colomar wrote:
> Hi Paul,
>
> On 2026-02-21T17:48:30-0800, Paul Eggert wrote:
> > On 2026-02-21 07:02, Alejandro Colomar wrote:
> > > +.BI char\~*streq(const\~char\~* s );
> >
> > I see you fixed the misspelling of "strnul". However, there's a more
> > important issue here: that's not the type of Gnulib strnul. Gnulib strnul is
> > a qualifier-generic macro, and (unlike C23 strchr) there is no underlying
> > function named "strnul". This needs to be documented clearly.
>
> Yup, if there are no plans to have a function, I'll document the
> const-generic macro. Thanks!
I've pushed the following patch:
commit e29efc9b6bdbb644a44c2b9e3d6bfbf06ce4ec62 (HEAD -> contrib)
Author: Alejandro Colomar <alx@kernel.org>
Date: 2026-02-22 14:34:36 +0100
man/man3/strnul.3: SYNOPSIS: Use QChar
Reported-by: Paul Eggert <eggert@cs.ucla.edu>
Signed-off-by: Alejandro Colomar <alx@kernel.org>
diff --git a/man/man3/strnul.3 b/man/man3/strnul.3
index 714b4d191cae..f84e13fdc82b 100644
--- a/man/man3/strnul.3
+++ b/man/man3/strnul.3
@@ -12,7 +12,7 @@ .SH SYNOPSIS
.nf
.B #include <string.h>
.P
-.BI char\~*strnul(const\~char\~* s );
+.BI QChar\~*strnul(QChar\~* s );
.fi
.SH DESCRIPTION
.BR strnul ()
I might document QChar is a separate page, eventually. I'm still
thinking about whether to do it or not, and what to document in such
a page. Patches are welcome, if anyone has some ideas.
Cheers,
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-22 13:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-21 15:02 [PATCH v1 0/1] Document strnul(3) Alejandro Colomar
2026-02-21 15:02 ` [PATCH v1 1/1] man/man3/strnul.3: New page Alejandro Colomar
2026-02-21 17:41 ` G. Branden Robinson
2026-02-21 19:56 ` Alejandro Colomar
2026-02-21 20:02 ` Simon Josefsson
2026-02-21 20:45 ` Alejandro Colomar
2026-02-21 20:05 ` G. Branden Robinson
2026-02-21 20:55 ` Alejandro Colomar
2026-02-22 1:48 ` Paul Eggert
2026-02-22 11:21 ` Alejandro Colomar
2026-02-22 13:46 ` Alejandro Colomar [this message]
2026-02-22 14:10 ` Bruno Haible
2026-02-22 14:19 ` Alejandro Colomar
2026-02-22 14:21 ` Alejandro Colomar
2026-02-21 15:04 ` [PATCH v1 0/1] Document strnul(3) Alejandro Colomar
2026-02-21 15:09 ` Alejandro Colomar
2026-02-21 20:53 ` [PATCH v2 " Alejandro Colomar
2026-02-21 20:53 ` [PATCH v2 1/1] man/man3/strnul.3: New page Alejandro Colomar
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=aZsIJhUxHa1L1cme@devuan \
--to=alx@kernel.org \
--cc=bug-gnulib@gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox