Order of Object Initialization Across Translation Units (101188)
The information in this article applies to:
- Microsoft C/C++ for MS-DOS 7.0
- Microsoft Visual C++ 1.0
- Microsoft Visual C++ 1.5
- Microsoft Visual C++ 2.0
- Microsoft Visual C++ 4.0
This article was previously published under Q101188 SUMMARY
The order of initialization of global objects is undefined across
translation units. For example, if your application consists of three
C++ modules and each module declares an object of xyz class, there is
no guarantee during program initialization which of these objects will
be constructed first.
In addition to not relying on the order of initialization, you should
not use one object's address in another object's initialization when
the two objects are contained in different translation units.
AT&T 2.1 does not define the order of initialization for global
objects across translation units. The order of initialization is
implementation-dependent.
| Modification Type: | Major | Last Reviewed: | 12/1/2003 |
|---|
| Keywords: | kbLangCPP KB101188 |
|---|
|