C++核心准则​讨论：按照成员声明的顺序定义和初始化成员变量

Discussion: Define and initialize member variables in the order of member declaration

讨论：按照成员声明的顺序定义和初始化成员变量

Member variables are always initialized in the order they are declared in the class definition, so write them in that order in the constructor initialization list. Writing them in a different order just makes the code confusing because it won't run in the order you see, and that can make it hard to see order-dependent bugs.

成员变量总是按照它们在类定义中声明的顺序进行初始化，因此请按该顺序将其写入构造函数初始化列表中。以不同的顺序编写它们只会使代码令人困惑，因为它不会按照您看到的顺序运行，并且这使得很难看到与顺序相关的错误。

class Employee {
    string email, first, last;
public:
    Employee(const char* firstName, const char* lastName);
    // ...
};

Employee::Employee(const char* firstName, const char* lastName)
  : first(firstName),
    last(lastName),
    // BAD: first and last not yet constructed
    email(first + "." + last + "@acme.com")
{}

In this example, email will be constructed before first and last because it is declared first. That means its constructor will attempt to use first and last too soon -- not just before they are set to the desired values, but before they are constructed at all.

在此示例中，由于email对象首先被声明，所以将在first和last之前进行构造。这意味着它的构造函数试图过早使用first和last-不仅早于将它们设置为所需值之前，甚至会遭遇对象完全构造之前。

If the class definition and the constructor body are in separate files, the long-distance influence that the order of member variable declarations has over the constructor's correctness will be even harder to spot.

如果类定义和构造函数体位于不同的文件中，则成员变量声明的顺序对构造函数正确性的远程影响将更加难以发现。

References（参考）:

[Cline99] §22.03-11, [Dewhurst03] §52-53, [Koenig97] §4, [Lakos96] §10.3.5, [Meyers97] §13, [Murray93] §2.1.3, [Sutter00] §47

原文链接

https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#discussion-define-and-initialize-member-variables-in-the-order-of-member-declaration