Lines Matching refs:preprocessor
25 * Cpp: (cpp). The GNU C preprocessor.
34 The C preprocessor implements the macro language used to transform C,
160 The C preprocessor, often known as "cpp", is a "macro processor" that is
165 The C preprocessor is intended to be used only with C, C++, and
181 Wherever possible, you should use a preprocessor geared to the
188 C preprocessor, which provides a small superset of the features of ISO
189 Standard C. In its default mode, the GNU C preprocessor does not do a
198 This manual describes the behavior of the ISO preprocessor. To
199 minimize gratuitous differences, where the ISO preprocessor's behavior
201 preprocessor should behave the same way. The various differences that
236 from the preprocessor with the '-E' option, it will be in UTF-8.
270 The preprocessor performs a series of textual transformations on its
412 possible tokenization, the preprocessor is greedy. It always makes each
428 The compiler does not re-tokenize the preprocessor's output. Each
435 Keywords of C have no significance to the preprocessor; they are
440 This is mostly true of other languages which use the C preprocessor.
442 preprocessor. *Note C++ Named Operators::.
466 The purpose of this unusual definition is to isolate the preprocessor
491 or angle bracket. The preprocessor looks for the header file in
513 preprocessor's output unchanged. The C compiler will almost certainly
532 are preserved. In the latter two cases the preprocessor emits a warning
550 most people think of as the preprocessor's job.
559 for arbitrary fragments of C code. The preprocessor will replace
696 The '#include' directive works by directing the C preprocessor to scan
698 current file. The output from the preprocessor contains the output
745 separate line by the C preprocessor, even if the included file lacks a
754 By default, the preprocessor looks for header files included by the
761 For the angle-bracket form '#include <FILE>', the preprocessor's
785 affect where the preprocessor searches for header files, the directory
787 the preprocessor.
789 Note that you can also prevent the preprocessor from searching any of
819 'FILE_FOO_SEEN' is defined. The preprocessor will skip over the entire
890 That rapidly becomes tedious. Instead, the preprocessor offers the
899 'SYSTEM_H' will be expanded, and the preprocessor will look for
904 tokens, not text. The preprocessor has no way of knowing that the macro
1042 keyword. The preprocessor does not know anything about keywords. This
1044 older compiler that does not understand it. However, the preprocessor
1086 then the C preprocessor will recognize and "expand" the macro
1115 The C preprocessor scans your program sequentially. Macro
1117 following input to the C preprocessor
1128 When the preprocessor expands a macro name, the macro's expansion
1275 preprocessor (but many macros will then expand to invalid code). You
1290 Previous GNU preprocessor implementations and documentation were
1309 is used with a leading '#', the preprocessor replaces it with the
1316 string constants and stringized arguments. The preprocessor replaces
1340 around the fragment. The preprocessor backslash-escapes the quotes
1396 either order. If you try, the preprocessor issues a warning and emits
1410 Keep in mind that the C preprocessor converts comments to whitespace
1598 preprocessor opened the file, not the short name specified in
1633 Neither of them is a macro; the preprocessor does not know the name of
1639 which the preprocessor is being run. The string constant contains
1649 which the preprocessor is being run. The string constant contains
1660 true; however, the preprocessor always conforms to the standard
1745 preprocessor: C, C++, Objective-C and Fortran. Their values are
1749 to Z. These macros are also defined if you invoke the preprocessor
1794 on the command line of the preprocessor or C compiler.
2246 The C preprocessor normally predefines several macros that indicate what
2286 treated as such even in the preprocessor. They function as operators in
2349 same as the old one, the preprocessor issues a warning and changes the
2353 preprocessor will only complain if the definitions do not match.
2361 Occasionally it is convenient to use preprocessor directives within the
2616 preprocessor output unchanged. Consider an example:
2643 alone by the preprocessor whenever it's used in running text. You can
2695 difference? And why not skip it and make the preprocessor faster?" The
2784 A "conditional" is a directive that instructs the preprocessor to select
2790 A conditional in the C preprocessor resembles in some ways an 'if'
2853 A conditional in the C preprocessor begins with a "conditional
2883 included in the output of the preprocessor if and only if MACRO is
2983 The preprocessor does not know anything about types in the language.
2989 The preprocessor calculates the value of EXPRESSION. It carries out
3125 test succeeds is it valid to use '__has_attribute' as a preprocessor
3158 integer contexts and in preprocessor '#if' and '#elif' expressions to
3163 be used in preprocessor '#if' and '#elif' expressions. The
3191 would cause the preprocessor to fail.
3206 test succeeds is it valid to use '__has_include' as a preprocessor
3249 The directive '#error' causes the preprocessor to report a fatal error.
3271 preprocessor to issue a warning and continue preprocessing. The tokens
3289 The C preprocessor informs the C compiler of the location in your source
3296 'bison' parser generator, you may want to adjust the preprocessor's
3306 the current preprocessor input file. '#line' has three variants:
3364 The preprocessor does not accept it within a preprocessing conditional
3369 preprocessor itself. Other pragmas are meaningful to the C or C++
3420 '#pragma GCC warning "message"' causes the preprocessor to issue a
3425 in preprocessor macros using '_Pragma'.
3451 preprocessor output. The primary significance of the existence of the
3462 When the C preprocessor is used with the C, C++, or Objective-C
3468 The output from the C preprocessor looks much like the input, except
3474 a preprocessor preserves whitespace between tokens, or replaces it with
3510 As an extension, the preprocessor accepts linemarkers in
3516 Some directives may be duplicated in the output of the preprocessor.
3517 These are '#ident' (always), '#pragma' (only if the preprocessor does
3532 preprocessing specified by the standard. When the preprocessor is
3534 traditional preprocessor.
3539 preprocessor explicitly, and not in the compiler front ends.
3543 preprocessor. After all, inconsistencies among traditional
3561 The traditional preprocessor does not decompose its input into tokens
3562 the same way a standards-conforming preprocessor does. The input is
3582 the output of the preprocessor, this means that comments can effectively
3584 separators for text handled by the preprocessor itself, since it doesn't
3613 Just as for the ISO preprocessor, what would be a closing quote can
3708 preprocessor.
3715 * A true traditional C preprocessor does not recognize '#error' or
3745 * In traditional C, some preprocessor directives did not exist.
3780 Here we document details of how the preprocessor's implementation
3842 * The numeric value of character constants in preprocessor
3845 The preprocessor and compiler interpret character constants in the
3867 For a discussion on how the preprocessor locates header files,
3914 The C standard requires this to be at least 63. In preprocessor
3919 The preprocessor treats all characters as significant. The C
4027 Most often when you use the C preprocessor you do not have to invoke it
4029 preprocessor is sometimes useful on its own. You can invoke the
4030 preprocessor either with the 'cpp' command, or via 'gcc -E'. In GCC,
4031 the preprocessor is actually integrated with the compiler rather than a
4044 OUTFILE. The preprocessor reads INFILE together with any other files it
4072 If you are invoking the preprocessor from a shell or shell-like
4093 FILE is the preprocessor's working directory _instead of_ the
4125 file. The preprocessor outputs one 'make' rule containing the
4137 This option does not suppress the preprocessor's debug output, such
4158 dependencies to. If no '-MF' switch is given the preprocessor
4235 Indicate to the preprocessor that the input file has already been
4238 most directives. The preprocessor still recognizes and removes
4241 preprocessor is little more than a tokenizer for the front ends.
4254 such as '#define', '#ifdef', and '#error'. Other preprocessor
4284 Set the distance between tab stops. This helps the preprocessor
4293 option makes the preprocessor and the compiler consume more memory.
4341 Enable generation of linemarkers in the preprocessor output that
4343 preprocessing. When this option is enabled, the preprocessor
4369 the preprocessor to treat comments as tokens in their own right.
4389 preprocessor. This might be useful when running the preprocessor
4427 preprocessor. Other LETTERS are interpreted by the compiler
4435 the preprocessor, including predefined macros. This gives you
4437 preprocessor. Assuming you have no file 'foo.h', the command
4459 definedness is tested in preprocessor directives, are output;
4607 once. The preprocessor also warns if the macro has not been used
4614 conditional blocks, then the preprocessor reports it as unused. To