From: Thomas Voss <mail@thomasvoss.com>
To: linux-man@vger.kernel.org
Cc: Alejandro Colomar <alx.manpages@gmail.com>,
mtk.manpages@gmail.com, Thomas Voss <mail@thomasvoss.com>
Subject: [PATCH] EXIT_SUCCESS.3const EXIT_FAILURE.3const: Add pages
Date: Wed, 16 Nov 2022 22:50:36 +0100 [thread overview]
Message-ID: <20221116215036.30423-1-mail@thomasvoss.com> (raw)
I see we have manuals for constants, types, and more now! That sure brings a
smile to my face :). I guess I might help out a bit will filling out some of
the missing manuals.
Signed-off-by: Thomas Voss <mail@thomasvoss.com>
---
man3const/EXIT_FAILURE.3const | 1 +
man3const/EXIT_SUCCESS.3const | 58 +++++++++++++++++++++++++++++++++++
2 files changed, 59 insertions(+)
create mode 100644 man3const/EXIT_FAILURE.3const
create mode 100644 man3const/EXIT_SUCCESS.3const
diff --git a/man3const/EXIT_FAILURE.3const b/man3const/EXIT_FAILURE.3const
new file mode 100644
index 000000000..ba0d62df9
--- /dev/null
+++ b/man3const/EXIT_FAILURE.3const
@@ -0,0 +1 @@
+.so man3const/EXIT_SUCCESS.3const
diff --git a/man3const/EXIT_SUCCESS.3const b/man3const/EXIT_SUCCESS.3const
new file mode 100644
index 000000000..dd6f908e5
--- /dev/null
+++ b/man3const/EXIT_SUCCESS.3const
@@ -0,0 +1,58 @@
+.\" Copyright (c) 2022 by Thomas Voss <mail@thomasvoss.com>
+.\"
+.\" SPDX-License-Identifier: Linux-man-pages-copyleft
+.\"
+.\"
+.TH EXIT_SUCCESS 3const (date) "Linux man-pages (unreleased)"
+.SH NAME
+EXIT_SUCCESS, EXIT_FAILURE \- termination status constants
+.SH LIBRARY
+Standard C library
+.RI ( libc )
+.SH SYNOPSIS
+.nf
+.B #include <stdlib.h>
+.PP
+.B "#define EXIT_SUCCESS /* ... */"
+.B "#define EXIT_FAILURE /* ... */"
+.fi
+.SH DESCRIPTION
+.BR EXIT_SUCCESS " and " EXIT_FAILURE
+represent a successful and unsuccessful exit status respectively.
+Both macros are constant expressions of type
+.I int
+which can be used as arguments to the
+.BR exit ()
+function.
+.SH CONFORMING TO
+C99 and later;
+POSIX.1-2001 and later.
+.SH EXAMPLES
+.\" SRC BEGIN (EXIT_SUCCESS.c)
+.EX
+#include <stdio.h>
+#include <stdlib.h>
+
+int
+main(int argc, char *argv[])
+{
+ FILE *fp;
+
+ if (argc != 2) {
+ fprintf(stderr, "Usage: %s <file>\en", argv[0]);
+ exit(EXIT_FAILURE);
+ }
+
+ if ((fp = fopen(argv[1], "r")) == NULL) {
+ perror(argv[1]);
+ exit(EXIT_FAILURE);
+ }
+
+ /* Other code omitted */
+
+ exit(EXIT_SUCCESS);
+}
+.EE
+.\" SRC END
+.SH SEE ALSO
+.BR exit (3)
--
2.38.1
next reply other threads:[~2022-11-16 21:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 21:50 Thomas Voss [this message]
2022-11-16 22:06 ` [PATCH] EXIT_SUCCESS.3const EXIT_FAILURE.3const: Add pages Alejandro Colomar
2022-11-16 22:11 ` Alejandro Colomar
2022-11-17 0:14 ` [PATCH v2] " Thomas Voss
2022-11-17 0:19 ` Alejandro Colomar
2022-11-17 0:25 ` [PATCH v3] " Thomas Voss
2022-11-17 0:26 ` [PATCH v2] " Alejandro Colomar
2022-11-17 0:36 ` [PATCH] " Thomas Voss
2022-11-17 0:45 ` Alejandro Colomar
2022-11-17 0:53 ` [PATCH v5] " Thomas Voss
2022-11-17 9:30 ` 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=20221116215036.30423-1-mail@thomasvoss.com \
--to=mail@thomasvoss.com \
--cc=alx.manpages@gmail.com \
--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