MISRA Discussion Forums

Full Version: Rule 15.5 and return statements as children of labels
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Rule 15.5 says:

Quote:When a return statement is used, it should be the final statement in the compound statement that forms the body of the function.

Consider the following example:

Code:
typedef unsigned uint32_t;
uint32_t ten(uint32_t var) {
    if (var == 10) {
       return 10;
    }
}

I think it is pretty clear that this violates Rule 15.5 as the return statement is a child statement of the body of the if, even though no other statements appear between the return statement and the end of the function. Is this correct?

What then about the following:

Code:
typedef unsigned uint32_t;
uint32_t ten() {
my_label:
    return 10;
}

The return statement is technically a child of the label statement so the "final statement in the compound statement that forms the body of the function" is a label statement according to the grammar of C. Is this intended to be a violation of Rule 15.5?
Both your examples are violations of rule 15.5.

The MISRA C Working Group will review the use of labeled return statements.
The compound statement that forms the body of the function refers to the outer { } braces of the function - not any inner compound statement.

Therefore, your first example violates R.15.5 - it also violates Mandatory R.17.4 as there is no return statement in the path when the condition is false.

In your second example, a labelled-statement is formed by an id followed by a statement - therefore, the use of a labelled return is not a violation or R.15.5