From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Ed Avis <eda-0aTcAJqSNDHby3iVrkZq2A@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
"'linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org'"
<linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: strtod(3) manual page not clear on error handling when endptr is null
Date: Mon, 9 May 2016 22:54:51 +0200 [thread overview]
Message-ID: <e9ad0c55-5dc8-bca4-1cb9-e803887700d2@gmail.com> (raw)
In-Reply-To: <7E039918541B4C4183BFDB8F015C7430DEB54FB3-wKnzbhvBYoCBAzx/YO/BcIT4S9po1h25@public.gmane.org>
Hello Ed,
On 04/28/2016 06:31 PM, Ed Avis wrote:
> strtod(3) says:
>
> If no conversion is performed, zero is returned and the value of nptr
> is stored in the location referenced by endptr.
>
> This surely can't be the case if endptr is null. I believe that the
> behaviour is more like
>
>
> If no conversion is performed, zero is returned, and (unless endptr
> is null) the value of nptr is stored in the location referenced by
> endptr.
Agreed. Page corrected.
Thanks,
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
prev parent reply other threads:[~2016-05-09 20:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 16:31 strtod(3) manual page not clear on error handling when endptr is null Ed Avis
[not found] ` <7E039918541B4C4183BFDB8F015C7430DEB54FB3-wKnzbhvBYoCBAzx/YO/BcIT4S9po1h25@public.gmane.org>
2016-05-09 20:54 ` Michael Kerrisk (man-pages) [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=e9ad0c55-5dc8-bca4-1cb9-e803887700d2@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=eda-0aTcAJqSNDHby3iVrkZq2A@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).