From: Eric Blake <eblake@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: pbonzini@redhat.com, mst@redhat.com, qemu-devel@nongnu.org,
dgilbert@redhat.com
Subject: Re: [Qemu-devel] [PATCH 7/7] error: On abort, report where the error was created
Date: Wed, 22 Jul 2015 08:13:05 -0600 [thread overview]
Message-ID: <55AFA4F1.3090800@redhat.com> (raw)
In-Reply-To: <87vbdcjo0i.fsf@blackfin.pond.sub.org>
[-- Attachment #1: Type: text/plain, Size: 1545 bytes --]
On 07/22/2015 07:54 AM, Markus Armbruster wrote:
>>
>>> +#define error_setg(errp, fmt, ...) \
>>> + error_setg_internal((errp), __FILE__, __LINE__, (fmt), ## __VA_ARGS__)
>>> +void error_setg_internal(Error **errp, const char *src, int line,
>>> + const char *fmt, ...) GCC_FMT_ATTR(4, 5);
>>>
>>
>>> +#define error_setg_errno(errp, os_error, fmt, ...) \
>>> + error_setg_errno_internal((errp), __FILE__, __LINE__, (os_error), \
>>> + (fmt), ## __VA_ARGS__)
>>
>> Nit - why the difference in \ alignment?
>
> I'm dense today... difference between where and where?
one space after error_setg(), aligned to far right after error_setg_errno().
>
>> Nit - as used here, 'errp', 'fmt', and 'os_error' can be used
>> unambiguously; you don't need '(errp)' given the context of a
>> parenthesized comma-separated list (even if someone DID want to unusual
>> by passing in '(a,b)' with a comma operator for their 'errp' argument,
>> they'd have to supply the () because of the semantics of making the
>> macro call).
>
> I put parenthesis around macro parameters in the expansion pretty much
> unthinkingly, because thought is expensive :)
Of course, it doesn't hurt semantically to leave them in, and if you
value the lower maintenance burden of less thinking, then the extra
typing is not something I will reject :)
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2015-07-22 14:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 19:26 [Qemu-devel] [PATCH 0/7] error: On abort, report where the error was created Markus Armbruster
2015-06-22 19:26 ` [Qemu-devel] [PATCH 1/7] error: De-duplicate code creating Error objects Markus Armbruster
2015-06-22 20:58 ` Eric Blake
2015-06-23 6:57 ` Markus Armbruster
2015-06-22 19:26 ` [Qemu-devel] [PATCH 2/7] error: Make error_setg() a function Markus Armbruster
2015-06-22 21:38 ` Eric Blake
2015-06-23 7:45 ` Markus Armbruster
2015-06-22 19:26 ` [Qemu-devel] [PATCH 3/7] qga: Clean up unnecessarily dirty casts Markus Armbruster
2015-06-22 22:01 ` Eric Blake
2015-06-23 7:28 ` Markus Armbruster
2015-06-22 19:26 ` [Qemu-devel] [PATCH 4/7] qga/vss-win32: Document the DLL requires non-null errp Markus Armbruster
2015-07-21 15:56 ` Eric Blake
2015-06-22 19:26 ` [Qemu-devel] [PATCH 5/7] error: error_set_errno() is unused, drop Markus Armbruster
2015-07-21 16:05 ` Eric Blake
2015-06-22 19:26 ` [Qemu-devel] [PATCH 6/7] error: Revamp interface documentation Markus Armbruster
2015-07-21 16:11 ` Eric Blake
2015-07-22 13:46 ` Markus Armbruster
2015-06-22 19:26 ` [Qemu-devel] [PATCH 7/7] error: On abort, report where the error was created Markus Armbruster
2015-07-06 20:29 ` Laszlo Ersek
2015-07-21 16:19 ` Eric Blake
2015-07-22 13:54 ` Markus Armbruster
2015-07-22 14:13 ` Eric Blake [this message]
2015-07-23 11:22 ` Markus Armbruster
2015-07-06 20:53 ` [Qemu-devel] [PATCH 0/7] " Michael S. Tsirkin
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=55AFA4F1.3090800@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).