🚀 go-pugleaf

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.

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.


--
Ruud van Gaal
MarketGraph Software & Images; Silicon Graphics, PC (DOS/Win95/NT) & Amiga
DoomShell 4.5: http://www.xs4all.nl/~jwkorver
DoomShell 5.0: 3D Game Alchemy for DOOM, DOOM II, Heretic and Hexen (book)

    /\
   /__\
   /  \   Datastructures for the computer-illiterate: the binary tree
  /____\
    ||