phoedos/pmd
1
1
Fork 1
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Udpated How it works page

Browse Source
This commit is contained in:
JosephAllen
2016-09-10 17:13:43 -04:00
parent b2a3725a8f
commit 423e032a86
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
pages/customizing/how_pmd_works.md
View File

@@ -17,13 +17,13 @@ folder: mydoc
PMD checks source code against rules and produces a report. Like this:
* Something passes a file name and a RuleSet into PMD
* PMD hands an InputStream to the file off to a JavaCC-generated parser
* PMD gets a reference to an Abstract Syntax Tree back from the parser
* Something passes a file name and a RuleSet into PMD.
* PMD hands an InputStream to the file to a JavaCC-generated parser.
* PMD gets a reference to an Abstract Syntax Tree back from the parser.
* PMD hands the AST off to the symbol table layer which builds scopes, finds declarations, and find usages.
* If any rules need data flow analysis, PMD hands the AST over to the DFA layer for building control flow graphs and data flow nodes.
* Each Rule in the RuleSet gets to traverse the AST and check for problems. The rules can also poke around the symbol table and DFA nodes.
* The Report is now filled with RuleViolations, and those get printed out in XML or HTML or whatever
* The Report is now filled with RuleViolations, and those get printed out in XML or HTML or whatever.
Not much detail here… if you think this document can be improved, please post [here](http://sourceforge.net/p/pmd/discussion/188192) and let us know how. Thanks!