From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Josh Newsgroups: gmane.emacs.devel Subject: Re: Emacs contributions, C and Lisp Date: Wed, 26 Feb 2014 09:08:23 -0800 Message-ID: References: <20140216180712.236069f6@forcix.jorgenschaefer.de> <87wqgr4v18.fsf@yandex.ru> <53064BD0.7070009@yandex.ru> <87ha7tr5bo.fsf@fencepost.gnu.org> <87ppmhecd8.fsf@yandex.ru> <87y50z90pd.fsf@fencepost.gnu.org> <87txbn8r6x.fsf@fencepost.gnu.org> <8338j717oe.fsf@gnu.org> <87zjlf6tdx.fsf@fencepost.gnu.org> <83sir7yue7.fsf@gnu.org> <8761o3dlak.fsf@wanadoo.es> <83bnxuzyl4.fsf@gnu.org> <871tyqes5q.fsf@wanadoo.es> <87a9ddg7o8.fsf@engster.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=20cf3010e8637a092904f35242f8 X-Trace: ger.gmane.org 1393434546 458 80.91.229.3 (26 Feb 2014 17:09:06 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 26 Feb 2014 17:09:06 +0000 (UTC) To: =?ISO-8859-1?Q?=D3scar_Fuentes?= , emacs-devel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Feb 26 18:09:15 2014 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 1WIhyo-0003F0-PJ for ged-emacs-devel@m.gmane.org; Wed, 26 Feb 2014 18:09:10 +0100 Original-Received: from localhost ([::1]:41924 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WIhyo-0003qy-8u for ged-emacs-devel@m.gmane.org; Wed, 26 Feb 2014 12:09:10 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49458) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WIhyg-0003qg-IG for emacs-devel@gnu.org; Wed, 26 Feb 2014 12:09:07 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WIhyZ-0004uP-So for emacs-devel@gnu.org; Wed, 26 Feb 2014 12:09:02 -0500 Original-Received: from mail-yk0-f170.google.com ([209.85.160.170]:39482) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WIhyZ-0004uI-Mt for emacs-devel@gnu.org; Wed, 26 Feb 2014 12:08:55 -0500 Original-Received: by mail-yk0-f170.google.com with SMTP id 9so1298919ykp.1 for ; Wed, 26 Feb 2014 09:08:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:content-type; bh=wWBZAXOpiOcg3ZjK2wCC5HYcABX1aJudIvOcwZ9cYp0=; b=hL38/urguvqgktutmaXmkjL84ltoh5ZRd3OTIbVcScG8A78pcr+Ywsj5d5BruWGCtq vukTIQB1EV3OB9Ib8dYQO/LAws5E0VT5tMjhCZXhfrHE87nrobCrJ3narAPR5btHSriV rD9w0hbgWn9CwLTDaal1Za3lE+6DaQ1J3r8FgwITGTQMjSMqFKVGp99cFzCGOTPOo2Gv P6hFpAm0zG2UuymuWmTv4ru2HcTJ8vv/TQstEYBbVNdcp1yiSIDf/fe7p1hqb3zNHQJG 2yaXueOehOy6VrszZg9CPGm0tmSFzv2fWlrtkotbpHY4w3xrrGZWM7bAGwJb1EPM882+ ildA== X-Gm-Message-State: ALoCoQkzUhiifPCbKAypcbhU01YOLmUhmvrHyt8wSouOhLZJW0DKr7wsBU9vBNfDqaLGdDKOdWJO X-Received: by 10.236.94.103 with SMTP id m67mr8932985yhf.7.1393434534991; Wed, 26 Feb 2014 09:08:54 -0800 (PST) Original-Received: by 10.170.168.130 with HTTP; Wed, 26 Feb 2014 09:08:23 -0800 (PST) In-Reply-To: <87a9ddg7o8.fsf@engster.org> X-Google-Sender-Auth: j2l-A9WTpSiEfYWiIGEwhyA_5kk X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 209.85.160.170 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:169887 Archived-At: --20cf3010e8637a092904f35242f8 Content-Type: text/plain; charset=ISO-8859-1 On Wed, Feb 26, 2014 at 8:28 AM, David Engster wrote: > > One was already mentioned by Stephen Leake: refactoring. Actually, > > anything that requires semantic knowledge of the source code you are > > working on. You could ask for a listing of places dependent of word > > size, for instance, or highlight the places where certain idiom is used. > > CEDET will most probably never be able to refactor C++ code, aside from > very simple cases. There are very few IDEs out there which even try to > do that; from my experience, none of them do it 100% reliably (just > bring some meta template programming into the game and see what > happens). IMHO, "Refactoring C++" should not be in the job description. Though I haven't used it myself, presumably one of these IDEs is Eclipse CDT[0]. According to this article[1], CDT includes a full C/C++ parser that's under active development (item 4) as well as extensive support for static analysis (item 5) and refactoring (item 6). Perhaps there are technical or licensing-related issues (see also item 9 regarding LLVM and Clang) that would make it a bad fit for integrating with Emacs in some way, but otherwise it might be worth a look. The wiki is here[2]. [0] https://www.eclipse.org/cdt/ [1] http://www.eclipse.org/community/eclipse_newsletter/2013/october/article1.php [2] https://wiki.eclipse.org/CDT/ Josh --20cf3010e8637a092904f35242f8 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

= On Wed, Feb 26, 2014 at 8:28 AM, David Engster <deng@randomsample.de> wrote:
> One was already mentioned by Stephen = Leake: refactoring. Actually,
> anything that requires semantic knowledge of the source code you are > working on. You could ask for a listing of places dependent of word > size, for instance, or highlight the places where certain idiom is use= d.

CEDET will most probably never be able to refactor C= ++ code, aside from
very simple cases. There are very few IDEs out there which even try to
do that; from my experience, none of them do it 100% reliably (just
bring some meta template programming into the game and see what
happens). IMHO, "Refactoring C++" should = not be in the job description.

Though I haven't used it myself, presumably one of these ID= Es is
Eclipse CDT[0].= =A0According to this article[1], CDT includes a full
C/C++ parser that's under active development (item 4) as wel= l as
extensive support for static analysis (item 5) a= nd refactoring
(item 6). =A0Perhaps there a= re technical or licensing-related issues
(s= ee also item 9 regarding LLVM and Clang) that would make it a bad
fit for integrating with Emacs in some way, but = otherwise it might
be worth a look. =A0The = wiki is here[2].

[0] https://www.eclipse.org/cdt/
[1] http://www.eclipse.or= g/community/eclipse_newsletter/2013/october/article1.php
[2] ht= tps://wiki.eclipse.org/CDT/

<= div class=3D"gmail_extra">Josh

--20cf3010e8637a092904f35242f8--