From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dan Nicolaescu Newsgroups: gmane.emacs.devel Subject: Re: Why and not "config.h" ? Date: Wed, 28 Jul 2010 15:50:13 -0400 Message-ID: References: <87wrsgs5t3.fsf@telefonica.net> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1280346803 9898 80.91.229.12 (28 Jul 2010 19:53:23 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 28 Jul 2010 19:53:23 +0000 (UTC) Cc: emacs-devel@gnu.org To: =?iso-8859-1?Q?=D3scar?= Fuentes Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jul 28 21:53:19 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1OeCgk-0001Hp-5N for ged-emacs-devel@m.gmane.org; Wed, 28 Jul 2010 21:53:14 +0200 Original-Received: from localhost ([127.0.0.1]:48656 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OeCdv-0003ZY-OJ for ged-emacs-devel@m.gmane.org; Wed, 28 Jul 2010 15:50:19 -0400 Original-Received: from [199.232.76.173] (port=45326 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OeCdr-0003ZQ-BF for emacs-devel@gnu.org; Wed, 28 Jul 2010 15:50:15 -0400 Original-Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1OeCdq-00033F-CE for emacs-devel@gnu.org; Wed, 28 Jul 2010 15:50:15 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]:39535) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1OeCdq-00033B-5V for emacs-devel@gnu.org; Wed, 28 Jul 2010 15:50:14 -0400 Original-Received: from dann by fencepost.gnu.org with local (Exim 4.69) (envelope-from ) id 1OeCdp-0006qf-FI; Wed, 28 Jul 2010 15:50:13 -0400 Mail-Followup-To: emacs-devel@gnu.org In-Reply-To: <87wrsgs5t3.fsf@telefonica.net> (=?iso-8859-1?Q?=22=D3scar?= Fuentes"'s message of "Wed\, 28 Jul 2010 04\:23\:20 +0200") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:127942 Archived-At: =D3scar Fuentes writes: > Emacs sources use the idiom > > #include > > Is there a specific reason for this? Usually the curly braces 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 and with "config.h" > and "epaths.h" ? Given that this is for your own needs, it seems that this is a change that you can make in your local tree. The code in question is very unlikely to change otherwise, so you can always safely stash it/unstash it