From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Paul Eggert Newsgroups: gmane.emacs.devel Subject: Re: Using " rather than < for header files in Emacs Date: Wed, 9 Mar 2016 00:19:41 -0800 Organization: UCLA Computer Science Department Message-ID: <56DFDC9D.9010007@cs.ucla.edu> References: <56D772EC.5070509@cs.ucla.edu> <87egbpdqb4.fsf@gnu.org> <56DB19B5.7040906@cs.ucla.edu> <87lh5tdl3l.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1457511621 21458 80.91.229.3 (9 Mar 2016 08:20:21 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 9 Mar 2016 08:20:21 +0000 (UTC) Cc: Wilfred Hughes , emacs-devel To: Mathieu Lirzin Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Mar 09 09:20:05 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1adZLg-0001Qc-Rq for ged-emacs-devel@m.gmane.org; Wed, 09 Mar 2016 09:20:04 +0100 Original-Received: from localhost ([::1]:39825 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1adZLc-0002gU-OU for ged-emacs-devel@m.gmane.org; Wed, 09 Mar 2016 03:20:00 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60107) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1adZLO-0002gF-P7 for emacs-devel@gnu.org; Wed, 09 Mar 2016 03:19:47 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1adZLL-0003aZ-Hv for emacs-devel@gnu.org; Wed, 09 Mar 2016 03:19:46 -0500 Original-Received: from zimbra.cs.ucla.edu ([131.179.128.68]:51120) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1adZLL-0003aN-CA; Wed, 09 Mar 2016 03:19:43 -0500 Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 8F455160E8A; Wed, 9 Mar 2016 00:19:42 -0800 (PST) Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id SinDHYOomzW8; Wed, 9 Mar 2016 00:19:41 -0800 (PST) Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id D9932160E8D; Wed, 9 Mar 2016 00:19:41 -0800 (PST) X-Virus-Scanned: amavisd-new at zimbra.cs.ucla.edu Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id OOx-jn__-oDQ; Wed, 9 Mar 2016 00:19:41 -0800 (PST) Original-Received: from [192.168.1.9] (pool-100-32-155-148.lsanca.fios.verizon.net [100.32.155.148]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id B68E9160E8A; Wed, 9 Mar 2016 00:19:41 -0800 (PST) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 In-Reply-To: <87lh5tdl3l.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 131.179.128.68 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:201234 Archived-At: Mathieu Lirzin wrote: >> >In theory, the "..." form could lead to including the wrong file. In >> >practice, the way Emacs does it is harmless, but why add risk by using >> >"..." more often? > Could you give a concrete example of a possible include problem using > "..."? It would help me understand the issue. Well, as I said I doubt whether Emacs has the problem, but it could be something like this: a/x.h: #include "y.h" b/z.h: #include b/y.h: int foo; c/y.h: char foo; c/f.c: #include cd c; cc -I../a -I../b f.c With GNU, 'foo' is of type 'int'. With Microsoft C, it sounds like 'foo' is of type 'char'. I don't use Microsoft C so this example is untested there and may not be quite right, but I hope it gives you the idea.