On Sep 5, 2008, at 4:56 PM, Reinier Zwitserloot wrote:
> > One major, humongous, huge, enormous, incredible STUPID aspect of > FindBugs is that it works on class files. > > D'oh. > > Source-level static analysis means your error/warning is better > focused on the problematic AST Node, and its much easier to program > 'quick fixes' right in there. I'm still waiting for a rewrite of > findbugs that works on source and not class files. Until then, I > understand looking at findbugs, going: Neat, we should have something > like that! - and then not using it all and rewriting its features > instead. It's unfortunate that the various efforts happening to get > there aren't communicating. Another problem with classfile analysis is that some problems get optimized away by the compiler and so FindBugs can't report on them. That said, FindBugs intraprocedural and threading analysis is pretty sweet. 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 -~----------~----~----~----~------~----~------~--~---
