Markus Gritsch wrote:
> klaus.berndl@... wrote:
>> Markus Gritsch wrote:
>>> Jans, Hauke wrote:
>>>> ecb-tagdefinition.el - addition to find a tag in my complete
>>>> project. Currently it f=EDnds the tag only if the file is loaded.
>>>> Klaus suggested running a shell script for parsing all source
>>>> files, but this has two problems for me:
>>>> - It runs very long (for one directory out of 20 i
>>>> let it run for one hour and it did not complete)
>>> What language do you use? I am programming in C++ and for this
>>> language ebrowse is an excellent choice.
>> an excellent choice for what?
> For that what Jans asked for: "[...] to find a tag in my complete
>> parsing a code base but using the informations (the tags)
> > without ebrowse?
> No, using it with ebrowse to jump to definitions and declarations.
>> Or working completely with
>> ebrowse, i.e. doing what the name suggests, browsing the c++-code?
> No, using ebrowse just for tag finding and using ECB for the rest.
>> IMHO ebrowse has a very clumsy user-interaction and integrates not
>> really smart within emacs-working...but of course a matter ot
> I am not going over this again, I already agreed on that. However, I
> am not seeing ebrowse as a foe which must be eliminated, just to use
> CEDET features alone. I was also trying to get CEDET working for me
> to jump=20
> to tag definitions/declarations, but didn't succeed.
> Having all the files which belong to a project open in Emacs is not a
> choice for me, since the projects I have to work on consist of about
> 1000+ source files, and the script coming with CEDET which should
> generate the database didn't work for me.
> ebrowse works great, can parse quite sophisticate C++, and does this
Markus, how would you rate the parsing-power of ebrowse compared to
> a decent rate of about 100+ files per second, since the parser is
> written in C. So regenerating the BROWSE file is not a pain at all,
> even if I have to trigger it manually due to severe changes in the
> source files. Usually I don't need to do it manully since I have
> automated this process in a .bat file which runs every day at
>> What are the advantages of ebrowse compaired to cedet (and speedbar
>> or ECB)?
> The tag thing described above.
Well, i assume the tag-database ebrowse generates can be used also
by other tools too (i assume this database is not a binary format?!)...
Then we should write a semanticdb-backend for the ebrowse-tag-database
so we get a fast and well parsed c++-code-completion...
Sounds promising ;-)
> Kind regards,