Re: Order of destructor execution.
On Jul 23, 7:24 pm, "Victor Bazarov" <v.Abaza...@comAcast.net> wrote:
eshn...@gmail.com wrote:
[..]
unsigned getCont( void )
{
MutexLocker( mut );
Not sure what 'mut' here is,
It doesn't matter.
but if it's a global object of some
kind, then the statement above creates (and immediately discards)
a temporary value of type 'MutexLocker'.
No. That statement declares a variable mut, of type
MutexLocker. If MutexLocker doesn't have a default constructor,
it is illegal, and the compiler should complain. If MutexLocker
does have a default constructor, then it is called.
The destructor for that
temporary is called before the following 'return' statement is
exectuted.
The destructor of mut is called on leaving the function.
return( cont );
}
Will the destructor ~MutexLocker() be executed before the copy
constructor of unsigned?
There is no "copy constructor of unsigned". Does all that clarify
the situation?
Conceptually, cont can be copied, as if it had a copy
constructor. The destructor of the variable mut will be called
after this copy.
--
James Kanze (GABI Software) email:james.kanze@gmail.com
Conseils en informatique orient=E9e objet/
Beratung in objektorientierter Datenverarbeitung
9 place S=E9mard, 78210 St.-Cyr-l'=C9cole, France, +33 (0)1 30 23 00 34