On Fri, Jun 17, 2011 at 6:29 AM, Paul Eggert <egg...@cs.ucla.edu> wrote: > On 06/16/11 10:36, Alfred M. Szmidt wrote: >> I'm thinking that maybe <config.h> should be generated with a double >> inclusion guard > > But the general rule is that <config.h> must always be included first, no? > So there shouldn't ever be a possibility of including it twice. > > It might be better to have config.h do something like this: > > #ifdef CONFIG_H > # error "config.h included twice" > #endif > #define CONFIG_H
Warning: Quite a few misbehaving packages actually install their config.h. -- Jack
