public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Thomas Voss <mail@thomasvoss.com>, linux-man@vger.kernel.org
Cc: mtk.manpages@gmail.com
Subject: Re: [PATCH] EXIT_SUCCESS.3const EXIT_FAILURE.3const: Add pages
Date: Wed, 16 Nov 2022 23:11:11 +0100	[thread overview]
Message-ID: <00ce9b77-4a83-4039-5dba-eb517c3d3c94@gmail.com> (raw)
In-Reply-To: <af30ba85-a9c5-741a-9937-e3b1327fe827@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2533 bytes --]



On 11/16/22 23:06, Alejandro Colomar wrote:
> Hi Thomas,
> 
> On 11/16/22 22:50, Thomas Voss wrote:
>> I see we have manuals for constants, types, and more now!  That sure brings a
>> smile to my face :).
> 
> It's good to see that there's audience that likes these.  :)
> 
> 
>>  I guess I might help out a bit will filling out some of
>> the missing manuals.
> 
> Sure.
> 
>>
>> 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  /* ... */"
> 
> Although ISO C leaves the value unspecified, POSIX guarantees it is 0, so I'd 
> document it as such.
> 
> The exact definition in glibc is (in my system):
> 
>      $ grepc EXIT_SUCCESS /usr/include/stdlib.h
>      /usr/include/stdlib.h:93:
>      #define    EXIT_SUCCESS    0    /* Successful exit status.  */
> 
> So I'd document it as:
> 
> .B "#define EXIT_SUCCESS  0"
> 
>> +.B "#define EXIT_FAILURE  /* ... */"
> 
> The /* ... */ should not be in bold (which makes me realize I did it wrong in 
> EOF.3const, sorry).  Also, POSIX specifies that it should be a non-zero value, 
> so I'd document it as:
> 
> .BR "#define EXIT_FAILURE" "  /* non-zero */"

Quick self-correction:

In man-pages(7), our guide style says we should use nonzero rather than non-zero.


-- 
<http://www.alejandro-colomar.es/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-11-16 22:11 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 [this message]
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=00ce9b77-4a83-4039-5dba-eb517c3d3c94@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