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 5/7] tests: Avoid 'do/while(false); ' in vhost-user-bridge
Date: Fri,  1 Dec 2017 17:24:31 -0600	[thread overview]
Message-ID: <20171201232433.25193-6-eblake@redhat.com> (raw)
In-Reply-To: <20171201232433.25193-1-eblake@redhat.com>

Use of a do/while(0) loop as a way to allow break statements in
the middle of execute-once code is unusual.  More typical is
the use of goto for early exits, with a label at the end of
the execute-once code, rather than nesting code in a scope;
however, the comment at the end of the existing code makes this
alternative a bit unpractical.

So, to avoid false positives from a future syntax check about
'while (false);', and to keep the loop form (in case someone
ever does add DONTWAIT support, where they can just as easily
manipulate the initial loop condition or add an if around the
final 'break'), I opted to use the form of a while(1) loop (the
break as an early exit is more idiomatic there), coupled with
a final break preserving the original comment.

Signed-off-by: Eric Blake <eblake@redhat.com>
---
 tests/vhost-user-bridge.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/tests/vhost-user-bridge.c b/tests/vhost-user-bridge.c
index d820033a72..e0605a529e 100644
--- a/tests/vhost-user-bridge.c
+++ b/tests/vhost-user-bridge.c
@@ -283,7 +283,7 @@ vubr_backend_recv_cb(int sock, void *ctx)
         return;
     }

-    do {
+    while (1) {
         struct iovec *sg;
         ssize_t ret, total = 0;
         unsigned int num;
@@ -343,7 +343,9 @@ vubr_backend_recv_cb(int sock, void *ctx)

         free(elem);
         elem = NULL;
-    } while (false); /* could loop if DONTWAIT worked? */
+
+        break;        /* could loop if DONTWAIT worked? */
+    }

     if (mhdr_cnt) {
         mhdr.num_buffers = i;
-- 
2.14.3

  parent reply	other threads:[~2017-12-01 23:24 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 ` Eric Blake [this message]
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 ` [Qemu-devel] [PATCH v2 7/7] checkpatch: Enforce proper do/while (0) style Eric Blake
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-6-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).