public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Joseph Carter <knghtbrd@debian.org>
Cc: Bart Trojanowski <bart@jukie.net>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: asm/unistd.h
Date: 05 Apr 2001 16:45:44 +0200	[thread overview]
Message-ID: <jevgojiew7.fsf@hawking.suse.de> (raw)
In-Reply-To: <A0C675E9DC2CD411A5870040053AEBA0284170@MAINSERVER> <Pine.LNX.4.30.0104050901500.13496-100000@localhost> <20010405072628.C22001@debian.org>
In-Reply-To: <20010405072628.C22001@debian.org>

Joseph Carter <knghtbrd@debian.org> writes:

|> On Thu, Apr 05, 2001 at 09:06:20AM -0400, Bart Trojanowski wrote:
|> > So you ask: "why not just use a { ... } to define a macro".  I don't
|> > remember the case for this but I know it's there.  It has to do with a
|> > complicated if/else structure where a simple {} breaks.
|> 
|> This doesn't follow in my mind.  I can't think of a case where a { ... }
|> would fail, but a do { ... } while (0) would succeed.  The former would
|> also save a few keystrokes.

Try this and watch your compiler complaining:

#define foo() { }
#define bar() do { } while (0)
void mumble ()
{
        if (1) foo(); else bar();
        if (2) bar(); else foo();
}

Andreas.

-- 
Andreas Schwab                                  "And now for something
SuSE Labs                                        completely different."
Andreas.Schwab@suse.de
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5

  parent reply	other threads:[~2001-04-05 14:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-05 12:58 asm/unistd.h Sardañons, Eliel
2001-04-05 13:06 ` asm/unistd.h Bart Trojanowski
2001-04-05 13:12   ` asm/unistd.h Tim Waugh
2001-04-05 14:26   ` asm/unistd.h Joseph Carter
2001-04-05 14:35     ` asm/unistd.h Bart Trojanowski
2001-04-05 14:35     ` asm/unistd.h Stephen Thomas
2001-04-05 14:45     ` Andreas Schwab [this message]
2001-04-05 17:38       ` asm/unistd.h J . A . Magallon
2001-04-05 13:07 ` asm/unistd.h David S. Miller
2001-04-05 13:13 ` asm/unistd.h Ben Collins
  -- strict thread matches above, loose matches on Subject: below --
2001-04-05 15:23 asm/unistd.h Steve Grubb
2001-04-05 15:41 ` asm/unistd.h Bart Trojanowski
2001-04-05 15:45 ` asm/unistd.h David S. Miller

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=jevgojiew7.fsf@hawking.suse.de \
    --to=schwab@suse.de \
    --cc=bart@jukie.net \
    --cc=knghtbrd@debian.org \
    --cc=linux-kernel@vger.kernel.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