Ви не можете вибрати більше 25 тем Теми мають розпочинатися з літери або цифри, можуть містити дефіси (-) і не повинні перевищувати 35 символів.

148 lines
5.8KB

  1. <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
  2. <html>
  3. <!-- Copyright (C) 1987-2020 Free Software Foundation, Inc.
  4. Permission is granted to copy, distribute and/or modify this document
  5. under the terms of the GNU Free Documentation License, Version 1.3 or
  6. any later version published by the Free Software Foundation. A copy of
  7. the license is included in the
  8. section entitled "GNU Free Documentation License".
  9. This manual contains no Invariant Sections. The Front-Cover Texts are
  10. (a) (see below), and the Back-Cover Texts are (b) (see below).
  11. (a) The FSF's Front-Cover Text is:
  12. A GNU Manual
  13. (b) The FSF's Back-Cover Text is:
  14. You have freedom to copy and modify this GNU Manual, like GNU
  15. software. Copies published by the Free Software Foundation raise
  16. funds for GNU development. -->
  17. <!-- Created by GNU Texinfo 6.5, http://www.gnu.org/software/texinfo/ -->
  18. <head>
  19. <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  20. <title>Include Operation (The C Preprocessor)</title>
  21. <meta name="description" content="Include Operation (The C Preprocessor)">
  22. <meta name="keywords" content="Include Operation (The C Preprocessor)">
  23. <meta name="resource-type" content="document">
  24. <meta name="distribution" content="global">
  25. <meta name="Generator" content="makeinfo">
  26. <link href="index.html#Top" rel="start" title="Top">
  27. <link href="Index-of-Directives.html#Index-of-Directives" rel="index" title="Index of Directives">
  28. <link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
  29. <link href="Header-Files.html#Header-Files" rel="up" title="Header Files">
  30. <link href="Search-Path.html#Search-Path" rel="next" title="Search Path">
  31. <link href="Include-Syntax.html#Include-Syntax" rel="prev" title="Include Syntax">
  32. <style type="text/css">
  33. <!--
  34. a.summary-letter {text-decoration: none}
  35. blockquote.indentedblock {margin-right: 0em}
  36. blockquote.smallindentedblock {margin-right: 0em; font-size: smaller}
  37. blockquote.smallquotation {font-size: smaller}
  38. div.display {margin-left: 3.2em}
  39. div.example {margin-left: 3.2em}
  40. div.lisp {margin-left: 3.2em}
  41. div.smalldisplay {margin-left: 3.2em}
  42. div.smallexample {margin-left: 3.2em}
  43. div.smalllisp {margin-left: 3.2em}
  44. kbd {font-style: oblique}
  45. pre.display {font-family: inherit}
  46. pre.format {font-family: inherit}
  47. pre.menu-comment {font-family: serif}
  48. pre.menu-preformatted {font-family: serif}
  49. pre.smalldisplay {font-family: inherit; font-size: smaller}
  50. pre.smallexample {font-size: smaller}
  51. pre.smallformat {font-family: inherit; font-size: smaller}
  52. pre.smalllisp {font-size: smaller}
  53. span.nolinebreak {white-space: nowrap}
  54. span.roman {font-family: initial; font-weight: normal}
  55. span.sansserif {font-family: sans-serif; font-weight: normal}
  56. ul.no-bullet {list-style: none}
  57. -->
  58. </style>
  59. </head>
  60. <body lang="en">
  61. <a name="Include-Operation"></a>
  62. <div class="header">
  63. <p>
  64. Next: <a href="Search-Path.html#Search-Path" accesskey="n" rel="next">Search Path</a>, Previous: <a href="Include-Syntax.html#Include-Syntax" accesskey="p" rel="prev">Include Syntax</a>, Up: <a href="Header-Files.html#Header-Files" accesskey="u" rel="up">Header Files</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Index-of-Directives.html#Index-of-Directives" title="Index" rel="index">Index</a>]</p>
  65. </div>
  66. <hr>
  67. <a name="Include-Operation-1"></a>
  68. <h3 class="section">2.2 Include Operation</h3>
  69. <p>The &lsquo;<samp>#include</samp>&rsquo; directive works by directing the C preprocessor to
  70. scan the specified file as input before continuing with the rest of the
  71. current file. The output from the preprocessor contains the output
  72. already generated, followed by the output resulting from the included
  73. file, followed by the output that comes from the text after the
  74. &lsquo;<samp>#include</samp>&rsquo; directive. For example, if you have a header file
  75. <samp>header.h</samp> as follows,
  76. </p>
  77. <div class="smallexample">
  78. <pre class="smallexample">char *test (void);
  79. </pre></div>
  80. <p>and a main program called <samp>program.c</samp> that uses the header file,
  81. like this,
  82. </p>
  83. <div class="smallexample">
  84. <pre class="smallexample">int x;
  85. #include &quot;header.h&quot;
  86. int
  87. main (void)
  88. {
  89. puts (test ());
  90. }
  91. </pre></div>
  92. <p>the compiler will see the same token stream as it would if
  93. <samp>program.c</samp> read
  94. </p>
  95. <div class="smallexample">
  96. <pre class="smallexample">int x;
  97. char *test (void);
  98. int
  99. main (void)
  100. {
  101. puts (test ());
  102. }
  103. </pre></div>
  104. <p>Included files are not limited to declarations and macro definitions;
  105. those are merely the typical uses. Any fragment of a C program can be
  106. included from another file. The include file could even contain the
  107. beginning of a statement that is concluded in the containing file, or
  108. the end of a statement that was started in the including file. However,
  109. an included file must consist of complete tokens. Comments and string
  110. literals which have not been closed by the end of an included file are
  111. invalid. For error recovery, they are considered to end at the end of
  112. the file.
  113. </p>
  114. <p>To avoid confusion, it is best if header files contain only complete
  115. syntactic units&mdash;function declarations or definitions, type
  116. declarations, etc.
  117. </p>
  118. <p>The line following the &lsquo;<samp>#include</samp>&rsquo; directive is always treated as a
  119. separate line by the C preprocessor, even if the included file lacks a
  120. final newline.
  121. </p>
  122. <hr>
  123. <div class="header">
  124. <p>
  125. Next: <a href="Search-Path.html#Search-Path" accesskey="n" rel="next">Search Path</a>, Previous: <a href="Include-Syntax.html#Include-Syntax" accesskey="p" rel="prev">Include Syntax</a>, Up: <a href="Header-Files.html#Header-Files" accesskey="u" rel="up">Header Files</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Index-of-Directives.html#Index-of-Directives" title="Index" rel="index">Index</a>]</p>
  126. </div>
  127. </body>
  128. </html>