From: Jeff King <peff@peff.net>
To: David Kastrup <dak@gnu.org>
Cc: John Keeping <john@keeping.me.uk>, git@vger.kernel.org
Subject: Re: [PATCH 1/5] notes-utils: handle boolean notes.rewritemode correctly
Date: Tue, 18 Feb 2014 04:01:56 -0500 [thread overview]
Message-ID: <20140218090156.GC2692@sigill.intra.peff.net> (raw)
In-Reply-To: <87vbwcstgw.fsf@fencepost.gnu.org>
On Tue, Feb 18, 2014 at 09:41:51AM +0100, David Kastrup wrote:
> gcc's flow analysis works with the same data as humans reading the
> code. If there is no information content in the function call, it makes
> more sense to either making it void.
The point of error() returning a constant -1 is to use this idiom:
if (something_failed)
return error("this will get printed, and we get a -1 return");
>From a code perspective it's pointless. You could "just" write:
if (something_failed) {
error(...);
return -1;
}
which is equivalent. But the point is that the former is shorter and a
little more readable, assuming you are familiar with the idiom.
> One can always explicitly write
>
> (config_error_nonbool("panic-when-assailed"), -1)
Yes, but again, the point is readability. Doing that at each callsite is
ugly and annoying.
> Shrug. This one has likely been discussed to death already. Sometimes
> it's more convenient to avoid getting a question asked in the first
> place rather than having a stock answer for it.
You are the first person to ask about it, so there is no stock answer.
However, everything I told you was in the commit messages and the list
archive already. We can also avoid questions being asked by using those
tools.
-Peff
next prev parent reply other threads:[~2014-02-18 9:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-16 16:06 [PATCH 0/5] Miscellaneous fixes from static analysis John Keeping
2014-02-16 16:06 ` [PATCH 1/5] notes-utils: handle boolean notes.rewritemode correctly John Keeping
2014-02-16 16:22 ` David Kastrup
2014-02-18 7:46 ` Jeff King
2014-02-18 8:41 ` David Kastrup
2014-02-18 9:01 ` Jeff King [this message]
2014-02-18 9:36 ` David Kastrup
2014-02-16 16:06 ` [PATCH 2/5] utf8: fix iconv error detection John Keeping
2014-02-16 16:06 ` [PATCH 3/5] utf8: use correct type for values in interval table John Keeping
2014-02-16 16:06 ` [PATCH 4/5] builtin/mv: don't use memory after free John Keeping
2014-02-16 16:06 ` [PATCH 5/5] streaming: simplify attaching a filter John Keeping
2014-02-18 23:56 ` Junio C Hamano
2014-02-19 0:02 ` Junio C Hamano
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=20140218090156.GC2692@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=dak@gnu.org \
--cc=git@vger.kernel.org \
--cc=john@keeping.me.uk \
/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 NNTP newsgroup(s).