Lines Matching full:expanded
567 and "macros" to be expanded. Its primary capabilities are:
599 Also, the directive name is not macro expanded. Thus, if `foo' is
690 recognized, and macro names are not expanded. Thus, `#include <x/*y>'
938 `SYSTEM_H' will be expanded, and the preprocessor will look for
951 not `"' or `<', then the entire line is macro-expanded like running
1046 they are expanded. This immunity is granted on an ad-hoc basis, when
1146 backslash-newline. When the macro is expanded, however, it will all
1186 `TABLESIZE' is expanded first to produce `BUFSIZE', then that macro is
1187 expanded to produce the final result, `1024'.
1208 expanded again when the expansion is
1227 A function-like macro is only expanded if its name appears with a
1240 be expanded, it would cause a syntax error.
1273 parameters in the macro definition. When the macro is expanded, each
1302 All arguments to a macro are completely macro-expanded before they
1310 For example, `min (min (a, b), c)' is first expanded to
1360 Unlike normal parameter replacement, the argument is not macro-expanded
1382 `x' were a macro, it would be expanded in the `if' statement, but not
1422 macro-expanded first. But `s' is an ordinary argument to `xstr', so it
1423 is completely macro-expanded before `xstr' itself is expanded (*note
1425 argument, it has already been macro-expanded.
1436 expanded, the two tokens on either side of each `##' operator are
1458 with stringification, the actual argument is not macro-expanded first.
1522 The variable argument is completely macro-expanded before it is
1772 ensure that `__COUNTER__' is not expanded prior to inclusion of
2612 `x' is not expanded in this case either. Thus, if we have
2625 Each macro is expanded when it appears in the definition of the other
2634 Macro arguments are completely macro-expanded before they are
2637 the substituted arguments, is scanned again for macros to be expanded.
2642 macro calls, they are expanded during the first scan. The result
2651 expanded once in the first scan, and a second time in the second scan.
2671 would not be expanded.
2693 This can cause a macro expanded on the second scan to be called
2930 * Macros. All macros in the expression are expanded before actual
3173 ANYTHING ELSE is checked for macro calls, which are expanded. The
3466 `foo' and `bar' are distinct identifiers and expanded separately if
3513 macro is expanded, but if the `-CC' option is passed on the command
3637 merely means that the macro is not expanded.
3752 * Interpretation of the filename resulting from a macro-expanded
4122 macro is "used" if it is expanded or tested for existence at least
4576 Like `D' except that only macros that are expanded, or whose
4604 passed through to the output file where the macro is expanded.
