Why static variable needs to be explicitly defined?

by

From the beginning of time C++ language, just like C, was built on the principle of independent translation. Each translation unit is compiled by the compiler proper independently, without any knowledge of other translation units. The whole program only comes together later, at linking stage. Linking stage is the earliest stage at which the entire program is seen by linker (it is seen as collection of object files prepared by the compiler proper).

In order to support this principle of independent translation, each entity with external linkage has to be defined in one translation unit, and in only one translation unit. The user is responsible for distributing such entities between different translation units. It is considered a part of user intent, i.e. the user is supposed to decide which translation unit (and object file) will contain each definition.

The same applies to static members of the class. Static members of the class are entities with external linkage. The compiler expects you to define that entity in some translation unit. The whole purpose of this feature is to give you the opportunity to choose that translation unit. The compiler cannot choose it for you. It is, again, a part of your intent, something you have to tell the compiler.

This is no longer as critical as it used to be a while ago, since the language is now designed to deal with (and eliminate) large amount of identical definitions (templates, inline functions, etc.), but the One Definition Rule is still rooted in the principle of independent translation.

In addition to the above, in C++ language the point at which you define your variable will determine the order of its initialization with regard to other variables defined in the same translation unit. This is also a part of user intent, i.e. something the compiler cannot decide without your help.

Starting from C++17 you can declare your static members as inline. This eliminates the need for a separate definition. By declaring them in that fashion you effectively tell compiler that you don’t care where this member is physically defined and, consequently, don’t care about its initialization order.

More Related Contents:

  1. The static keyword and its various uses in C++
  2. Static constant string (class member)
  3. Why are global and static variables initialized to their default values?
  4. Why does a static data member need to be defined outside of the class?
  5. Why can’t I initialize non-const static member or static array in class?
  6. Defining static members in C++
  7. Defining static const integer members in class definition
  8. When are static C++ class members initialized?
  9. Static member initialization in a class template
  10. Prevent static initialization order “fiasco”, C++
  11. Static variables in member functions
  12. Static variables in C++
  13. When are static and global variables initialized?
  14. Are function static variables thread-safe in GCC?
  15. C++ where to initialize static const
  16. Template static variable
  17. Variable declarations in header files – static or not?
  18. How to initialize a static const member in C++?
  19. C++: When (and how) are C++ Global Static Constructors Called?
  20. What makes a static variable initialize only once?
  21. constexpr static member before/after C++17
  22. Are static fields inherited?
  23. Circular C++ Header Includes
  24. How do static variables in lambda function objects work?
  25. Advantages of classes with only static methods in C++
  26. Is C++ static member variable initialization thread-safe?
  27. Should one never use static inline function?
  28. Static global variables in C++
  29. On local and global static variables in C++
  30. C++, static vs. namespace vs. singleton

Leave a Comment