Paul Eggert <[EMAIL PROTECTED]> writes:
> Simon Josefsson <[EMAIL PROTECTED]> writes:
>
>> Hm, what about modules that use #if constructs in the Include:
>> statement? E.g. mbchar:
>>
>> Include:
>> #if HAVE_WCHAR_H
>> #include "mbchar.h"
>> #endif
>
> Good point.
>
> In that case, perhaps we sho
Simon Josefsson <[EMAIL PROTECTED]> writes:
> Hm, what about modules that use #if constructs in the Include:
> statement? E.g. mbchar:
>
> Include:
> #if HAVE_WCHAR_H
> #include "mbchar.h"
> #endif
Good point.
In that case, perhaps we should be putting "#include" in, consistently?
Paul Eggert <[EMAIL PROTECTED]> writes:
> Is there any rule for whether the Include: sections' lines should
> start with '#include'?
>
> I noticed 34 instances with #include and 276 without, so would it be OK
> to remove the "#include" from those 34 instances, for consistency?
> Here they are:
...
Bruno Haible <[EMAIL PROTECTED]> writes:
> 2007-01-01 Bruno Haible <[EMAIL PROTECTED]>
>
> * modules/settime (Include): Require timespec.h.
> * modules/nanosleep (Include): Likewise.
Thanks, I installed it.
One thing, though:
> Include:
> + #include "timespec.h"
> ...
> Includ
