lang/C/the.ansi.c.programming.language/notes.accompany.ansi.c/sx7l.html

   1 <!DOCTYPE HTML PUBLIC "-//W3O//DTD W3 HTML 2.0//EN">
   2 <!-- This collection of hypertext pages is Copyright 1995, 1996 by Steve Summit. -->
   3 <!-- This material may be freely redistributed and used -->
   4 <!-- but may not be republished or sold without permission. -->
   5 <html>
   6 <head>
   7 <link rev="owner" href="mailto:scs@eskimo.com">
   8 <link rev="made" href="mailto:scs@eskimo.com">
   9 <title>section 4.11.1: File Inclusion</title>
  10 <link href="sx7k.html" rev=precedes>
  11 <link href="sx7m.html" rel=precedes>
  12 <link href="sx7.html" rev=subdocument>
  13 </head>
  14 <body>
  15 <H2>section 4.11.1: File Inclusion</H2>
  16
  17 <p>The two syntaxes for <TT>#include</TT> lines can be used in various ways,
  18 but very simply speaking,
  19 <TT>""</TT> is for header files you've written,
  20 and <TT>&lt;&gt;</TT> is for headers which are provided for you
  21 (which someone else has written).
  22 </p><p>page 89
  23 </p><p>Deep sentences:
  24 <blockquote><TT>#include</TT> is the preferred way
  25 to tie the declarations together
  26 for a large program.
  27 It guarantees that all the source files will be supplied with
  28 the same definitions and variable declarations,
  29 and thus eliminates a particularly nasty kind of bug.
  30 Naturally,
  31 when an included file is changed,
  32 all files that depend on it must be recompiled.
  33 </blockquote>That's the story on <TT>#include</TT>, in a nutshell.
  34 </p><hr>
  35 <p>
  36 Read sequentially:
  37 <a href="sx7k.html" rev=precedes>prev</a>
  38 <a href="sx7m.html" rel=precedes>next</a>
  39 <a href="sx7.html" rev=subdocument>up</a>
  40 <a href="top.html">top</a>
  41 </p>
  42 <p>
  43 This page by <a href="http://www.eskimo.com/~scs/">Steve Summit</a>
  44 // <a href="copyright.html">Copyright</a> 1995, 1996
  45 // <a href="mailto:scs@eskimo.com">mail feedback</a>
  46 </p>
  47 </body>
  48 </html>