Linux Manual Pages development
 help / color / mirror / Atom feed
From: Eric Blake <eblake-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: Stefan Puiu <stefan.puiu-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Bernhard Walle <bernhard-X9USDgGjgfuzQB+pC5nmwQ@public.gmane.org>
Subject: Re: [PATCH] strerror: improve strerror_r description
Date: Sat, 21 Apr 2012 20:18:58 -0600	[thread overview]
Message-ID: <4F936A92.4050004@redhat.com> (raw)
In-Reply-To: <CAKgNAkhJDrjrTJJKxubkJ2CMmoB0HBPHWmG2PWJpg7DKMcKWnw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1017 bytes --]

On 04/21/2012 06:19 PM, Michael Kerrisk (man-pages) wrote:
> Eric,
> 

> In addition to the above, I added the following, and I'd be happy if
> you could ack it.
> 
> =====
> --- a/man3/strerror.3
> +++ b/man3/strerror.3
> @@ -133,6 +133,19 @@ functions return
>  the appropriate error description string,
>  or an "Unknown error nnn" message if the error number is unknown.
> 
> +POSIX.1-2001 and POSIX.1-2008 require that a successful call to
> +.BR strerror (3)
> +shall leave
> +.I errno
> +unchanged, and note that,
> +since no function return value is reserved to indicate an error,
> +an application that wishes to check for errors should initialize
> +.I errno
> +to zero before the call,
> +and then check
> +.I errno
> +after the call.
> +
>  The XSI-compliant
>  .BR strerror_r ()
>  function returns 0 on success.
> =====

Correct.

-- 
Eric Blake   eblake-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 620 bytes --]

  parent reply	other threads:[~2012-04-22  2:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-17 22:26 [PATCH] strerror: improve strerror_r description Eric Blake
     [not found] ` <1300400795-9123-1-git-send-email-eblake-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-03-18  9:35   ` Stefan Puiu
     [not found]     ` <AANLkTim_cCxXXGE_BgSV5ewEQziru=gH0LpeFAWRWdkb-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-03-24 20:51       ` Eric Blake
     [not found]         ` <4D8BAEBD.4080202-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-03-24 21:35           ` Stefan Puiu
2012-04-22  0:19           ` Michael Kerrisk (man-pages)
     [not found]             ` <CAKgNAkhJDrjrTJJKxubkJ2CMmoB0HBPHWmG2PWJpg7DKMcKWnw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-04-22  2:18               ` Eric Blake [this message]
     [not found]                 ` <4F936A92.4050004-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-04-22  2:47                   ` Michael Kerrisk (man-pages)

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=4F936A92.4050004@redhat.com \
    --to=eblake-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=bernhard-X9USDgGjgfuzQB+pC5nmwQ@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=stefan.puiu-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