From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.help Subject: Re: A guide on setting up C/C++ development environment for Emacs Date: Fri, 29 Aug 2014 02:02:54 +0200 Message-ID: <87ha0w6u35.fsf@wanadoo.es> References: <513ad0e2-f7f4-484c-b17b-7c94a8c2fc7a@googlegroups.com> <8738chaieo.fsf@wanadoo.es> <87tx4x9353.fsf@wanadoo.es> <87ppfl91ft.fsf@wanadoo.es> <87lhq98zoy.fsf@wanadoo.es> <87ha0x8xbh.fsf@wanadoo.es> <47129814-f079-4441-be39-9387912bca3a@googlegroups.com> <87ppfk71ip.fsf@wanadoo.es> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1409270622 26221 80.91.229.3 (29 Aug 2014 00:03:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 29 Aug 2014 00:03:42 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Fri Aug 29 02:03:35 2014 Return-path: Envelope-to: geh-help-gnu-emacs@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 1XN9fD-0004MT-0g for geh-help-gnu-emacs@m.gmane.org; Fri, 29 Aug 2014 02:03:35 +0200 Original-Received: from localhost ([::1]:39488 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XN9fC-0004Ax-LD for geh-help-gnu-emacs@m.gmane.org; Thu, 28 Aug 2014 20:03:34 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57462) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XN9ev-0004Ad-GU for help-gnu-emacs@gnu.org; Thu, 28 Aug 2014 20:03:23 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XN9ep-0007wZ-K5 for help-gnu-emacs@gnu.org; Thu, 28 Aug 2014 20:03:17 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:58237) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XN9ep-0007wT-Dp for help-gnu-emacs@gnu.org; Thu, 28 Aug 2014 20:03:11 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XN9en-0003yr-JN for help-gnu-emacs@gnu.org; Fri, 29 Aug 2014 02:03:09 +0200 Original-Received: from 18.red-83-41-63.dynamicip.rima-tde.net ([83.41.63.18]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 29 Aug 2014 02:03:09 +0200 Original-Received: from ofv by 18.red-83-41-63.dynamicip.rima-tde.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 29 Aug 2014 02:03:09 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 29 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 18.red-83-41-63.dynamicip.rima-tde.net User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4.50 (gnu/linux) Cancel-Lock: sha1:t63Ksi+dEV0lXlklwVJgPEAmpuI= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:99491 Archived-At: Stefan Monnier writes: >> start coding one on C/C++. They could use Clang's right away, or GCC's >> once the modularization is completed, but they insist on their own's. > > Actually, no, they don't insist on their own. Well, if there exists one current plus another near-future solutions which are vastly superior to their own parser, but they plan to continue working on it, then yes, they are insisting on using their own parser. > CEDET's infrastructure is > designed so you can use external tools. The C/C++ support is not simply > replaced by Clang's support because many people don't use Clang What means "don't use Clang"? Is there some principled (cough!) stance that forbids them from using Clang? > (and because it predates Clang, IIUC). This is not a reason for keeping with it, moreover as CEDET's architecture (the one you refer to above) makes it easy to replace the default parser. > Also, AFAIK noone has written the CEDET binding to Clang yet, See Dmitry's response to this. [snip]