is there a reason that compiler-gcc.h defines both:
#define __pure __attribute__((pure))
#define __attribute_pure__ __attribute__((pure))
one would think that the shorter form would be preferable to go along
with the other short forms defined in that header file, but a quick
tree scan shows that the longer form is used exclusively (although
still not in what you'd call overwhelming numbers):
$ grep -rw __attribute_pure__ * | wc -l
17
$ grep -rw __pure * | wc -l
1
is there any reason not to just change those few instances to the
short form?
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
-
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/
[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]
