Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!lll-winken!uunet!math.fu-berlin.de!unido!nixpbe!nixsin!koerber.sin@sni.de
From: koerber.sin@sni.de (Mathias Koerber)
Newsgroups: comp.lang.c
Subject: Re: include files -- help needed
Message-ID: <1966@nixsin.UUCP>
Date: 11 Jun 91 04:31:27 GMT
References: <1991Jun7.233854.11170@arcturus.uucp>
Sender: koerberm@nixsin.UUCP
Reply-To: koerber.sin@sni.de
Organization: Siemens Nixdorf Information Systems (Singapore) Pte Ltd
Lines: 22

In article <1991Jun7.233854.11170@arcturus.uucp> guthriew@arcturus.uucp (Guthrie;Wade) writes:
>
>In order to follow the guidelines of
>
>	1) no nested include files and
>	2) limiting the scope of globals and typedefs,

Why no nested include files? They are a *GOOD THING*, especially when one
include file automatically includes the definitions it references itself. On
pre-ansi compiler you must be a bit carefule about multiple inclusions though,
since not all headers have the

#ifndef THIS_IS_A_UNIQUE_DEFINE
#define THIS_IS_A_UNIQUE_DEFINE
...
#endif

code to skip the file when it was already included. Maybe you could add them
to your standard header files to make it even easier on the programmer. Just
be sure to pick unique_defines that are guaranteed to be really unique.

Mathias