From: Jakub Wilk <jwilk@jwilk.net>
To: Stefan Kanthak <stefan.kanthak@nexgo.de>
Cc: <mtk.manpages@gmail.com>, <alx.manpages@gmail.com>,
<linux-man@vger.kernel.org>
Subject: Re: wcschr(3): add special case for NUL, as in strchr(3)
Date: Mon, 12 Jul 2021 18:09:06 +0200 [thread overview]
Message-ID: <20210712160906.yfb4etzsylmzulox@jwilk.net> (raw)
In-Reply-To: <64D55817DE2A4D0E99757425D9883066@H270>
* Stefan Kanthak <stefan.kanthak@nexgo.de>, 2021-07-12, 11:37:
>JFTR: to avoid any possible confusion of "null byte" alias NUL with the
>"null pointer" alias NULL (C macro) or nullptr (C++), "null byte"
>should be replaced with "NUL byte"!
"NUL byte" looks like a typo for "NULL byte", so if anything, it makes
the potential for confusion greater.
Anyway, "null byte" is the preferred term in the man-pages style guide;
see the "NULL, NUL, null pointer, and null character" subsection in
man-pages(7).
--
Jakub Wilk
next prev parent reply other threads:[~2021-07-12 16:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-12 9:37 wcschr(3): add special case for NUL, as in strchr(3) Stefan Kanthak
2021-07-12 16:09 ` Jakub Wilk [this message]
2021-07-12 18:41 ` Stefan Kanthak
2021-08-10 6:40 ` Michael Kerrisk (man-pages)
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=20210712160906.yfb4etzsylmzulox@jwilk.net \
--to=jwilk@jwilk.net \
--cc=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=stefan.kanthak@nexgo.de \
/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.