linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Jon Grant <jg-hus3n9K41k0@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: null terminating byte man pages
Date: Sun, 19 May 2013 19:55:07 +0200	[thread overview]
Message-ID: <519911FB.4070909@gmail.com> (raw)
In-Reply-To: <CAGc9Evdt3W-OtH3B5xyWPtuLkVMuob2rK2_QWhqV_+Ev0S67LA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hi Jon,

On 04/25/13 15:07, Jon Grant wrote:
> Hello
> 
> readdir (3) man page says:
> "the terminating null byte"
> 
> Could it be updated to follow "man strlen" page and say:
> 
> "the terminating null byte ('\0')"
> 
> Other pages only say "null byte", e.g. getdomainname
> http://man7.org/linux/man-pages/man2/setdomainname.2.html
> 
> Should they all be changed to clarify?
> 
> others: gethostname, readlink, stat, argz_add, asprintf, catgets,
> confstr, getcwd, getline,
> getlogin, memchr, pthread_setname_np, strerror, strfmon, strftime,
> sysconf, inotify,
> 
> wprintf - should also say ('\0') ?

So (1) there is some inconsistency in the pages with respect to this
point, but I'm not too worried about it and (2) C programmers should
know what a terminating null byte is. Therefore, I'm not really 
inclined to fix this in every case, but I did add the detail to 
these pages:

readdir.2
asprintf.3
catgets.3
getline.3
getlogin.3
pthread_setname_np.3
readdir.3
strerror.3
inotify.7

Cheers,

Michael
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2013-05-19 17:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-25 13:07 null terminating byte man pages Jon Grant
     [not found] ` <CAGc9Evdt3W-OtH3B5xyWPtuLkVMuob2rK2_QWhqV_+Ev0S67LA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-05-19 17:55   ` Michael Kerrisk [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=519911FB.4070909@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=jg-hus3n9K41k0@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).