#4 Add support for code checkers

[Nascif Abousalh Neto]

There are some tools out there for static code analysis
that could be integrated with flymake. Usually they
assume the code is syntatically correct, so they could be
executed as an optional second pass, if the first pass
(the compiler) returns no messages.

To give a specific example, check JLint for Java (http://
artho.com/jlint/).

It can detect many problems that I don't think Jikes can
detect, like synchronization related potential bugs. JLint
is, just like Jikes, very fast. So it would be a good
candidate for integration, unlike for example Java-based
code checkers (like PMD and CheckStyle) that would
impose a much bigger performance impact.

Regards,
Nascif

[jeremy_wickersheimer]

Four years later, this would still be very nice to have.

I think it should be quite simple to implement alternate programs, and or alternate output parsers.

For example the simple ability to define more than error / warning parsers would take care of this feature, then you could change the program that check the source by a script that runs the compiler first, then Jikes/Jlint.