Re[1]: [cedet-semantic] [ECB-list] practical ECB page on emacs wiki

[Eric M. L. <er...@si...>]

Hi Timo,

You are right that the intellisense stuff doesn't live up to the
expectations of anyone coming from Visual Studio or other environment,
but that doesn't mean it isn't a priority.

Good intellisense / tag jumping for a very large project basically
requires good parsing in a local context, that all the code is parsed,
and tags are stored in a fast database.  Currently the parsing is slow,
and the database really needs to be offloaded outside of Emacs.

Anyway, that is where the effort needs to go.  Solving those problems
will make solving intellisense specific problems worthwhile.

Eric

>>> Timothee Besset <tt...@id...> seems to think that:
>kla...@sd... wrote:
>> Hi Timothee,
>>
>> I forward your email to the cedet-list as well, because you mentioned
>> semantic too and you are right: probably for an end-user it isn't not always easy
>> to know which part (ecb, semantic) does what.
>>
>> But in general there is a simple rule: ALL (!!) parsing is done by semantic,
>> ECB is only the displayor for the parsing results.
>>
>> But i'm stll wondering what is so difficult for you to come up with a working
>> combination of ECB/cedet(semantic)??
>>
>> I would understand if you mean such topics like intellisense or navigating large
>> code-bases residing in a lot of different direktories because for these there are
>> still suboptimal solutions....
>>   
>Yes, exactly that.
>
>The C++ codebase I work with has around 1400 files in about a 100
>directories. That's not a really big codebase either, seems to me a lot
>of people have to deal with much larger stuff.
>
>The features I am looking for are indeed intellisense and navigating
>types. Pretty much all the things that are mentioned in the page:
>http://www.emacswiki.org/cgi-bin/wiki/WhatAreTheNeedsOfProgrammers
>
>Sometimes I feel that a lot the priorities of functionality work in IDE
>tools ( such as ECB and several others ) do not match what as an
>everyday user I consider most basic and essential. Visual Studio doesn't
>provide much code browsing functionality, but at least it has the basics
>working, which are autocomplete and easy navigation to
>definition/declaration.
>
>TTimo

-- 
          Eric Ludlam:                 za...@gn..., er...@si...
   Home: http://www.ludlam.net            Siege: www.siege-engine.com
Emacs: http://cedet.sourceforge.net               GNU: www.gnu.org