Re: Why <config.h> and not "config.h" ?

[Óscar Fuentes]

Yavor Doganov <address@hidden> writes:

>> Emacs sources use the idiom
>> 
>> #include <config.h>
>
> The Autoconf manual recommends this practice.

Yes, for the very same reason Miles explained. Quoting from the manual:

"With the appropriate -I option, you can use ‘#include
<config.h>’. Actually, it's a good habit to use it, because in the rare
case when the source directory contains another config.h, the build
directory should be searched first."

I'll emphasize the phrase "With the appropriate -I option." Otherwise
having a config.h on the source directory in a out of tree build is
asking for trouble.