[an error occurred while processing this directive]

<center><h1> Preprocessor Directives<BR> 
             & Separate Compilation </h1></center>

<H3>#includes</H3>
<UL>
   <LI>Only #include the header files at the top of a .c file that are needed 
       by the code in that file.
   <LI>Since the header file you have created for your modular functions,
       (Let's call it foo.h) needs to be seen before the function definitions
       (found in foo.c) and also any calls to those functions (found in 
       proj?.c), the header file foo.h needs to be #included at the top of
       both the foo.c and the proj?.c files. 
   <LI><font color="red">Don't #include .c files.</font><BR>
       .c files are to be compiled separately from one another and then
       linked together at compile time.
   <LI><font color="red">Don't have #includes of any files 
within header files</font><BR>
       Since header files contain prototypes and never have any function 
       calls in them, it isn't necessary to have any #include directives 
       in a header file.  
</UL>
<H3>#defines</H3>
For purposes of information hiding, you should place the #defines of constants
<B><font color="red">only as "high" in the program as they need to be.
</font></B>
<UL>
   <LI>If a constant is used in only one .c file, then its #define should be 
       placed at the top of that file.  
   <LI>If a constant is used by 2 .c files, then you should place the #define 
       for that constant in the header file that gets #included in both of 
       those .c files.
</UL>

<center><font size=-1>Last modified - Saturday, 24-Sep-2005 10:55:58 EDT 
</font></center>
[an error occurred while processing this directive]
</body>
</html>