Re: managing header files

Here's my take on headers.

A header for each C file is a good idea, but it should only contain the 
definitions of the functions in that C file.  Put datatypes in their own 
separate header.  Separate global variables as well, although it's 
preferable not to have any.

If header A needs a datatype defined in header B, A should #include B. 
You can then include headers in any order you like, and you will never 
need to include a header which is unrelated to the task at hand.  Do not 
include header B from a header A unless the definitions in header A 
require it.  If something in the C file which corresponds to header A 
needs header B you should include it from the C file.

Use "header guards" to solve the multiple inclusion problem.  Surround 
the content of your header in a preprocessor condition like this:

#ifndef _HEADERNAME_H_INCLUDED_
#define _HEADERNAME_H_INCLUDED_
..
..
..
#endif /* defined(_HEADERNAME_H_INCLUDED_) */

change the name _HEADERNAME_H_INCLUDED_ as appropriate for each header.
-- 
comp.lang.c.moderated - moderation address: clcm@[EMAIL PROTECTED]
 -- you must
have an appropriate newsgroups line in your header for your mail to be
seen,
or the newsgroup name in square brackets in the subject line.  Sorry.