unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Andreas Röhler" <andreas.roehler@online.de>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: emacs-devel@gnu.org
Subject: Re: Why <config.h> and not "config.h" ?
Date: Wed, 28 Jul 2010 09:06:03 +0200	[thread overview]
Message-ID: <4C4FD6DB.7080901@online.de> (raw)
In-Reply-To: <87wrsgs5t3.fsf@telefonica.net>

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" ?
>
>
>
>    




  parent reply	other threads:[~2010-07-28  7:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-28  2:23 Why <config.h> and not "config.h" ? Óscar Fuentes
2010-07-28  2:30 ` Miles Bader
2010-07-28  3:25   ` Óscar Fuentes
2010-07-28  6:30     ` Jan Djärv
2010-07-28  6:46       ` Óscar Fuentes
2010-07-28  7:06         ` Jan Djärv
2010-07-28  7:35           ` Óscar Fuentes
2010-07-28  7:57             ` Jan Djärv
2010-07-28  8:04               ` immanuel litzroth
2010-07-28  8:19                 ` Jan Djärv
2010-07-28  9:38               ` Óscar Fuentes
2010-07-28 10:07               ` Óscar Fuentes
2010-07-28  8:29         ` Andreas Schwab
2010-07-28  8:59           ` Óscar Fuentes
2010-07-29 14:26   ` Stefan Monnier
2010-07-30  9:21     ` Stephen J. Turnbull
2010-07-30  9:55       ` Eli Zaretskii
2010-08-01  9:31         ` Stephen J. Turnbull
2010-07-28  7:06 ` Andreas Röhler [this message]
2010-07-28  7:10   ` Óscar Fuentes
2010-07-28  7:15 ` Yavor Doganov
2010-07-28  7:46   ` Óscar Fuentes
2010-07-28 19:50 ` Dan Nicolaescu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C4FD6DB.7080901@online.de \
    --to=andreas.roehler@online.de \
    --cc=emacs-devel@gnu.org \
    --cc=ofv@wanadoo.es \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).