macros: "do-while" versus "({ })" and a compile-time error

  just to stir the pot a bit regarding the discussion of the two
different ways to define macros, 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

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.

rday
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: macros: "do-while" versus "({ })" and a compile-time error
  - From: Stefan Richter <[email protected]>
- Re: macros: "do-while" versus "({ })" and a compile-time error
  - From: "H. Peter Anvin" <[email protected]>

Prev by Date: Re: kallsyms_lookup export in -mm
Next by Date: Re: kobject.c changes in -mm
Previous by thread: [PATCH] r/o bind mounts: add vfsmount and superblock writer counts
Next by thread: Re: macros: "do-while" versus "({ })" and a compile-time error
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]