From: Walter Harms <wharms@bfs.de>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>,
"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: "linux-man@vger.kernel.org" <linux-man@vger.kernel.org>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Subject: AW: error.3: What happens if status = 0
Date: Fri, 19 Feb 2021 09:09:13 +0000 [thread overview]
Message-ID: <9c7d3296e4894ec3b118f0f130c51415@bfs.de> (raw)
In-Reply-To: <089a65d2-3dec-b9c1-8c8d-dddcd28f756b@gmail.com>
Hi,
yes, error(0,...) is a bit like warn(), it returns to the programm.
That supports what my man page says:
" If status has a nonzero value, then error() calls exit(3) to terminate
the program using the given value as the exit status."
may be you want an add on like:
"Otherwise error() returns."
re,
wh
________________________________________
Von: Alejandro Colomar (man-pages) <alx.manpages@gmail.com>
Gesendet: Donnerstag, 18. Februar 2021 22:55:13
An: Michael Kerrisk (man-pages)
Cc: linux-man@vger.kernel.org; libc-alpha@sourceware.org
Betreff: error.3: What happens if status = 0
Hi Michael,
I think it's not quite clear what happens when status = 0; for
error[_at_line](3) from the text of the manual page. From the glibc
documentation[1], it seems that error(0, ...) is similar to warn(...),
isn't it?
Thanks,
Alex
[1]:
<https://www.gnu.org/software/libc/manual/html_node/Error-Messages.html#Error-Messages>
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
next prev parent reply other threads:[~2021-02-19 9:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 21:55 Alejandro Colomar (man-pages)
2021-02-19 9:09 ` Walter Harms [this message]
2021-02-19 12:23 ` AW: " Michael Kerrisk (man-pages)
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=9c7d3296e4894ec3b118f0f130c51415@bfs.de \
--to=wharms@bfs.de \
--cc=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).