Yes, in Polyspace Bug Finder 2023b, there is a way to flag cases where a pointer parameter could be declared 'const' if it is not modified inside a function. This is supported through MISRA C:2023 Rule 8.13, which states that a pointer should point to a const-qualified type whenever possible.
To enable this check:
- Make sure your analysis is configured to use the MISRA C:2023 coding standard.
- Confirm that Rule 8.13 is active in your rule set. Polyspace will then analyze whether pointer parameters are used to modify the data they point to. If not, it will flag the parameter as a candidate for const qualification.
Please note that this rule is context-sensitive. For example, if a pointer parameter is copied and later modified indirectly, Polyspace may not report it. Additionally, this rule is designed to address coding-standard compliance rather than stylistic recommendations, so it will not enforce const propagation beyond what is explicitly defined in the selected standard.
If you are not using MISRA C:2023 or need broader enforcement, you could supplement Polyspace with external tools like Clang-Tidy or integrate const-qualification checks into your code review process.
For more details, refer to the official documentation:
- https://www.mathworks.com/help/bugfinder/ref/misrac2023rule8.13.html
- https://www.mathworks.com/help/bugfinder/check-reference.html
- https://www.mathworks.com/help/bugfinder/analysis-options.html
I hope this helps!
