From: Jon Grant <jg-hus3n9K41k0@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: printf 3
Date: Wed, 05 Oct 2011 01:04:10 +0100 [thread overview]
Message-ID: <4E8B9EFA.8020100@jguk.org> (raw)
In-Reply-To: <CAKgNAkgrL4tXZmrLaauLNxSv7rngKxsnkk8pWA1AoP1urk-_5g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Michael Kerrisk wrote, On 04/10/11 06:46:
> Hi Jon,
>
> On Tue, Oct 4, 2011 at 1:58 AM, Jon Grant<jg-hus3n9K41k0@public.gmane.org> wrote:
>> Hello
>>
>> Looking at this page:
>> http://man7.org/linux/man-pages/online/pages/man3/printf.3.html
>>
>> "If an output error is encountered, a negative value is returned."
>>
>> I am thinking if this could be clarified. If I call printf(NULL), errno is
>> set to EINVAL, and -1 is returned.
>>
>> Perhaps could be expanded to add:
>>
>> "If a parameter error is encountered, errno set to EINVAL, and -1 is
>> returned. If an output error is encountered, errno set EIO and -1 returned.
>
> The apparently vague wording is deliberate. Glibc may generally return
> -1, but POSIX simply says "a negative value", and that's all that is
> guaranteed to an application.
Ah ok. Good point.
Is it worth documenting the Glibc behaviour on the man page in addition
to explaining POSIX spec.
Best regards, Jon
--
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 prev parent reply other threads:[~2011-10-05 0:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 23:58 printf 3 Jon Grant
[not found] ` <4E8A4C32.9000607-hus3n9K41k0@public.gmane.org>
2011-10-04 5:46 ` Michael Kerrisk
[not found] ` <CAKgNAkgrL4tXZmrLaauLNxSv7rngKxsnkk8pWA1AoP1urk-_5g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-10-05 0:04 ` Jon Grant [this message]
[not found] ` <4E8B9EFA.8020100-hus3n9K41k0@public.gmane.org>
2011-10-05 4:39 ` Michael Kerrisk
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=4E8B9EFA.8020100@jguk.org \
--to=jg-hus3n9k41k0@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@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