🚀 go-pugleaf

If you inspect each of the system files, a unique symbol is usually
#defined in  each file which you can use in your own includes as follows:

#ifndef SYMBOL
   #include <filewithsymbol.h>
#endif



In article <gnusenetraub-2412960039190001@dialup52.afn.org>, Mauricio
Tavares <raub@kushana.aero.ufl.edu> wrote:

>         I am finding some very interesting behavior from #define and
> #ifndef/#ifdef.  Let's say that I have a header file called MyHeader.h.  This
> file is included by all my routines (they usually are in separate files).  Now
> that would not be very nice since it would include the very same include files
> (stdio.h and others) over and over again.  So, I thought if I use something
> like
> 
> #ifndef MOOSE
> #define MOOSE
> #include <stdio.h>
> #include <X11/Xlib.h>
> #endif
> 
> the code would only include *one* copy of these two include files.  What I am
> finding out is that is not the case.  Running C programs that have similar 
> conditional including of header files in gcc (Sparc), Think C (Mac), Borland
> TC++ 3.1 for Windows (PC), and SAS/C (Amiga) results in the same thing.  It
> really seems that the compiler simply *forgets* what was defined in the
> previous .c file and define them all over again.  As a result, my object files
> become unnecessarily large.  Yes, the executable seems to take care of that,
> but still I am using more disk space than I should.  I am open for suggestions
> as usual.
> 
> -- 
>  ===========================+=======================================
> | Mauricio Tavares          | "We will attack...                    |
> | raub@kushana.aero.ufl.edu |  ...under the cover of daylight!"     |
> |                           |                                Rimmer |
>  ===========================+=======================================