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

Robert P. J. Day wrote:
[...]
> what the above implies is
> that the ALIGN() macro can *never* be extended in that way because of
> the way it's being used in the struct definition above, outside of a
> function.
> 
> doesn't that place an unnecessarily limit on what might be done with
> ALIGN() in the future?
[...]

The one occurrence which is different from others could be changed.

But more importantly: Don't overuse macros.
-- 
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]>
- Re: 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: "linux-os \(Dick Johnson\)" <[email protected]>
- Re: macros: "do-while" versus "({ })" and a compile-time error
  - From: "Robert P. J. Day" <[email protected]>

Prev by Date: Re: [patch -mm] slab: use CPU_LOCK_[ACQUIRE|RELEASE]
Next by Date: Re: Fix the reproducible oops in scsi
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]