Which static analysis tool for Java is easiest to extend? -


Which stable analysis tool for Java is the easiest extension mechanism I tested but the process of writing custom rules is very much involved. Specifically, I want to know if there is any device that provides syntax like Pahaluganj to choose interesting areas of code? I know about Aspecze, but it seems like this can do.

I got a related question:

Static analysis tool for Java recommended?

Many devices are listed in the answer but I want to know which option is the easiest option to write custom rules.

Edit: So far, the PMP's Express Expeditions by Gilum seems to be the closest to me, what I see. I'm looking for it soon. The real problem "static analysis" is a comprehensive subject that is "expansion" of a static analysis tool. You usually need a lot of machinery to do this: parsing, tree building, control flow graph extraction, data flow extraction, numeral analysis, interprocalaral analysis, range analysis, and on the list, to analyze the programs. Co. See tons of plywood literature.

You can use the pattern matching of the surface syntax to focus the tool on some program code, but you still have to explain the device that you want to "statically analyze" at that point. (And some analysts [like points-to-you] need to analyze first, and then select the part you want.)

Ethical : Easy to use arbitrary trust Tool for removing you should basically decide what kind of analysis you are pre-cautioned (stained inputs? Subscript range investigation? API abuse?) And find the device that already supports that thing At least your "extension" has an opportunity to be simple on the basis of what is already in the possession of the equipment.

Our DMS Software Renewing Toolkit is an attempt to refine the cost of building all types of analysis; machinery is applied across multiple applications and languges, for different degrees for C, C ++, Java and COBOL To provide analysis, control / dataflow analysis and points-analysis. And in order to help "point" you have the surface-syntax pattern.


Comments