Lines Matching full:macros

722 for aligning variables/macros, for reflowing text and other similar tasks.
792 12) Macros, Enums and RTL
795 Names of macros defining constants and labels in enums are capitalized.
803 CAPITALIZED macro names are appreciated but macros resembling functions
806 Generally, inline functions are preferable to macros resembling functions.
808 Macros with multiple statements should be enclosed in a do - while block:
818 Function-like macros with unused parameters should be replaced by static
831 are generally better documented than macros for some reason.
841 Things to avoid when using macros:
843 1) macros that affect control flow:
856 2) macros that depend on having a local variable with a magic name:
865 3) macros with arguments that are used as l-values: FOO(x) = y; will
868 4) forgetting about precedence: macros defining constants using expressions
870 macros using parameters.
877 5) namespace collisions when defining local variables in macros resembling
892 The cpp manual deals with macros exhaustively. The gcc internals manual also
908 There are a number of driver model diagnostic macros in <linux/dev_printk.h>
979 appropriate (for example as a means of replacing macros, see Chapter 12), it
1067 18) Don't re-invent the kernel macros
1070 The header file include/linux/kernel.h contains a number of macros that
1085 There are also min() and max() macros that do strict type checking if you
1243 WARN*() macros are not to be used for anything that is expected to happen