From: Alejandro Colomar <alx.manpages@gmail.com>
To: mtk.manpages@gmail.com
Cc: Alejandro Colomar <alx.manpages@gmail.com>,
linux-man@vger.kernel.org, libc-alpha@sourceware.org
Subject: [PATCH 3/6] err.3: SYNOPSIS: Use 'noreturn' in prototypes
Date: Thu, 18 Feb 2021 22:23:56 +0100 [thread overview]
Message-ID: <20210218212358.246072-4-alx.manpages@gmail.com> (raw)
In-Reply-To: <20210218212358.246072-1-alx.manpages@gmail.com>
Glibc uses __attribute__((__noreturn__)) for [v]err[x]().
These functions never return.
Let's use standard C11 'noreturn' in the manual page.
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
---
man3/err.3 | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/man3/err.3 b/man3/err.3
index 128afde6a..a4d4eb620 100644
--- a/man3/err.3
+++ b/man3/err.3
@@ -43,16 +43,16 @@ err, verr, errx, verrx, warn, vwarn, warnx, vwarnx \- formatted error messages
.nf
.B #include <err.h>
.PP
-.BI "void err(int " eval ", const char *" fmt ", ...);"
-.BI "void errx(int " eval ", const char *" fmt ", ...);"
+.BI "noreturn void err(int " eval ", const char *" fmt ", ...);"
+.BI "noreturn void errx(int " eval ", const char *" fmt ", ...);"
.PP
.BI "void warn(const char *" fmt ", ...);"
.BI "void warnx(const char *" fmt ", ...);"
.PP
.B #include <stdarg.h>
.PP
-.BI "void verr(int " eval ", const char *" fmt ", va_list " args );
-.BI "void verrx(int " eval ", const char *" fmt ", va_list " args );
+.BI "noreturn void verr(int " eval ", const char *" fmt ", va_list " args );
+.BI "noreturn void verrx(int " eval ", const char *" fmt ", va_list " args );
.PP
.BI "void vwarn(const char *" fmt ", va_list " args );
.BI "void vwarnx(const char *" fmt ", va_list " args );
--
2.30.1.721.g45526154a5
next prev parent reply other threads:[~2021-02-18 21:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 21:23 [PATCH 0/6] man[23]: SYNOPSIS: Use 'noreturn' in prototypes Alejandro Colomar
2021-02-18 21:23 ` [PATCH 1/6] abort.3: " Alejandro Colomar
2021-02-19 12:31 ` Michael Kerrisk (man-pages)
2021-02-18 21:23 ` [PATCH 2/6] _exit.2: " Alejandro Colomar
2021-02-18 21:23 ` Alejandro Colomar [this message]
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=20210218212358.246072-4-alx.manpages@gmail.com \
--to=alx.manpages@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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