If I define a local variable instance of a class halfway down my function without using a pointer and new, does the constructor get called on entering the function or where it is defined?
If I define another instance of a class globally within the file does that constructor get called when executable is first loaded? What if multiple threads are accessing the .dll?
Finally is you answer going to be the same in .dll, .so, .exe and linux executables?
If I define a local variable instance of a class halfway down my function without using a pointer and new, does the constructor get called o entering the function or where it is defined?
When it is defined.
If I define another instance of a class globally within the file does that constructor get called when executable is first loaded?
Yes.
What if multiple threads are accessing the .dll?
DLLs usually only get loaded once for the whole application – in fact, DLLs also have an entry point which is called by your application's threads but global variable initialization happens before that and only once.
If I define a local variable instance of a class halfway down my function without using a pointer and new, does the constructor get called on entering the function or where it is defined?
Such variables have local scope. Their constructor is called when they're defined. For local statics, the constructor is only called once, since the statics will survive multiple function calls and returns. The order is important, and is the order of definition:
void foo() {
....
if(cond) {
...
// called here: first for f, then for b
static Foo f;
static Bar b;
}
...
Foo f; // not static: called here, in every invocation of foo.
}
If I define another instance of a class globally within the file does that constructor get called when executable is first loaded?
Yes, such variable is said to have static storage duration, and namespace scope. Its constructor is called at program start. The order is the order it is defined in the file. That is, a variable defined later will have its ctor called later. The order in which variables defined in different translation units is not defined (look-out for the static initialization order fiasco). But they are all called at program start.
What if multiple threads are accessing the .dll?
All bets are off. The variable is only constructed once. After that, when you start threads and access it, the variable has to be thread safe, or the threads has to do proper locking when accessing the variable.
For .dlls, it depends on the compiler and the C runtime (CRT). For MSVC released with Visual Studio 2008 SP1, the .dll's CRT will initialize global objects at DLL_PROCESS_ATTACH time and destroy them at DLL_PROCESS_DETACH time, assuming that nothing horrible happened during DLL_PROCESS_ATTACH.
MSN