⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 the-preprocessing-language.html

📁 gcc手册
💻 HTML
字号:
<html lang="en">

<head>

<title>The C Preprocessor</title>

<meta http-equiv="Content-Type" content="text/html">

<meta name="description" content="The C Preprocessor">

<meta name="generator" content="makeinfo 4.3">

<link href="http://www.gnu.org/software/texinfo/" rel="generator-home">

<!--

Copyright &copy; 1987, 1989, 1991, 1992, 1993, 1994, 1995, 1996,

1997, 1998, 1999, 2000, 2001, 2002, 2003

Free Software Foundation, Inc.



   <p>Permission is granted to copy, distribute and/or modify this document

under the terms of the GNU Free Documentation License, Version 1.1 or

any later version published by the Free Software Foundation.  A copy of

the license is included in the

section entitled "GNU Free Documentation License".



   <p>This manual contains no Invariant Sections.  The Front-Cover Texts are

(a) (see below), and the Back-Cover Texts are (b) (see below).



   <p>(a) The FSF's Front-Cover Text is:



   <p>A GNU Manual



   <p>(b) The FSF's Back-Cover Text is:



   <p>You have freedom to copy and modify this GNU Manual, like GNU

     software.  Copies published by the Free Software Foundation raise

     funds for GNU development. 

-->

</head>

<body>

<div class="node">

<p>

Node:<a name="The%20preprocessing%20language">The preprocessing language</a>,

Previous:<a rel="previous" accesskey="p" href="Tokenization.html#Tokenization">Tokenization</a>,

Up:<a rel="up" accesskey="u" href="Overview.html#Overview">Overview</a>

<hr><br>

</div>



<h3 class="section">The preprocessing language</h3>



   <p>After tokenization, the stream of tokens may simply be passed straight

to the compiler's parser.  However, if it contains any operations in the

<dfn>preprocessing language</dfn>, it will be transformed first.  This stage

corresponds roughly to the standard's "translation phase 4" and is

what most people think of as the preprocessor's job.



   <p>The preprocessing language consists of <dfn>directives</dfn> to be executed

and <dfn>macros</dfn> to be expanded.  Its primary capabilities are:



     <ul>

<li>Inclusion of header files.  These are files of declarations that can be

substituted into your program.



     <li>Macro expansion.  You can define <dfn>macros</dfn>, which are abbreviations

for arbitrary fragments of C code.  The preprocessor will replace the

macros with their definitions throughout the program.  Some macros are

automatically defined for you.



     <li>Conditional compilation.  You can include or exclude parts of the

program according to various conditions.



     <li>Line control.  If you use a program to combine or rearrange source files

into an intermediate file which is then compiled, you can use line

control to inform the compiler where each source line originally came

from.



     <li>Diagnostics.  You can detect problems at compile time and issue errors

or warnings. 

</ul>



   <p>There are a few more, less useful, features.



   <p>Except for expansion of predefined macros, all these operations are

triggered with <dfn>preprocessing directives</dfn>.  Preprocessing directives

are lines in your program that start with <code>#</code>.  Whitespace is

allowed before and after the <code>#</code>.  The <code>#</code> is followed by an

identifier, the <dfn>directive name</dfn>.  It specifies the operation to

perform.  Directives are commonly referred to as <code>#</code><var>name</var><code></code>

where <var>name</var> is the directive name.  For example, <code>#define</code> is

the directive that defines a macro.



   <p>The <code>#</code> which begins a directive cannot come from a macro

expansion.  Also, the directive name is not macro expanded.  Thus, if

<code>foo</code> is defined as a macro expanding to <code>define</code>, that does

not make <code>#foo</code> a valid preprocessing directive.



   <p>The set of valid directive names is fixed.  Programs cannot define new

preprocessing directives.



   <p>Some directives require arguments; these make up the rest of the

directive line and must be separated from the directive name by

whitespace.  For example, <code>#define</code> must be followed by a macro

name and the intended expansion of the macro.



   <p>A preprocessing directive cannot cover more than one line.  The line

may, however, be continued with backslash-newline, or by a block comment

which extends past the end of the line.  In either case, when the

directive is processed, the continuations have already been merged with

the first line to make one long line.



   </body></html>



⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -