From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Benjamin Peterson <benjamin@python.org>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
jwilk@jwilk.net, Mike Frysinger <vapier@gentoo.org>
Subject: Re: [PATCH v2] exit.3: Use hex for the status mask.
Date: Sat, 8 Feb 2020 12:00:58 +0100 [thread overview]
Message-ID: <92a0961f-927c-703a-7d7a-16bdd98324d4@gmail.com> (raw)
In-Reply-To: <20180915173848.19733-1-benjamin@python.org>
Hello Ben,
On 9/15/18 7:38 PM, Benjamin Peterson wrote:
> Admittedly, the POSIX specification for exit() also uses octal. However, 0xFF
> immediately indicates the lowest 8 bits to me whereas I had to think a bit about
> the octal mask.
Thanks. Patch applied. (Mike Frysinger provided a similar patch,
so I've noted you both in the commit.)
Cheers,
Michael
> ---
> man2/_exit.2 | 2 +-
> man3/exit.3 | 5 ++---
> 2 files changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/man2/_exit.2 b/man2/_exit.2
> index c55d2a612..6e656c8f4 100644
> --- a/man2/_exit.2
> +++ b/man2/_exit.2
> @@ -65,7 +65,7 @@ The process's parent is sent a
> signal.
> .PP
> The value
> -.I "status & 0377"
> +.I "status & 0xFF"
> is returned to the parent process as the process's exit status, and
> can be collected using one of the
> .BR wait (2)
> diff --git a/man3/exit.3 b/man3/exit.3
> index 4a30fc39f..b47ba17a1 100644
> --- a/man3/exit.3
> +++ b/man3/exit.3
> @@ -38,9 +38,8 @@ exit \- cause normal process termination
> .SH DESCRIPTION
> The
> .BR exit ()
> -function causes normal process termination and the
> -value of \fIstatus & 0377\fP is returned to the parent
> -(see
> +function causes normal process termination and the value of \fIstatus &
> +0xFF\fP is returned to the parent (see
> .BR wait (2)).
> .PP
> All functions registered with
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next parent reply other threads:[~2020-02-08 11:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1537033056.1989189.1509225696.4324DB3A@webmail.messagingengine.com>
[not found] ` <20180915173848.19733-1-benjamin@python.org>
2020-02-08 11:00 ` Michael Kerrisk (man-pages) [this message]
2020-02-10 11:02 ` AW: [PATCH v2] exit.3: Use hex for the status mask Walter Harms
2020-02-24 7:59 ` 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=92a0961f-927c-703a-7d7a-16bdd98324d4@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=benjamin@python.org \
--cc=jwilk@jwilk.net \
--cc=linux-man@vger.kernel.org \
--cc=vapier@gentoo.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).