I wonder how hard it would be to adapt the gcc plugin so that it can
output static analysis information for java (gcj) also.
Of course Dehydra is much less required in that context, obviously the
java Eclipse editor has a level of analyses of the java code that is
quite up to part with what dehydra produces.
I was thinking about it for DXR, if some of your project code is in
java, you'd want to be able to index it on the same DXR front-end, so it
would be convenient to use the same tool chain, compiling the java with
gcj.
Maybe they are also cases where after having developed some js analysis
script, you want to run the same/similar analysis on the java part of
your code, and not port it to completely different tool chain.
But maybe also what makes the most sense in terms of development effort
is for DXR to use the required equivalent tools from the Eclipse
project, and convert their output to something it can understand.
_______________________________________________
dev-static-analysis mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-static-analysis
