Lines Matching refs:preprocessor
53 * Cpp: (cpp). The GNU C preprocessor.
73 The C preprocessor implements the macro language used to transform C,
180 The C preprocessor, often known as @dfn{cpp}, is a @dfn{macro processor}
186 The C preprocessor is intended to be used only with C, C++, and
202 Wherever possible, you should use a preprocessor geared to the language
209 preprocessor, which provides a small superset of the features of ISO
210 Standard C@. In its default mode, the GNU C preprocessor does not do a
219 This manual describes the behavior of the ISO preprocessor. To
220 minimize gratuitous differences, where the ISO preprocessor's
222 traditional preprocessor should behave the same way. The various
256 output from the preprocessor with the @option{-E} option, it will be
286 The preprocessor performs a series of textual transformations on its
464 tokenization, the preprocessor is greedy. It always makes each token,
485 The compiler does not re-tokenize the preprocessor's output. Each
493 underscore. Keywords of C have no significance to the preprocessor;
498 This is mostly true of other languages which use the C preprocessor.
500 preprocessor. @xref{C++ Named Operators}.
527 The purpose of this unusual definition is to isolate the preprocessor
559 closing quote or angle bracket. The preprocessor looks for the header
587 preprocessor's output unchanged. The C compiler will almost certainly
610 NULs are preserved. In the latter two cases the preprocessor emits a
624 what most people think of as the preprocessor's job.
636 for arbitrary fragments of C code. The preprocessor will replace the
776 The @samp{#include} directive works by directing the C preprocessor to
778 current file. The output from the preprocessor contains the output
833 separate line by the C preprocessor, even if the included file lacks a
839 By default, the preprocessor looks for header files included by the quote
848 preprocessor's default behavior is to look only in the standard system
873 that affect where the preprocessor searches for header files, the
875 search path used by the preprocessor.
877 Note that you can also prevent the preprocessor from searching any of
911 because @code{FILE_FOO_SEEN} is defined. The preprocessor will skip
985 That rapidly becomes tedious. Instead, the preprocessor offers the
997 @code{SYSTEM_H} will be expanded, and the preprocessor will look for
1003 tokens, not text. The preprocessor has no way of knowing that the macro
1149 keyword. The preprocessor does not know anything about keywords. This
1151 older compiler that does not understand it. However, the preprocessor
1200 then the C preprocessor will recognize and @dfn{expand} the macro
1234 The C preprocessor scans your program sequentially. Macro definitions
1236 to the C preprocessor
1252 When the preprocessor expands a macro name, the macro's expansion
1428 preprocessor (but many macros will then expand to invalid code).
1445 empty argument. Previous GNU preprocessor implementations and
1466 parameter is used with a leading @samp{#}, the preprocessor replaces it
1473 string constants and stringized arguments. The preprocessor
1504 around the fragment. The preprocessor backslash-escapes the quotes
1563 @code{+} in either order. If you try, the preprocessor issues a warning
1578 Keep in mind that the C preprocessor converts comments to whitespace
1797 a C string constant. This is the path by which the preprocessor opened
1836 manual). Neither of them is a macro; the preprocessor does not know the
1844 the preprocessor is being run. The string constant contains eleven
1854 which the preprocessor is being run. The string constant contains
1865 preprocessor always conforms to the standard unless the
1953 preprocessor: C, C++, Objective-C and Fortran. Their values are the major
1958 macros are also defined if you invoke the preprocessor directly.
2008 on the command line of the preprocessor or C compiler.
2468 The C preprocessor normally predefines several macros that indicate what
2509 treated as such even in the preprocessor. They function as operators in
2585 same as the old one, the preprocessor issues a warning and changes the
2589 preprocessor will only complain if the definitions do not match.
2595 Occasionally it is convenient to use preprocessor directives within
2897 the preprocessor output unchanged. Consider an example:
2930 left alone by the preprocessor whenever it's used in running text. You
2991 And why not skip it and make the preprocessor faster?'' The answer is
3089 A @dfn{conditional} is a directive that instructs the preprocessor to
3095 A conditional in the C preprocessor resembles in some ways an @code{if}
3156 A conditional in the C preprocessor begins with a @dfn{conditional
3190 will be included in the output of the preprocessor if and only if
3306 The preprocessor does not know anything about types in the language.
3312 The preprocessor calculates the value of @var{expression}. It carries
3460 test succeeds is it valid to use @code{__has_attribute} as a preprocessor
3492 constant integer contexts and in preprocessor @samp{#if} and @samp{#elif}
3497 The operator may also be used in preprocessor @samp{#if} and @samp{#elif}
3526 directives that would cause the preprocessor to fail.
3542 test succeeds is it valid to use @code{__has_include} as a preprocessor
3587 The directive @samp{#error} causes the preprocessor to report a fatal
3616 preprocessor to issue a warning and continue preprocessing. The tokens
3632 The C preprocessor informs the C compiler of the location in your source
3639 @command{bison} parser generator, you may want to adjust the preprocessor's
3650 for subsequent input in the current preprocessor input file.
3719 The preprocessor does not accept it within a preprocessing conditional
3725 preprocessor itself. Other pragmas are meaningful to the C or C++
3784 @code{#pragma GCC warning "message"} causes the preprocessor to issue
3789 embedded in preprocessor macros using @samp{_Pragma}.
3817 preprocessor output. The primary significance of the existence of the
3825 When the C preprocessor is used with the C, C++, or Objective-C
3833 The output from the C preprocessor looks much like the input, except
3839 preprocessor preserves whitespace between tokens, or replaces it with
3882 As an extension, the preprocessor accepts linemarkers in non-assembler
3888 Some directives may be duplicated in the output of the preprocessor.
3890 preprocessor does not handle the pragma itself), and @samp{#define} and
3902 the preprocessing specified by the standard. When the preprocessor
3905 preprocessor.
3910 the preprocessor explicitly, and not in the compiler front ends.
3913 early pre-standard versions of GCC, nor to any true traditional preprocessor.
3929 The traditional preprocessor does not decompose its input into tokens
3930 the same way a standards-conforming preprocessor does. The input is
3951 of the output of the preprocessor, this means that comments can
3953 behave like separators for text handled by the preprocessor itself,
3993 Just as for the ISO preprocessor, what would be a closing quote can be
4095 preprocessor.
4105 A true traditional C preprocessor does not recognize @samp{#error} or
4140 In traditional C, some preprocessor directives did not exist.
4175 Here we document details of how the preprocessor's implementation
4239 @item The numeric value of character constants in preprocessor expressions.
4241 The preprocessor and compiler interpret character constants in the
4263 For a discussion on how the preprocessor locates header files,
4314 The C standard requires this to be at least 63. In preprocessor
4319 The preprocessor treats all characters as significant. The C standard
4444 Most often when you use the C preprocessor you do not have to invoke it
4446 preprocessor is sometimes useful on its own. You can invoke the
4447 preprocessor either with the @command{cpp} command, or via @command{gcc -E}.
4448 In GCC, the preprocessor is actually integrated with the compiler
4472 complete list of preprocessor-specific options.
4484 @var{outfile}. The preprocessor reads @var{infile} together with any