public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: macros:  "do-while" versus "({ })" and a compile-time error
Date: Tue, 09 Jan 2007 18:33:19 +0100	[thread overview]
Message-ID: <45A3D1DF.4020205@s5r6.in-berlin.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0701081347410.32420@localhost.localdomain>

Robert P. J. Day wrote:
>   just to stir the pot a bit regarding the discussion of the two
> different ways to define macros,

You mean function-like macros, right?

> i've just noticed that the "({ })"
> notation is not universally acceptable.  i've seen examples where
> using that notation causes gcc to produce:
> 
>   error: braced-group within expression allowed only inside a function

And function calls and macros which expand to "do { expr; } while (0)"
won't work anywhere outside of functions either.

> i wasn't aware that there were limits on this notation.  can someone
> clarify this?  under what circumstances *can't* you use that notation?
> thanks.

The limitations are certainly highly compiler-specific.
-- 
Stefan Richter
-=====-=-=== ---= -=--=
http://arcgraph.de/sr/

  parent reply	other threads:[~2007-01-09 17:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-08 18:50 macros: "do-while" versus "({ })" and a compile-time error Robert P. J. Day
2007-01-09 17:08 ` H. Peter Anvin
2007-01-09 17:33 ` Stefan Richter [this message]
2007-01-09 19:23   ` linux-os (Dick Johnson)
2007-01-09 20:19     ` Stefan Richter
2007-01-10  6:20     ` Robert P. J. Day
2007-01-10 12:16       ` linux-os (Dick Johnson)
2007-01-10 13:46         ` Robert P. J. Day
2007-01-10 14:07           ` linux-os (Dick Johnson)
2007-01-10 18:25           ` Stefan Richter
2007-01-10 21:49         ` J.A. Magallón
2007-01-10 22:04           ` Andreas Schwab

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=45A3D1DF.4020205@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpjday@mindspring.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