On Feb 25, 5:58 pm, Reinier Zwitserloot <[email protected]> wrote: > need to start advocating the mandatory use of such tools, work on > getting findbugs integrated into javac,
A. Why would you want to integrate findbugs into javac? B. Mandatory use of tools wouldn't work too well. Yes, you can make tools that tell developers that they aren't perfect, euphemistically speaking, but if they are sufficiently capable with any programming language, they'll find a way to work around the litany of the mandatory tools, for example by logging it to /dev/null .. ;) In a galaxy far away, a long time ago, a compiler called jikes tried to do that - their last or so release basically made a -Wall mode the default one, and showered the users with pedantic warnings about the quality of their code. Unsurprisingly, faced with hundreds or thousands of warnings on code bases that compiled cleanly with other compilers, developers blamed the compiler, and turned the pedantic mode off, rather then spending their time fixing the issues the compiler complained about. Static analysis tools can tell you which of the code out there is below average quality - Freud can tell you that its developers likely don't want to know that, anyway. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
