Re: Re: Features brainstorming

Tor Norbye <[email protected]> Mon, 02 Feb 2004 12:09:10 -0800
Newsgroups gmane.comp.java.netbeans.modules.tasklist.devel
Message-ID <[email protected]>
On Feb 2, 2004, at 8:56 AM, Petr Kuzel wrote:
> Also compare currently provided solutions from user's point of view:
>   - delete unused variable (PMD)
>   - delete unused import (PMD)
>   - add import (javaparser)
>   - create method (javaparser)
>   - type cast (javaparser)
>   - identifier case errors (javaparser)
> you can see that most common suggestions come from non-PMD
> provider in spite of fact it could be provided by PMD. Simply
> actual implementation is irrelevant for most users. We need
> to identify crucial suggestions and provide their fast
> implementation.

One important distinction between the javaparser module and the pmd 
stuff is that pmd (and most refactoring tools) only operate on valid & 
compileable source.

The javaparser module on the other hand is doing string-tricks and 
looking at the (compileable) environment, which means it can offer 
suggestions even for invalid code. This makes it a bit different from 
solutions based on ASTs, like PMD.  The ideal would be to have the AST 
for the code where compilation fails; hopefully with JSR XXX (201? 
something like that, can't remember off hand) that will be feasible.

-- Tor