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.

Answer 1

[Anirban]

You have to use:

/* polyspace CODE-METRICS: VOCF [Not a defect:Low] The amount of called functions is necessary due to readability and functionality */

For more information, see Annotate Code and Hide Known or Acceptable Results.

.

[Svatopluk]

Hello, so i have tried but with no effect, any solution?

[Anirban]

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]

Well the finding is for line 0 of the code, lots of the errors are detected at the 1st line. In that case is hard to tell where it should be justified.

[Anirban]

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]

Thanks, do you have any example? From 15th i am trying to justify file metrics, on the 1st line, with the string format is you have suggested, but with no luck ( Language Scope, anf number of called functions)

[Anirban]

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