From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Alan Aversa <alan.aversa-j9pdmedNgrk@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: strlen man-page misinformation
Date: Thu, 18 Feb 2016 14:12:30 +0100 [thread overview]
Message-ID: <56C5C33E.7030407@gmail.com> (raw)
In-Reply-To: <56B237F9.8010206-j9pdmedNgrk@public.gmane.org>
Hello Alan,
On 02/03/2016 06:25 PM, Alan Aversa wrote:
> Hello,
>
> The 2015-08-08 strlen man-page is incorrect. Here's a diff:
>
> --- a/man3/strlen.3
> +++ b/man3/strlen.3
> @@ -45,7 +45,7 @@ excluding the terminating null byte (\(aq\\0\(aq).
> .SH RETURN VALUE
> The
> .BR strlen ()
> -function returns the number of bytes in the string
> +function returns the number of *characters* in the string that
> precede the terminating null character
I went for a simpler change: s/bytes/characters/
> .IR s .
> .SH ATTRIBUTES
> For an explanation of the terms used in this section, see
> @@ -60,7 +60,7 @@ T{
> T} Thread safety MT-Safe
> .TE
> .SH CONFORMING TO
> -POSIX.1-2001, POSIX.1-2008, C89, C99, SVr4, 4.3BSD.
> +POSIX.1-2001, POSIX.1-2008, C89, C99, C11, SVr4, 4.3BSD.
Fixed.
> .SH SEE ALSO
> .BR string (3),
> .BR strnlen (3),
>
> Page 392 (PDF p. 390, §7.24.6.3) of the C11 standard
> <http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1570.pdf> says:
>
> The *strlen* function returns the number of characters that precede
> the terminating null character.
Thanks for the report. Interesting, POSIX.1 still uses the term "bytes"
the spec.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
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
next parent reply other threads:[~2016-02-18 13:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <56B237F9.8010206@cox.net>
[not found] ` <56B237F9.8010206-j9pdmedNgrk@public.gmane.org>
2016-02-18 13:12 ` Michael Kerrisk (man-pages) [this message]
[not found] ` <56C5C33E.7030407-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-02-18 15:42 ` strlen man-page misinformation walter harms
[not found] ` <56C5E67A.2010401-fPG8STNUNVg@public.gmane.org>
2016-02-18 16:25 ` Keith Thompson
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=56C5C33E.7030407@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=alan.aversa-j9pdmedNgrk@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 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.