Rule: DataflowAnomalyAnalysis
PMD makes the assumption that the analysed code is compilable. At the time DataflowAnomalyAnalysisRule was introduced, this was probably not the case, so it made sense to check for UR anomalies. However that assumption is now strongly relied upon by many parts of PMD, including the symbol table and many rules. Since no java compiler would let an undefined variable be referenced, we can assume that any reported UR anomaly is a false positive, and hence why the rule should stop checking for them.
abcfy2, l0s, wuwen5 and LeonieXU
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4