Re: reasons for having no inclusion guards in config.h

[John Calcote]

On 3/7/2010 11:53 AM, Bob Friesenhahn wrote:
> On Sun, 7 Mar 2010, Carsten Heinrici wrote:
> > but: if there is this golden rule to always have them included first,
> > there should be no harm if they would include inclusion guards.
> >
> > what am I missing here?
>
> There may be several config.h files, each of which has somewhat 
> different content.  Bing!

So what would be wrong with generating an include guard tag based on the 
name of the project?

For instance,

--------
#ifndef GRAPHICSMAGICK_CONFIG_H
#define GRAPHICSMAGICK_CONFIG_H

...

#endif
--------

John