On Feb 26, 2009, at 12:18 PM, Reinier Zwitserloot wrote:
> > Yes, findbugs works on class files right now, but there's no reason > why it couldn't work on source files. Some projects have tried > (arguscodewatch for example) and while they're mostly inactive at this > point, source-level scanning is better in many ways; you can have > quick fix suggestions and certain findbugs-esque things can only be > detected on the source level and no longer in the class level. > > So, perhaps not findbugs per se, but some sort of serious static > analysis tool, at least. PMD does a good bit of source code analysis, including some limited data flow analysis. As you say, compilation removes some things from the source code, so PMD can find a few things that a bytecode checker can't. What PMD doesn't do yet (if I recall correctly) is a complete type resolution, e.g., this reference to "List" is a java.util.List, not a com.mycompany.List. But the tools are in place for it to do that.... Yours, Tom --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
