Linux-man Archive on lore.kernel.org
 help / color / Atom feed
From: Jonny Grant <jg@jguk.org>
To: mtk.manpages@gmail.com
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: strcpy compared to POSIX strcpy
Date: Tue, 30 Jun 2020 11:59:50 +0100
Message-ID: <8b1272d9-cb76-e5a2-3731-e98c18344444@jguk.org> (raw)
In-Reply-To: <CAKgNAkgH4L-_A0LqqYyk621EmRqDOqAbG80gR-bu4Fk6jcEskA@mail.gmail.com>



On 29/06/2020 21:30, Michael Kerrisk (man-pages) wrote:
> Hi Jonny
> 
> On Mon, 29 Jun 2020 at 15:41, Jonny Grant <jg@jguk.org> wrote:
>>
>> Hi Michael,
>>
>> Returning to an old topic, noticed strcpy man page is different from the POSIX spec with regards to "terminating NUL character" or "null-terminated" shouldn't man pages should follow POSIX style writing "NUL"?
>>
>> https://man7.org/linux/man-pages/man3/strcpy.3.html
>>
>> https://man7.org/linux/man-pages/man3/strcpy.3p.html
>>
>> https://pubs.opengroup.org/onlinepubs/9699919799/functions/strcpy.html
>>
>> Another function even has nul in the name
>> https://man7.org/linux/man-pages/man3/strchrnul.3.html
> 
> It's not so simple. In POSIX/SUS, you will find variously:
> 
> terminating NUL character
> terminating NUL
> terminating null character
> terminating null byte
> 
> There's even one instance of "terminating NULL character" (in
> <net/if.h>; I estimate it's a bug).
> 
> In the C standard (C11), "terminating null character" seems to be used
> exclusively, but as I understand the C standard [char == byte] by
> definition.
> 
> I've tried to consistently use "terminating null byte" across all
> pages in man-pages. See also the discussion in man-pages(7).

Hi Michael,

It is good you have made things consistent. It sounds like you can't make the POSIX man pages the same, as that comes from the POSIX spec right?

BTW,  net/if.h looks okay on my Ubuntu LTS, line 36 does have:
    char *if_name;		/* null terminated name: "eth0", ... */

Cheers, Jonny

      reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29 13:41 Jonny Grant
2020-06-29 20:30 ` Michael Kerrisk (man-pages)
2020-06-30 10:59   ` Jonny Grant [this message]

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=8b1272d9-cb76-e5a2-3731-e98c18344444@jguk.org \
    --to=jg@jguk.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    /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

Linux-man Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-man/0 linux-man/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-man linux-man/ https://lore.kernel.org/linux-man \
		linux-man@vger.kernel.org
	public-inbox-index linux-man

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-man


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git