linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonny Grant <jg@jguk.org>
To: Michael Kerrisk <mtk.manpages@gmail.com>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: strcpy compared to POSIX strcpy
Date: Mon, 29 Jun 2020 14:41:40 +0100	[thread overview]
Message-ID: <0608691a-6400-0a44-1031-a693f57dee52@jguk.org> (raw)

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


Regards, Jonny

             reply	other threads:[~2020-06-29 19:39 UTC|newest]

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

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=0608691a-6400-0a44-1031-a693f57dee52@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
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;
as well as URLs for NNTP newsgroup(s).