Details
-
Type:
New Feature
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 3.12, Backlog: Thales, Backlog of rules: Cppcheck
-
Labels:
Description
Approach : by using a collection of all declared private functions and a collection of all used functions
The steps are the following ones :
- Each time a private function declaration is encountered, add a this element to a collection A
- Based on the AST, each time a function is used, add this function name to a collection B
- At the end of this analysis, find all the function names which are in A but not in B -> log an issue on those private function declarations
Potential limite of this approach : the size of of the collection B might be important on big projects (to be checked)
Attachments
Issue Links
- depends upon
-
CPP-1497 AST visitor API should provide the ability to log issues issues at the end of the project analysis
-
- Closed
-
-
CPP-760 Report issues in project's header files, when build-wrapper is used
-
- Closed
-
- implements
-
RSPEC-1144 Unused "private" methods should be removed
- Active
- is depended upon by
-
CPP-1120 Remove support of Cppcheck
-
- Closed
-
- is related to
-
CPP-1507 Fix false-positives in UnusedPrivateMethodCheck S1144 for function typedef
-
- Closed
-
-
CPP-1209 Rule: Unused private fields should be removed
-
- Closed
-
-
SUPPORT-2365 Loading...