From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: hk <hk@r4in.tk>, "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man@vger.kernel.org, mtk.manpages@gmail.com
Subject: Re: man pthread_join(3)
Date: Thu, 10 Feb 2022 23:29:16 +0100 [thread overview]
Message-ID: <485a7d6a-6cf6-32ab-ed89-73075abde040@gmail.com> (raw)
In-Reply-To: <2b9e5c94-fc1a-6ba3-20e5-3bb5c6430476@r4in.tk>
[CC += Branden]
Hello Aitch,
On 2/10/22 01:42, hk wrote:
> Good day
>
> I'm not sure that is a bug or I'm missing something, but still.
>
> There is man-page for pthread_join() function and in its "ERRORS"
> section one
> error code - EINVAL - is mentioned twice with different causes, so I
> have doubts
> about how to handle such of an error.
>
> Here is a link https://man7.org/linux/man-pages/man3/pthread_join.3.html
>
> Could you correct that if it is a mistype? Or, may be add some kind of
> explanation for that kind of situation.
It's just that there's more than one reason you could get that error.
Other Unix systems' manual pages also use this syntax[1][2]. At first
it also seemed weird to me, I'll admit.
I don't know if some other syntax could be easier to read/understand...
Maybe something like:
[
EXXX Reason for EXXX.
EYYY
* One reason for EYYY.
* Another reason for EYYY.
]
[1]:
<https://www.freebsd.org/cgi/man.cgi?query=open&apropos=0&sektion=2&manpath=FreeBSD+13.0-RELEASE+and+Ports&arch=default&format=html#ERRORS>
[2]: <https://man.openbsd.org/open.2#ERRORS>
Thanks,
Alex
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
next prev parent reply other threads:[~2022-02-10 22:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 0:42 man pthread_join(3) hk
2022-02-10 22:29 ` Alejandro Colomar (man-pages) [this message]
2022-02-11 22:13 ` hk
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=485a7d6a-6cf6-32ab-ed89-73075abde040@gmail.com \
--to=alx.manpages@gmail.com \
--cc=g.branden.robinson@gmail.com \
--cc=hk@r4in.tk \
--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