Destruction order of static objects in C++

by

The static objects are destructed in the reverse order of construction. And the order of construction is very hard to control. The only thing you can be sure of is that two objects defined in the same compilation unit will be constructed in the order of definition. Anything else is more or less random.

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. C++ static virtual members?
  11. Prevent static initialization order “fiasco”, C++
  12. Static variables in member functions
  13. Static variables in C++
  14. How do you create a static class in C++?
  15. Does there exist a static_warning?
  16. Are function static variables thread-safe in GCC?
  17. C++ where to initialize static const
  18. Template static variable
  19. Variable declarations in header files – static or not?
  20. C++: When (and how) are C++ Global Static Constructors Called?
  21. What makes a static variable initialize only once?
  22. Circular C++ Header Includes
  23. static vs non-static variables in namespace
  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. Member function with static linkage
  28. How to execute a piece of code only once?
  29. Why is a C++ bool var true by default?
  30. How to ignore false positive memory leaks from _CrtDumpMemoryLeaks?

Leave a Comment