Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!mips!zaphod.mps.ohio-state.edu!samsung!rex!uflorida!kluge!serss0!id8rld06
From: id8rld06@serss0.fiu.edu (Michael Johnston)
Newsgroups: comp.lang.c
Subject: Re: A question on C programming style
Message-ID: <3345@kluge.fiu.edu>
Date: 16 Apr 91 00:06:06 GMT
References: <1991Apr12.103621.8907@umiami.ir.miami.edu>
Sender: news@kluge.fiu.edu
Organization: Florida International University, Miami
Lines: 28

In responce to the question of whether to use nested includes:

I use nested includes. At the very top of each include is a comment
identifying the file. Following that is something like:

#ifndef MODULE_NAME
#define MODULE_NAME

#include ...

[the rest of the include file goes here]

#endif

This way, any include file necessary is right there. Now, anyone using
this module only needs to know what it does and not how it does it. It
is one less place to make a mistake in the future.
    If you choose to not nest include files, make sure you document
what each file needs. AND DOCUMENT IT WELL!!

Mike


--
====================================================================
Michael Johnston
id8rld06@serss0.fiu.edu or
26793271x@servax.fiu.edu