qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: armbru@redhat.com, qemu-trivial@nongnu.org, pbonzini@redhat.com
Subject: [Qemu-devel] [PATCH v2 7/7] checkpatch: Enforce proper do/while (0) style
Date: Fri,  1 Dec 2017 17:24:33 -0600	[thread overview]
Message-ID: <20171201232433.25193-8-eblake@redhat.com> (raw)
In-Reply-To: <20171201232433.25193-1-eblake@redhat.com>

Use of a loop construct for code that is not intended to repeat
does not make much idiomatic sense, except in one place: it is a
common usage in macros in order to wrap arbitrary code with
single-statement semantics.  But when used in a macro, it is more
typical for the caller to supply the trailing ';' when calling
the macro.

Although qemu coding style frowns on bare:
  if (cond)
    statement1;
  else
    statement2;
where extra semicolons actually cause syntax errors, we still
want our macro styles to be easily copied to other projects.
Thus, declare it an error if we encounter any form of 'while (0)'
with a semicolon in the same line.

Signed-off-by: Eric Blake <eblake@redhat.com>
---
 scripts/checkpatch.pl | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index 34df753571..27800a4ed9 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -1622,6 +1622,11 @@ sub process {
 			}
 		}

+# 'do ... while (0/false)' only makes sense in macros, without trailing ';'
+		if ($line =~ /while\s*\((0|false)\);/) {
+			ERROR("suspicious ; after while (0)\n" . $herecurr);
+		}
+
 # Check relative indent for conditionals and blocks.
 		if ($line =~ /\b(?:(?:if|while|for)\s*\(|do\b)/ && $line !~ /^.\s*#/ && $line !~ /\}\s*while\s*/) {
 			my ($s, $c) = ($stat, $cond);
-- 
2.14.3

  parent reply	other threads:[~2017-12-01 23:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-01 23:24 [Qemu-devel] [PATCH v2 0/7] macro do/while (0) cleanup Eric Blake
2017-12-01 23:24 ` [Qemu-devel] [PATCH v2 1/7] net: Drop unusual use of do { } while (0); Eric Blake
2017-12-01 23:24 ` [Qemu-devel] [PATCH v2 2/7] mips: Tweak location of ';' in macros Eric Blake
2017-12-01 23:24 ` [Qemu-devel] [PATCH v2 3/7] chardev: Use goto/label instead of do/break/while(0) Eric Blake
2017-12-03 14:20   ` Marc-André Lureau
2017-12-01 23:24 ` [Qemu-devel] [PATCH v2 4/7] chardev: Clean up previous patch indentation Eric Blake
2017-12-03 14:20   ` Marc-André Lureau
2017-12-01 23:24 ` [Qemu-devel] [PATCH v2 5/7] tests: Avoid 'do/while(false); ' in vhost-user-bridge Eric Blake
2017-12-01 23:24 ` [Qemu-devel] [PATCH v2 6/7] maint: Fix macros with broken 'do/while(0); ' usage Eric Blake
2017-12-02 11:53   ` Juan Quintela
2017-12-01 23:24 ` Eric Blake [this message]
2018-01-09 20:52 ` [Qemu-devel] [PATCH v2 0/7] macro do/while (0) cleanup Eric Blake
2018-01-10 13:52   ` Paolo Bonzini

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=20171201232433.25193-8-eblake@redhat.com \
    --to=eblake@redhat.com \
    --cc=armbru@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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).