Re: What IDE features do we need? defaults!]

[joakim@verona.se]

Eli Zaretskii <eliz@gnu.org> writes:

> 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.
>
>> 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.
>
> I don't see why not; could you explain?
>
> 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).

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.

>
-- 
Joakim Verona