You are here: CodeIdol.com > C++ > C++ Coding Standards: 101 Rules, Guidelines, and Best Practices > Avoid Initialization Dependencies Across Compilation Units

SAVE
Digg
del.icio.us
Technorati
reddit

C++ Coding Standards: 101 Rules, Guidelines, and Best Practices

Avoid initialization dependencies across compilation units

21. SummaryDiscussionReferences...

Summary

Keep (initialization) order: Namespace-level objects in different compilation units should never depend on each other for initialization, because their initialization order is undefined. Doing otherwise...

read more: Summary

Discussion

When you define two namespace-level objects in different compilation units, which object's constructor is called first is not defined. Often (but not always) your tools...

read more: Discussion

References

[Dewhurst03] §55 • [Gamma95] • [McConnell93] §5.• [Stroustrup00] §9.4.1, §10.4.9...

read more: References