Repeat Destructor vs member

Question

I already saw a similar question: The destructor against the race of member functions .. but could not find the answer to the following. Suppose we have a class that owns some workflow. A class destructor might look like this:

~OurClass
{
    ask_the_thread_to_terminate;
    wait_for_the_thread_to_terminate;
    ....
    do_other_things;
}

The question arises: can we name ourClass member functions in the workflow, because we are sure that all these calls will be made before do_other_things in the destructor?

Answer 1

Yes, you can. Destruction of member variables will only begin after completion do_other_things. It is safe to call member functions before the destruction of the object.

Answer 2

, , . , - :

~OurClass
{
    delete *memberPointer_; 
    ask_the_thread_to_terminate; // the thread calls OurClass::foo();
    wait_for_the_thread_to_terminate;
    ....
    do_other_things
}

void OurClass::foo()
{
    memberPointer->doSomething();
}

. . . , , , .

Answer 3

, - , . , (, SingerOfTheFall).