Lines Matching refs:preprocessor
55 * Cpp: (cpp). The GNU C preprocessor.
75 The C preprocessor implements the macro language used to transform C
183 The C preprocessor, often known as @dfn{cpp}, is a @dfn{macro processor}
189 The C preprocessor is intended to be used only with C and C++ source
205 Wherever possible, you should use a preprocessor geared to the language
212 preprocessor, which provides a small superset of the features of ISO
213 Standard C@. In its default mode, the GNU C preprocessor does not do a
221 This manual describes the behavior of the ISO preprocessor. To
222 minimize gratuitous differences, where the ISO preprocessor's
224 traditional preprocessor should behave the same way. The various
258 output from the preprocessor with the @option{-E} option, it will be
288 The preprocessor performs a series of textual transformations on its
466 tokenization, the preprocessor is greedy. It always makes each token,
487 The compiler does not re-tokenize the preprocessor's output. Each
495 underscore. Keywords of C have no significance to the preprocessor;
500 This is mostly true of other languages which use the C preprocessor.
502 preprocessor. @xref{C++ Named Operators}.
532 The purpose of this unusual definition is to isolate the preprocessor
564 closing quote or angle bracket. The preprocessor looks for the header
594 the preprocessor's output unmolested. The C compiler will almost
617 NULs are preserved. In the latter two cases the preprocessor emits a
631 what most people think of as the preprocessor's job.
643 for arbitrary fragments of C code. The preprocessor will replace the
782 The @samp{#include} directive works by directing the C preprocessor to
784 current file. The output from the preprocessor contains the output
839 separate line by the C preprocessor, even if the included file lacks a
941 because @code{FILE_FOO_SEEN} is defined. The preprocessor will skip
982 That rapidly becomes tedious. Instead, the preprocessor offers the
994 @code{SYSTEM_H} will be expanded, and the preprocessor will look for
1000 tokens, not text. The preprocessor has no way of knowing that the macro
1148 keyword. The preprocessor does not know anything about keywords. This
1150 older compiler that does not understand it. However, the preprocessor
1199 then the C preprocessor will recognize and @dfn{expand} the macro
1233 The C preprocessor scans your program sequentially. Macro definitions
1235 to the C preprocessor
1251 When the preprocessor expands a macro name, the macro's expansion
1427 preprocessor (but many macros will then expand to invalid code).
1444 empty argument. Previous GNU preprocessor implementations and
1465 parameter is used with a leading @samp{#}, the preprocessor replaces it
1472 string constants and stringified arguments. The preprocessor will
1503 around the fragment. The preprocessor backslash-escapes the quotes
1562 @code{+} in either order. If you try, the preprocessor issues a warning
1577 Keep in mind that the C preprocessor converts comments to whitespace
1786 a C string constant. This is the path by which the preprocessor opened
1825 manual). Neither of them is a macro; the preprocessor does not know the
1833 the preprocessor is being run. The string constant contains eleven
1843 which the preprocessor is being run. The string constant contains
1854 preprocessor always conforms to the standard unless the
1926 preprocessor: C and C++. Their values are the major version, minor
1930 macros are also defined if you invoke the preprocessor directly.
1985 on the command line of the preprocessor or C compiler.
2168 The C preprocessor normally predefines several macros that indicate what
2209 treated as such even in the preprocessor. They function as operators in
2285 same as the old one, the preprocessor issues a warning and changes the
2289 preprocessor will only complain if the definitions do not match.
2295 Occasionally it is convenient to use preprocessor directives within
2607 the preprocessor output unchanged. Consider an example:
2640 left alone by the preprocessor whenever it's used in running text. You
2701 And why not skip it and make the preprocessor faster?'' The answer is
2799 A @dfn{conditional} is a directive that instructs the preprocessor to
2805 A conditional in the C preprocessor resembles in some ways an @code{if}
2869 A conditional in the C preprocessor begins with a @dfn{conditional
2899 will be included in the output of the preprocessor if and only if
3015 The preprocessor does not know anything about types in the language.
3021 The preprocessor calculates the value of @var{expression}. It carries
3174 The directive @samp{#error} causes the preprocessor to report a fatal
3203 preprocessor to issue a warning and continue preprocessing. The tokens
3219 The C preprocessor informs the C compiler of the location in your source
3226 @command{bison} parser generator, you may want to adjust the preprocessor's
3237 for subsequent input in the current preprocessor input file.
3347 The preprocessor does not accept it within a preprocessing conditional
3353 preprocessor itself. Other pragmas are meaningful to the C or C++
3428 preprocessor output. The primary significance of the existence of the
3436 When the C preprocessor is used with the C or C++ compilers, it is
3443 The output from the C preprocessor looks much like the input, except
3449 preprocessor preserves whitespace between tokens, or replaces it with
3492 As an extension, the preprocessor accepts linemarkers in non-assembler
3498 Some directives may be duplicated in the output of the preprocessor.
3500 preprocessor does not handle the pragma itself), and @samp{#define} and
3514 preprocessor.
3517 the preprocessor, and not in the compiler front ends. This chapter
3518 outlines the traditional preprocessor semantics we implemented.
3521 earlier versions of GCC, nor to any true traditional preprocessor.
3537 The traditional preprocessor does not decompose its input into tokens
3538 the same way a standards-conforming preprocessor does. The input is
3559 of the output of the preprocessor, this means that comments can
3561 behave like separators for text handled by the preprocessor itself,
3601 Just as for the ISO preprocessor, what would be a closing quote can be
3703 preprocessor.
3713 A true traditional C preprocessor does not recognize @samp{#error} or
3748 In traditional C, some preprocessor directives did not exist.
3783 Here we document details of how the preprocessor's implementation
3847 @item The numeric value of character constants in preprocessor expressions.
3849 The preprocessor and compiler interpret character constants in the
3871 For a discussion on how the preprocessor locates header files,
3922 The C standard requires this to be at least 63. In preprocessor
3927 The preprocessor treats all characters as significant. The C standard
4104 @item The form of whitespace between tokens in preprocessor output
4107 also the format used by stringification. Normally, the preprocessor
4132 In the current version of the preprocessor, if @samp{##} appears between
4163 Most often when you use the C preprocessor you will not have to invoke it
4165 preprocessor is sometimes useful on its own. All the options listed
4170 @emph{Note:} Whether you use the preprocessor by way of @command{gcc}
4199 The C preprocessor expects two file names as arguments, @var{infile} and
4200 @var{outfile}. The preprocessor reads @var{infile} together with any