[CEDET-devel] notes on ebrowse support for cedet
Brought to you by:
zappo
From: <jo...@ve...> - 2006-07-19 20:54:45
|
I've been spending some time on trying to implement ebrowse supot for cedet. If I'd gotten very far, I'd cal this mail a "progres report" rather than "notes" :) I have spent most of my time just trying to understand eieio, ebrowse, and the semanticdb. So far I've figured out this: - I think the code in the semanticdb-ebrowse skeleton doesnt realy work. Creating the ebrowse structure works, using ebrowse-read. The "splitting" that is called "stripping" in the code, seems to assume there is only 1 class per file. Also, there is code to retrieve the ebrowse equivalent of a "table", but that is just a stub. I've tried to implement something that works like this: - read the ebrowse structure - for each class tree, figure out the corresponding declaration file and put it on an assoc list for that file(this is nearly the same idea as the existing code) Currently this code doesnt work well, but it doesnt seem so hard anymore. Then there are problems when searching the ebrose structures. The existing ebrowse api seems geared towards just jumping to the declarator of a tag, not returning info about it. Currently I think one has to recurse the tree linearly to find a tag, which feels suboptimal. Then there are some problems converting the match to a semantic tag, because the ebrowse tag only seems to contain a single point, not the start and end of a declaration. It almost seems beter to just convert the ebrowse trees to something more like semantics internal structures directly when reading. I dont think I've figured out something that wasnt already known, I just felt like telling how the experiment went. -- Joakim Verona http://www.verona.se |