Lines Matching full:preprocessor
29 * Cpp: (cpp). The GNU C preprocessor.
35 The C Preprocessor
38 The C preprocessor implements the macro language used to transform C,
52 * Preprocessor Output::
166 The C preprocessor, often known as "cpp", is a "macro processor" that
172 The C preprocessor is intended to be used only with C, C++, and
188 Wherever possible, you should use a preprocessor geared to the
195 C preprocessor, which provides a small superset of the features of ISO
196 Standard C. In its default mode, the GNU C preprocessor does not do a
205 This manual describes the behavior of the ISO preprocessor. To
206 minimize gratuitous differences, where the ISO preprocessor's behavior
208 preprocessor should behave the same way. The various differences that
243 from the preprocessor with the `-E' option, it will be in UTF-8.
277 The preprocessor performs a series of textual transformations on its
419 possible tokenization, the preprocessor is greedy. It always makes
436 The compiler does not re-tokenize the preprocessor's output. Each
443 underscore. Keywords of C have no significance to the preprocessor;
448 This is mostly true of other languages which use the C preprocessor.
450 preprocessor. *Note C++ Named Operators::.
477 The purpose of this unusual definition is to isolate the preprocessor
502 or angle bracket. The preprocessor looks for the header file in
526 the preprocessor's output unmolested. The C compiler will almost
546 are preserved. In the latter two cases the preprocessor emits a
564 most people think of as the preprocessor's job.
573 for arbitrary fragments of C code. The preprocessor will replace
710 The `#include' directive works by directing the C preprocessor to scan
712 current file. The output from the preprocessor contains the output
759 separate line by the C preprocessor, even if the included file lacks a
855 `FILE_FOO_SEEN' is defined. The preprocessor will skip over the entire
929 That rapidly becomes tedious. Instead, the preprocessor offers the
938 `SYSTEM_H' will be expanded, and the preprocessor will look for
943 tokens, not text. The preprocessor has no way of knowing that the macro
1090 keyword. The preprocessor does not know anything about keywords. This
1092 older compiler that does not understand it. However, the preprocessor
1134 then the C preprocessor will recognize and "expand" the macro
1163 The C preprocessor scans your program sequentially. Macro
1165 following input to the C preprocessor
1176 When the preprocessor expands a macro name, the macro's expansion
1323 preprocessor (but many macros will then expand to invalid code). You
1338 Previous GNU preprocessor implementations and documentation were
1358 is used with a leading `#', the preprocessor replaces it with the
1365 string constants and stringified arguments. The preprocessor will
1391 characters around the fragment. The preprocessor backslash-escapes the
1447 either order. If you try, the preprocessor issues a warning and emits
1461 Keep in mind that the C preprocessor converts comments to whitespace
1640 preprocessor opened the file, not the short name specified in
1675 manual). Neither of them is a macro; the preprocessor does not know the
1681 which the preprocessor is being run. The string constant contains
1691 which the preprocessor is being run. The string constant contains
1702 true; however, the preprocessor always conforms to the standard
1783 preprocessor: C, C++, Objective-C and Fortran. Their values are
1788 preprocessor directly.
1838 on the command line of the preprocessor or C compiler.
2194 The C preprocessor normally predefines several macros that indicate what
2234 treated as such even in the preprocessor. They function as operators in
2300 same as the old one, the preprocessor issues a warning and changes the
2304 preprocessor will only complain if the definitions do not match.
2312 Occasionally it is convenient to use preprocessor directives within the
2578 preprocessor output unchanged. Consider an example:
2605 alone by the preprocessor whenever it's used in running text. You can
2657 difference? And why not skip it and make the preprocessor faster?"
2747 A "conditional" is a directive that instructs the preprocessor to
2749 stream passed to the compiler. Preprocessor conditionals can test
2753 A conditional in the C preprocessor resembles in some ways an `if'
2819 A conditional in the C preprocessor begins with a "conditional
2845 included in the output of the preprocessor if and only if MACRO is
2946 The preprocessor does not know anything about types in the language.
2952 The preprocessor calculates the value of EXPRESSION. It carries out
3095 The directive `#error' causes the preprocessor to report a fatal error.
3117 preprocessor to issue a warning and continue preprocessing. The tokens
3135 The C preprocessor informs the C compiler of the location in your source
3142 `bison' parser generator, you may want to adjust the preprocessor's
3152 the current preprocessor input file. `#line' has three variants:
3252 The preprocessor does not accept it within a preprocessing conditional
3257 preprocessor itself. Other pragmas are meaningful to the C or C++
3308 File: cpp.info, Node: Other Directives, Next: Preprocessor Output, Prev: Pragmas, Up: Top
3325 preprocessor output. The primary significance of the existence of the
3331 File: cpp.info, Node: Preprocessor Output, Next: Traditional Mode, Prev: Other Directives, Up: Top
3333 9 Preprocessor Output
3336 When the C preprocessor is used with the C, C++, or Objective-C
3342 The output from the C preprocessor looks much like the input, except
3348 a preprocessor preserves whitespace between tokens, or replaces it with
3388 As an extension, the preprocessor accepts linemarkers in
3394 Some directives may be duplicated in the output of the preprocessor.
3395 These are `#ident' (always), `#pragma' (only if the preprocessor does
3404 File: cpp.info, Node: Traditional Mode, Next: Implementation Details, Prev: Preprocessor Output, Up: Top
3412 preprocessor.
3415 the preprocessor, and not in the compiler front ends. This chapter
3416 outlines the traditional preprocessor semantics we implemented.
3419 earlier versions of GCC, nor to any true traditional preprocessor.
3438 The traditional preprocessor does not decompose its input into tokens
3439 the same way a standards-conforming preprocessor does. The input is
3459 of the output of the preprocessor, this means that comments can
3461 like separators for text handled by the preprocessor itself, since it
3491 Just as for the ISO preprocessor, what would be a closing quote can
3587 preprocessor.
3594 * A true traditional C preprocessor does not recognize `#error' or
3625 * In traditional C, some preprocessor directives did not exist.
3660 Here we document details of how the preprocessor's implementation
3723 * The numeric value of character constants in preprocessor
3726 The preprocessor and compiler interpret character constants in the
3749 For a discussion on how the preprocessor locates header files,
3797 The C standard requires this to be at least 63. In preprocessor
3802 The preprocessor treats all characters as significant. The C
3942 * The form of whitespace between tokens in preprocessor output
3944 *Note Preprocessor Output::, for the current textual format. This
3946 preprocessor communicates tokens directly to the compiler's
3971 In the current version of the preprocessor, if `##' appears between
4003 Most often when you use the C preprocessor you will not have to invoke
4005 preprocessor is sometimes useful on its own. All the options listed
4010 _Note:_ Whether you use the preprocessor by way of `gcc' or `cpp',
4016 The C preprocessor expects two file names as arguments, INFILE and
4017 OUTFILE. The preprocessor reads INFILE together with any other files
4044 If you are invoking the preprocessor from a shell or shell-like
4088 expressions. Note that many of the preprocessor's warnings are on
4123 once. The preprocessor will also warn if the macro has not been
4179 file. The preprocessor outputs one `make' rule containing the
4191 This option does not suppress the preprocessor's debug output,
4213 dependencies to. If no `-MF' switch is given the preprocessor
4376 for FILE is the preprocessor's working directory _instead of_ the
4445 such as `#define', `#ifdef', and `#error'. Other preprocessor
4469 Indicate to the preprocessor that the input file has already been
4472 most directives. The preprocessor still recognizes and removes
4475 preprocessor is little more than a tokenizer for the front ends.
4482 Set the distance between tab stops. This helps the preprocessor
4511 Enable generation of linemarkers in the preprocessor output that
4514 preprocessor will emit, after the initial linemarker, a second
4549 the preprocessor, including predefined macros. This gives
4551 of the preprocessor. Assuming you have no file `foo.h', the
4577 definedness is tested in preprocessor directives, are output;
4584 preprocessor. This might be useful when running the preprocessor
4586 which might be confused by the linemarkers. *Note Preprocessor
4595 the preprocessor to treat comments as tokens in their own right.
5400 * linemarkers: Preprocessor Output. (line 28)
5418 * output format: Preprocessor Output. (line 12)
5527 Node: Preprocessor Output135811
