🚀 go-pugleaf

In article <0a05qnw60.alamito@marketgraph.xs4all.nl> rvg@marketgraph.xs4all.nl writes:
>In <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
>
>Something somewhere is wrong. Having includes be included multiple times this 
>way would also mean that any #define's in the include file would be 
>forgotten. That will certainly NOT be the case.
>Other possibility: #ifndef is broke.

Nothing is broke, or wrong.  In the original post, the author was
expecting the ifndef (and other things) to live _across_ translation units
(.c files if you will) not the typical scenario of a .c that included a .h
which may or may not have already #include'd the same thing.

>Better: try #include-ing such a file, then do:
>#ifdef MOOSE
>#error Should get here
>#else
>#error What is going on here?
>#endif
>
>in your C/C++ source.
>
>Let me/us know the results.

As per above, this is not relevant to the "problem"
This is a good technique for people to know in general though.

- Greg
-- 
       Comeau Computing, 91-34 120th Street, Richmond Hill, NY, 11418-3214
               Producers of Comeau C++ 4.0 front-end pre-release
 ***WEB: http://www.comeaucomputing.com / Voice:718-945-0009 / Fax:718-441-2310
 Here:comeau@comeaucomputing.com / BIX:comeau or comeau@bix.com / CIS:72331,3421