Re: Jde-complete performance (PLEASE: someone add jde-usages to jde proper!)

On Tue, 2006-04-11 at 08:41 -0700, Suraj Acharya wrote:
> Hi Nascif,
> 
> CVS jde-usages has two exprimental features
> 
> 1)  an implementation of getClassInfo which uses the jde-usages data
> structures :
> (defalias 'jde-complete-invoke-get-class-info
> 'jde-usages-complete-invoke-get-class-info) 
> 
> 2) A slightly reworked jde-parse-eval-type-of which changes the order
> in which in tests for the type of the input. The main change is that
> it defers the expensive  call to jde-parse-get-qualified-name as long
> as possible if the suspected class name does not match the usual class
> name convention, eg "FooBarBaz". 
> (defalias 'jde-parse-eval-type-of 'jde-usages-parse-eval-type-of)
> 
> There are also some other functions that replace JDEE java code by
> using the jde-usages structures:
> 
> (defalias 'jde-parse-get-qualified-name
> 'jde-usages-parse-get-qualified-name) 
> (defalias 'jde-parse-class-exists 'jde-usages-parse-class-exists)
> 
> 
> These features are exprimental because I don't have any regression
> tests yet for them, and have not done any exhaustive tests to look for
> differences from the jde behaviour, however I use emacs with these
> features turned on and fix bugs as I find them, so they're quite
> stable and usable. 
> 

Can someone PLEASEf add jde-usage to the proper jde CVS tree? I think it
is THE killer plugin for jde, and it fills in some long long standing
missing features.

It currently just doesn't feel integrated enough, even if it's only for
the plugin menu entry that has to be traversed first.

As far as I remember, even the author of jde-xref says that jde-usages
does the job "better" by not needing any source code parsing and
generally being faster.

	jtl