From: Alejandro Colomar <alx.manpages@gmail.com>
To: Thomas Voss <mail@thomasvoss.com>
Cc: linux-man@vger.kernel.org, mtk.manpages@gmail.com
Subject: Re: [PATCH v2] EXIT_SUCCESS.3const EXIT_FAILURE.3const: Add pages
Date: Thu, 17 Nov 2022 01:26:51 +0100 [thread overview]
Message-ID: <6da4b1d7-238c-c670-400e-a0ef2831d3ce@gmail.com> (raw)
In-Reply-To: <1d22a70a-6622-f318-6a04-d30fc0858073@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2451 bytes --]
Hi Thomas,
You missed a few comments in v3. Please check below.
But mostly looks good.
Cheers,
Alex
On 11/17/22 01:19, Alejandro Colomar wrote:
>> 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..f125afb32
>> --- /dev/null
>> +++ b/man3const/EXIT_SUCCESS.3const
>> @@ -0,0 +1,59 @@
>> +.\" 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
>> +.BR "#define EXIT_SUCCESS " 0
>
> I prefer 2 spaces between the macro name and the expansion, so please one more
> space before the quote.
this
>
>> +.BR "#define EXIT_FAILURE " /* nonzero */
>
> "/* nonzero */" needs to be quoted too.
this
>
>> +.fi
>> +.SH DESCRIPTION
>> +.B EXIT_SUCCESS
>> +and
>> +.B EXIT_FAILURE
>> +represent a successful and unsuccessful exit status respectively and can be used
>> +as arguments to the
>> +.BR exit ()
>
> .BR exit (3)
this
>
>> +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 */
>> +
>> + fclose(fp);
>> + exit(EXIT_SUCCESS);
>> +}
>> +.EE
>> +.\" SRC END
>> +.SH SEE ALSO
>> +.BR exit (3)
>
> Also interesting:
>
> .BR sysexits.h (3head)
>
> Cheers,
>
> Alex
>
>
--
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-11-17 0:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 21:50 [PATCH] EXIT_SUCCESS.3const EXIT_FAILURE.3const: Add pages Thomas Voss
2022-11-16 22:06 ` 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 ` Alejandro Colomar [this message]
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=6da4b1d7-238c-c670-400e-a0ef2831d3ce@gmail.com \
--to=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mail@thomasvoss.com \
--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