From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
libc-alpha@sourceware.org
Subject: Re: [PATCH 1/6] abort.3: SYNOPSIS: Use 'noreturn' in prototypes
Date: Fri, 19 Feb 2021 13:31:39 +0100 [thread overview]
Message-ID: <0f80aeba-a619-4b9f-3d99-70a6777080b3@gmail.com> (raw)
In-Reply-To: <20210218212358.246072-2-alx.manpages@gmail.com>
Hi Alex,
On 2/18/21 10:23 PM, Alejandro Colomar wrote:
> POSIX specifies that abort() shall not return.
> Glibc uses __attribute__((__noreturn__)).
> Let's use standard C11 'noreturn' in the manual page.
C11!? I'm only just getting over C99... But okay, it seems
reasonable :-). I applied all of the patches.
Cheers,
Michael
>
> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
> ---
> man3/abort.3 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/man3/abort.3 b/man3/abort.3
> index 71d555841..b33d23ad1 100644
> --- a/man3/abort.3
> +++ b/man3/abort.3
> @@ -38,7 +38,7 @@ abort \- cause abnormal process termination
> .nf
> .B #include <stdlib.h>
> .PP
> -.B void abort(void);
> +.B noreturn void abort(void);
> .fi
> .SH DESCRIPTION
> The
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2021-02-19 12:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 21:23 [PATCH 0/6] man[23]: " Alejandro Colomar
2021-02-18 21:23 ` [PATCH 1/6] abort.3: " Alejandro Colomar
2021-02-19 12:31 ` Michael Kerrisk (man-pages) [this message]
2021-02-18 21:23 ` [PATCH 2/6] _exit.2: " Alejandro Colomar
2021-02-18 21:23 ` [PATCH 3/6] err.3: " Alejandro Colomar
2021-02-18 21:23 ` [PATCH 4/6] exit.3: " Alejandro Colomar
2021-02-18 21:23 ` [PATCH 5/6] pthread_exit.3: " Alejandro Colomar
2021-02-18 21:23 ` [PATCH 6/6] setjmp.3: " Alejandro Colomar
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=0f80aeba-a619-4b9f-3d99-70a6777080b3@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=alx.manpages@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).