qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: "Markus Armbruster" <armbru@redhat.com>,
	"Andreas Färber" <afaerber@suse.de>
Cc: "peter.maydell@linaro.org" <peter.maydell@linaro.org>,
	"peter.crosthwaite@xilinx.com" <peter.crosthwaite@xilinx.com>,
	"Huangweidong (C)" <weidong.huang@huawei.com>,
	"aliguori@amazon.com" <aliguori@amazon.com>,
	"mst@redhat.com" <mst@redhat.com>,
	"marcel.a@redhat.com" <marcel.a@redhat.com>,
	Luonengjun <luonengjun@huawei.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"lcapitulino@redhat.com" <lcapitulino@redhat.com>,
	"Gonglei (Arei)" <arei.gonglei@huawei.com>,
	"av1474@comtv.ru" <av1474@comtv.ru>,
	"kraxel@redhat.com" <kraxel@redhat.com>,
	"stefanha@redhat.com" <stefanha@redhat.com>,
	"pbonzini@redhat.com" <pbonzini@redhat.com>,
	"dmitry@daynix.com" <dmitry@daynix.com>,
	"imammedo@redhat.com" <imammedo@redhat.com>,
	"Huangpeng (Peter)" <peter.huangpeng@huawei.com>,
	"dgilbert@redhat.com" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 2/8] usb: a trivial code change for more idiomatic writing style
Date: Fri, 01 Aug 2014 09:56:36 -0600	[thread overview]
Message-ID: <53DBB8B4.6040604@redhat.com> (raw)
In-Reply-To: <87fvhglnjl.fsf@blackfin.pond.sub.org>

[-- Attachment #1: Type: text/plain, Size: 1906 bytes --]

On 08/01/2014 12:41 AM, Markus Armbruster wrote:

>>>>> +        if (data == NULL) {
>>>>
>>>> Wouldn't it be even more idiomatic as:
>>>>
>>>> if (!data) {
>>>>
>>>> Probably applies throughout your series.
>>>>
>>> OK, will do. Thanks!
>>
>> Not so quick! You are free to use that in your patches, but please don't
>> change all code that way without the author's consent. Just like "equals
>> null" is a natural English way of reading, compared to "null equals
>> something", "not null" reads like a boolean expression to me, and even
>> worse while all valid C, "not strcmp" leads to mind-boggling inverted
>> logic...

If it's going to be controversial, then the right thing to do is that
both '(!ptr)' and '(ptr == NULL)' are acceptable, and that preference
should be given to consistency to nearby code.

> 
> !strcmp() is somewhat error prone, because it suggests inequality.

That's why libvirt uses a STREQ() macro; it evaluates to !strcmp under
the hood, but it's a LOT easier to reason about 'STREQ(a, b)' than it is
to reason about '!strcmp(a, b)'.

> Can't claim that for !data.  That one suggests "no data", which is
> exactly right.  Like Eric, I prefer it to the cumbersome data == NULL.

I also prefer 'if (ptr)' over 'if (ptr != NULL)'.

> data == 0 is right out.

Correct, especially if data is a pointer (hmm, our coding style should
mention that we STRONGLY prefer NULL over 0 when referring to the null
pointer).

> 
> Since there's no consensus on !data vs. data == NULL, you're free to
> follow your own taste in new code.  When changing existing code, imitate
> nearby code.  When nearby code is inconsistent, it's your own taste
> again.

Yes, so capturing this sentiment in the coding style guide would be
worthwhile.

-- 
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: 539 bytes --]

  parent reply	other threads:[~2014-08-01 15:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-01  2:32 [Qemu-devel] [PATCH v2 for-2.2 0/8] about Yoda conditions arei.gonglei
2014-08-01  2:32 ` [Qemu-devel] [PATCH v2 1/8] CODING_STYLE: Section about conditional statement arei.gonglei
2014-08-01  3:07   ` Eric Blake
2014-08-01  3:31     ` Gonglei (Arei)
2014-08-01  2:32 ` [Qemu-devel] [PATCH v2 2/8] usb: a trivial code change for more idiomatic writing style arei.gonglei
2014-08-01  3:08   ` Eric Blake
2014-08-01  3:32     ` Gonglei (Arei)
2014-08-01  3:42       ` Andreas Färber
2014-08-01  3:54         ` Gonglei (Arei)
2014-08-01  6:41         ` Markus Armbruster
2014-08-01  6:50           ` Gonglei (Arei)
2014-08-01 15:56           ` Eric Blake [this message]
2014-08-01  2:32 ` [Qemu-devel] [PATCH v2 3/8] audio: " arei.gonglei
2014-08-01  2:32 ` [Qemu-devel] [PATCH v2 4/8] isa-bus: " arei.gonglei
2014-08-01  2:32 ` [Qemu-devel] [PATCH v2 5/8] " arei.gonglei
2014-08-01  2:32 ` [Qemu-devel] [PATCH v2 6/8] spice: " arei.gonglei
2014-08-01  2:32 ` [Qemu-devel] [PATCH v2 7/8] vl: " arei.gonglei
2014-08-01  2:32 ` [Qemu-devel] [PATCH v2 8/8] vmxnet3: " arei.gonglei
2014-08-01  2:51 ` [Qemu-devel] [PATCH v2 for-2.2 0/8] about Yoda conditions Eric Blake
2014-08-01  3:23   ` Gonglei (Arei)

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=53DBB8B4.6040604@redhat.com \
    --to=eblake@redhat.com \
    --cc=afaerber@suse.de \
    --cc=aliguori@amazon.com \
    --cc=arei.gonglei@huawei.com \
    --cc=armbru@redhat.com \
    --cc=av1474@comtv.ru \
    --cc=dgilbert@redhat.com \
    --cc=dmitry@daynix.com \
    --cc=imammedo@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=luonengjun@huawei.com \
    --cc=marcel.a@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.crosthwaite@xilinx.com \
    --cc=peter.huangpeng@huawei.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=weidong.huang@huawei.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).