>
> Hi,
>
> this is probably a silly questions, but I'll take my chance: I was
> wondering if there's a preferred way to include the config.h file
> generated by autoconf (with the define settings)? I.e. is there any
> reason why
>
> #include <config.h>
>
> would be better than
I've seen it documented - but briefly, the reason is that bracketed includes
are more predictable (compilers differ on the search rules for quoted includes,
making them unsuited for porting programs that may be built with objects and
sources in different directories).
> #include "config.h"
>
> (or vice versa) for the "general case"?
>
> I couldn't find any mention of this in the docs, and I suspect that if
> this is an issue, it is a more suitable question to ask within the
> domain of automake use, as it has possible ramifications for the way
> $(top_builddir) is used in the include-directories list..?
>
> Regards,
> Morten
>
--
Thomas E. Dickey
[EMAIL PROTECTED]
http://www.clark.net/pub/dickey
