In addition to finally checking in the semanticdb find results with
Klaus' patch idea, I also made a change deep inside semanticdb that
can effect anyone writing a custom semanticdb back end.
All find methods now accept a new third argument which is a list of
The functional API also changed, but not as much. All
semanticdb-find functions accept a "PATH" argument which can be one
of many different things. A new thing it can be is a semanticdb find
This basically lets you stack semanticdb searches into compound
searches. The old way you did one semanticdb search, then you had to
strip the results and pass it down into a semantic-find call. This
new way keeps the tables associated with the tags so you never need
to load the files into memory to find out where the tag is and
everything is (theoretically) faster. Yay!
Anyway, more to come on the completion code using all this stuff.
Eric Ludlam: zappo@..., eric@...
Home: http://www.ludlam.net Siege: http://www.siege-engine.com
Emacs: http://cedet.sourceforge.net GNU: http://www.gnu.org