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

linux-os (Dick Johnson) wrote:
> On Tue, 9 Jan 2007, Stefan Richter wrote:
>> The limitations are certainly highly compiler-specific.
> 
> I don't think so.

I referred to the ({ expr; }) in this remark, not to do-while. It's not
a valid construct in many flavors of the C language in the first place.
Also, occurrences of ({ expr; }) could be expandable to a constant
expression but would still not be accepted by gcc's parser outside of
functions.
-- 
Stefan Richter
-=====-=-=== ---= -=--=
http://arcgraph.de/sr/
-
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/

---

• References:
  • macros: "do-while" versus "({ })" and a compile-time error
    • From: "Robert P. J. Day" <[email protected]>
  • 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: "linux-os \(Dick Johnson\)" <[email protected]>

• Prev by Date: Re: Finding hardlinks
• Next by Date: Re: 2.6.20-rc4: known unfixed regressions (v2)
• Previous by thread: Re: macros: "do-while" versus "({ })" and a compile-time error
• 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]