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

[Andreas Röhler]

Am 28.07.2010 04:23, schrieb Óscar Fuentes:
> Emacs sources use the idiom
>
> #include<config.h>
>
> Is there a specific reason for this? Usually the curly braces

Hi,

just a language question, not to get non-native english speakers -as you 
and me :-) bewildered.
Does "<...>" really mean curly?

IMHO these "{...}" are curly...

Do I misunderstand something?

Best regards,

Andreas

--
https://code.launchpad.net/~a-roehler/python-mode
https://code.launchpad.net/s-x-emacs-werkstatt/




>   are for
> headers that live outside the project. Some code analysis tools assume
> that. And some compilers (including gcc, AFAIK) use a different
> procedure for locating headers surrounded by curly braces, which may
> produce unexpected results for headers included from config.h.
>
> Any objections to replacing<config.h>  and<epaths.h>  with "config.h"
> and "epaths.h" ?
>
>
>
>