Lines Matching refs:macros

725 for aligning variables/macros, for reflowing text and other similar tasks.
798 Names of macros defining constants and labels in enums are capitalized.
806 CAPITALIZED macro names are appreciated but macros resembling functions
809 Generally, inline functions are preferable to macros resembling functions.
821 Function-like macros with unused parameters should be replaced by static
834 are generally better documented than macros for some reason.
844 Things to avoid when using macros:
846 1) macros that affect control flow:
859 2) macros that depend on having a local variable with a magic name:
868 3) macros with arguments that are used as l-values: FOO(x) = y; will
871 4) forgetting about precedence: macros defining constants using expressions
873 macros using parameters.
880 5) namespace collisions when defining local variables in macros resembling
895 The cpp manual deals with macros exhaustively. The gcc internals manual also
911 There are a number of driver model diagnostic macros in <linux/dev_printk.h>
982 appropriate (for example as a means of replacing macros, see Chapter 12), it
1070 18) Don't re-invent the kernel macros
1073 The header file include/linux/kernel.h contains a number of macros that
1088 There are also min() and max() macros that do strict type checking if you
1246 WARN*() macros are not to be used for anything that is expected to happen