AUTOSAR C++14 Rule A8-5-1

In an initialization list, the order of initialization shall be following: (1) virtual base classes in depth and left to right order of the inheritance graph, (2) direct base classes in left to right order of inheritance list, (3) non-static data members in the order they were declared in the class definition

Description

In an initialization list, the order of initialization shall be following: (1) virtual base classes in depth and left to right order of the inheritance graph, (2) direct base classes in left to right order of inheritance list, (3) non-static data members in the order they were declared in the class definition.

Troubleshooting

If you expect a rule violation but Polyspace^® does not report it, see Diagnose Why Coding Standard Violations Do Not Appear as Expected.

Check Information

Group: Declarators

Category: Required, Automated

PQL Name: std.autosar_cpp14.A8_5_1

Version History

Introduced in R2019a

R2023b: Member initialization using NSDMI taken into account

Starting in R2023b, Polyspace no longer reports a violation of this rule on classes that perform nonstatic data member initialization (NSDMI). For instance, consider the class A:

#include<string>

class A
{
public:
    explicit A(std::string& instr);

private:
    std::string str1;
    std::string str2;
    std::string str3{"Third String"};
};

A::A(std::string& inStr) : str1(inStr)   //Compliant
    , str2(inStr)
{
}

The data member A::str3 is initialized using the NSDMI. The constructor A::A() initializes the uninitialized variables in the correct order. Polyspace does not report a violation. Previously, Polyspace reported a violation on classes that used NSDMI to initialize one or more nonstatic data members.