From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Newsgroups: gmane.emacs.devel Subject: RE: What IDE features do we need? defaults!] Date: Tue, 22 Apr 2008 19:07:08 +0200 Message-ID: <84D8FEFE8D23E94E9C2A6F0C58EE07E33A8D3F@mucmail3.sdm.de> References: <87ve2ac2eo.fsf@jurta.org><20080422115216.GA2609@muc.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1208884107 10520 80.91.229.12 (22 Apr 2008 17:08:27 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 22 Apr 2008 17:08:27 +0000 (UTC) To: , , Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Apr 22 19:09:02 2008 connect(): Connection refused 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.50) id 1JoLyb-0002jM-3S for ged-emacs-devel@m.gmane.org; Tue, 22 Apr 2008 19:08:17 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JoLxu-0007UV-Qv for ged-emacs-devel@m.gmane.org; Tue, 22 Apr 2008 13:07:34 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JoLxf-0007Fd-RD for emacs-devel@gnu.org; Tue, 22 Apr 2008 13:07:19 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JoLxe-0007E5-8T for emacs-devel@gnu.org; Tue, 22 Apr 2008 13:07:19 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JoLxe-0007E0-0x for emacs-devel@gnu.org; Tue, 22 Apr 2008 13:07:18 -0400 Original-Received: from world2.sdm.de ([192.76.162.230]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1JoLxX-0002pt-MO; Tue, 22 Apr 2008 13:07:11 -0400 Original-Received: from mucns1 ([10.40.232.18] helo=mucns1.sdm.de) by world2.sdm.de with esmtp (MTA) id 1JoLxW-00022M-MK; Tue, 22 Apr 2008 19:07:10 +0200 Original-Received: from localhost ([127.0.0.1] helo=sdmmail1.sdm.de) by mucns1.sdm.de with esmtp (MTA) id 1JoLxW-00056p-E0; Tue, 22 Apr 2008 19:07:10 +0200 Original-Received: from mucmail3.sdm.de ([10.40.232.45]) by sdmmail1.sdm.de with Microsoft SMTPSVC(6.0.3790.1830); Tue, 22 Apr 2008 19:07:09 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message In-reply-to: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: What IDE features do we need? defaults!] Thread-Index: AcikfyjQl7eEZnpzQKi7qJ+g1+FNxQAG/LLg X-OriginalArrivalTime: 22 Apr 2008 17:07:09.0205 (UTC) FILETIME=[4C992450:01C8A49B] X-detected-kernel: by monty-python.gnu.org: 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:95789 Archived-At: joakim@verona.se wrote: > Eli Zaretskii writes: >=20 >> In addition, etags does not really grok C++ and Java style >> object-oriented languages, so it cannot, for example, let you >> complete on class members, or show signatures of class methods, >> whether in tooltips or elsewhere.=20 >>=20 >>> Improving etags this way would be more of a stop-gap than a >>> solution. It just isn't powerful enough for that sort of >>> proprietary environment.=20 >>=20 >> I don't see why not; could you explain? >>=20 >> OTOH, we could also base an Emacs solution on something like >> ID-Utils, but that would require to develop parsers for popular >> languages such as C++, Java, Python, etc. As yet another >> alternative, we could use Ebrowse, although it, too, needs some work >> to catch up with current C++ standards (from a few blatant bugs I >> recently uncovered in Ebrowse, I conclude that it is almost unused). >=20 > I think Cedet is the way to go, since it supports a common Emacs > interface to several different tag generating backends, some of which > are written entirely in elisp. I 100% second this - Eric (maintainer of CEDET) works really hard to make CEDET useable even with huge code-bases - AFAIK performance of CEDET has increased a lot....