HIS Code Metrics justification
显示 更早的评论
Hello,
does anyone know how to justify HIS findings in code?
I have tried:
/* polyspace<Custom:Language Scope:Not a defect:Justify with annotations> The code is difficult because it's highly optimized. */
/* polyspace<Custom Number of Called Functions:Not a defect:Justify with annotations> The amout of called functions is necessary due to readability and functionality */
/* polyspace<Custom VOCF:Not a defect:Justify with annotations> The amout of called functions is necessary due to readability and functionality */
But with no luck.
I know that normally I use the same format of comment with MISRA or RTE findings.
I am using polyspace check for C++ code.
采纳的回答
Anirban
2022-10-12
1 个投票
You have to use:
/* polyspace CODE-METRICS: VOCF [Not a defect:Low] The amount of called functions is necessary due to readability and functionality */
.
6 个评论
Svatopluk
2022-11-14
Hello, so i have tried but with no effect, any solution?
Anirban
2022-11-15
Did you place the comment beside the function name in the definition?
Here is an example that justifies the language scope for function f :
int g(int);
int f(int i) /* polyspace CODE-METRIC:VOCF [No action planned:Low] "The amount of called functions is necessary due to readability and functionality." */
{
if (i == 1)
return i;
else
return i * g(i-1);
}
Svatopluk
2022-11-15
The code metrics are either project, file or function metrics. See the various types of metrics here.
File metrics appear at the beginning of a file (and cannot be justified). Function metrics appear next to the function signature in the definition and should be justified there.
Svatopluk
2022-11-22
Anirban
2022-11-22
Correcting my previous answer: it seems file metrics cannot be justified. However, language scope and number of called functions are function metrics, not file metrics, and should be justifiable. For instance, you can try the example below and see that the language scope is justified:
int g(int);
int f(int i) /* polyspace CODE-METRIC:VOCF [No action planned:Low] "The amount of called functions is necessary due to readability and functionality." */
{
if (i == 1)
return i;
else
return i * g(i-1);
}
About the reason why language scope and number of called functions are coming at the beginning of the file instead of next to a function definiton, I am not sure. Please contact MathWorks Technical Support for more help with the problem: https://www.mathworks.com/support/contact_us.html
更多回答（0 个）
类别
在 帮助中心 和 File Exchange 中查找有关 Code Metrics 的更多信息
Translated by 
