From: Paolo Bonzini <pbonzini@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Fam Zheng" <famz@redhat.com>,
qemu-devel@nongnu.org, "Stefan Hajnoczi" <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] scsi-generic: Simplify error handling code
Date: Thu, 18 Jan 2018 13:03:43 +0100 [thread overview]
Message-ID: <cf2b427d-a8a0-a124-16dd-598d4f7eea46@redhat.com> (raw)
In-Reply-To: <a81a812f-065c-e8be-0d6d-92525a379a82@amsat.org>
On 18/01/2018 12:21, Philippe Mathieu-Daudé wrote:
>> I'm not a fan of bool return types, in general (because "!" is often
>> success while "< 0" is failure) and especially when there is an Error**;
>> I disagree with commit 9d3b155186. But the function is not in an area I
>> maintain so I'm queuing this, thanks.
> Do you prefer "if (local_err)" and "if (errp && *errp)" ?
The latter is wrong. I do prefer
if (local_err) {
error_propagate(errp, local_err);
return;
}
or maybe (but only if there is a meaning to a zero vs. positive return
value, or if errno is an important part of the returned Error *)
ret = f(..., errp);
if (ret < 0) {
return;
}
> I wondered once if a macro might improve this pattern but thought the
> code would get more obscure.
Eduardo had a series to avoid error_propagate, where NULL was replaced
by a (non-NULL) IGNORED_ERRORS macro. Then you could do:
f(..., errp);
if (error_is_set(errp)) {
return;
}
See here:
https://lists.gnu.org/archive/html/qemu-devel/2017-06/msg03139.html
Paolo
next prev parent reply other threads:[~2018-01-18 12:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 2:52 [Qemu-devel] [PATCH] scsi-generic: Simplify error handling code Fam Zheng
2018-01-18 4:34 ` Philippe Mathieu-Daudé
2018-01-18 8:20 ` Paolo Bonzini
2018-01-18 11:21 ` Philippe Mathieu-Daudé
2018-01-18 12:03 ` Paolo Bonzini [this message]
2018-01-18 15:55 ` Philippe Mathieu-Daudé
2018-01-18 15:59 ` Paolo Bonzini
2018-01-18 20:34 ` Eric Blake
2018-01-18 21:38 ` Eduardo Habkost
2018-01-18 22:19 ` Paolo Bonzini
2018-01-18 22:39 ` Eduardo Habkost
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=cf2b427d-a8a0-a124-16dd-598d4f7eea46@redhat.com \
--to=pbonzini@redhat.com \
--cc=f4bug@amsat.org \
--cc=famz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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 NNTP newsgroup(s).