From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Rusi Newsgroups: gmane.emacs.help Subject: Re: A guide on setting up C/C++ development environment for Emacs Date: Fri, 29 Aug 2014 06:15:02 -0700 (PDT) Message-ID: <62df7bb1-f9d4-46f8-8037-cfefe3ac1c9f@googlegroups.com> 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; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1409318134 20080 80.91.229.3 (29 Aug 2014 13:15:34 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 29 Aug 2014 13:15:34 +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 15:15:27 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 1XNM1U-0000rx-QR for geh-help-gnu-emacs@m.gmane.org; Fri, 29 Aug 2014 15:15:24 +0200 Original-Received: from localhost ([::1]:42004 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XNM1U-0001O1-7m for geh-help-gnu-emacs@m.gmane.org; Fri, 29 Aug 2014 09:15:24 -0400 X-Received: by 10.182.166.73 with SMTP id ze9mr5808592obb.4.1409318103530; Fri, 29 Aug 2014 06:15:03 -0700 (PDT) X-Received: by 10.50.153.77 with SMTP id ve13mr86146igb.16.1409318103377; Fri, 29 Aug 2014 06:15:03 -0700 (PDT) Original-Path: usenet.stanford.edu!r2no9910599igi.0!news-out.google.com!ef6ni0igb.0!nntp.google.com!r2no9910568igi.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=59.95.22.176; posting-account=mBpa7woAAAAGLEWUUKpmbxm-Quu5D8ui Original-NNTP-Posting-Host: 59.95.22.176 User-Agent: G2/1.0 Injection-Date: Fri, 29 Aug 2014 13:15:03 +0000 Original-Xref: usenet.stanford.edu gnu.emacs.help:207231 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:99506 Archived-At: On Friday, August 29, 2014 11:36:35 AM UTC+5:30, David Engster wrote: > =EF=BF=BDscar Fuentes writes: > > However, I don't see CEDET's team throwing away their Elisp parser and > > 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. > Stop this, =EF=BF=BDscar. I think you're very well aware that the clang b= inary > in itself only provides smart completions, nothing more. I *have* added > support for this in CEDET. I'm pretty sure you know that as well, > because I've already written this to you the last time this was > discussed. > What you are talking about is walking the AST using libclang/libtooling, > which is a whole different matter and nothing which one does "right > away". Just look at projects like rtags which do that, and see what it > entails. rtags looks interesting. Ive been thinking for a long time... Once things like dbus stabilize, its only a question of time before=20 the optimal solution is to parcel off code analysis to the right source rather than emacs running in a (hopeless) catching up game of trying to do as well as the language system itself. So "what it entails" ?? What are the issues? The one question I have straight off is "Is it generic?" ie can rtags carry over to haskell/python etc? [Of course assuming that the corresponding server for haskell/python etc code analysis exist/can be written]