Default and value initialization of POD types in C++

by

Local variables with automatic storage duration are not being initialized automatically. Since using uninitialized variables produces undefined behavior, it is a good practice to explicitly initialize your variables even when it’s redundant.

About POD types that are being zero-initialized, C++03 standard 3.6.2 Initialization of non-local objects states:

§1 Objects with static storage duration (3.7.1) shall be zero-initialized (8.5) before any other initialization takes place. Zero-initialization and initialization with a constant expression are collectively called static initialization; all other initialization is dynamic initialization. Objects of POD types (3.9) with static storage duration initialized with constant expressions (5.19) shall be initialized before any dynamic initialization takes place.

So it’s guaranteed by standard that POD types with static storage duration (whatever their scope is) will be zero-initialized.

POD members of a class (without explicit initialization in a constructor)

This situation is described in 12.6.2 Initializing bases and members, that states (selected parts):

If a given nonstatic data member or base class is not named by a mem-initializer-id (including the case where there is no mem-initializer-list because the constructor has no ctor-initializer), then:

— If the entity is a nonstatic data member…, and the entity class is a non-POD class, the entity is default-initialized (8.5)…

— Otherwise, the entity is not initialized…

After the call to a constructor for class X has completed, if a member of X is neither specified in the constructor’s mem-initializers, nor default-initialized, nor value-initialized, nor given a value during execution of the body of the constructor, the member has indeterminate value.

Example:

class C
{
public:
    C(int x, int z) : x(x), z(z) { }
    int x, y, z;
};

int main(void)
{
    C* c = new C(1,3);
    std::cout << c->y; // value of y is undetermined !!!
}

More Related Contents:

  1. What is the easiest way to initialize a std::vector with hardcoded elements?
  2. Finding C++ static initialization order problems
  3. How to emulate C array initialization “int arr[] = { e1, e2, e3, … }” behaviour with std::array?
  4. static initialization order fiasco
  5. Why do I see strange values when I print uninitialized variables?
  6. C++11 allows in-class initialization of non-static and non-const members. What changed?
  7. How to initialise memory with new operator in C++?
  8. Object creation on the stack/heap?
  9. Using newly declared variable in initialization (int x = x+1)?
  10. C++11: Correct std::array initialization?
  11. Why are my struct’s members not properly initialised using `{}`? [duplicate]
  12. memset() or value initialization to zero out a struct?
  13. Are function static variables thread-safe in GCC?
  14. C++ where to initialize static const
  15. What are primitive types default-initialized to in C++?
  16. C++: Where to initialize variables in constructor [duplicate]
  17. What is dynamic initialization of object in c++?
  18. Initializing container of unique_ptrs from initializer list fails with GCC 4.7
  19. Value initialization and Non POD types
  20. Has the new C++11 member initialization feature at declaration made initialization lists obsolete?
  21. Different ways of initializing an object in c++
  22. Uses for anonymous namespaces in header files
  23. Member fields, order of construction
  24. Why must const members be initialized in the constructor initializer rather than in its body?
  25. What happens if a constructor throws an exception?
  26. How could comma separated initialization such as in Eigen be possibly implemented in C++?
  27. Fun with uninitialized variables and compiler (GCC)
  28. Is uninitialized data behavior well specified?
  29. C++ function called without object initialization
  30. C++ – value of uninitialized vector

Leave a Comment