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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>> 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!

How do you include several config.h files?
In general, a C file starts with

#if defined(HAVE_CONFIG_H)
#  include "config.h"
#endif

This would never include more than one, I think.

Carsten


_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf


[Index of Archives]     [GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [Linux USB]     [Samba]

  Powered by Linux