Thread: Design Issue.

Just recently I started a thread here where I was asking exactly what's the best way to deal with dynamic data members. You can find it here

Without disregard to any other reply I got there, take notice of Sorensen's solution further down to the end of the thread. You may find it useful.

Actually, the solution is simpler than you thought! See, when a derived class is being destroyed, the base class destructor is called too! Compile and run this:

Code:

class Foo{ public:

~Foo(){ cout << "Foo Destructor Being Called" << endl; getch();}

};



class Bar : public Foo{ public:

~Bar(){ cout << "Bar Destructor Being Called" << endl; getch();}
};




class Tee : public Bar{ public:

~Tee(){ cout << "Tee Destructor Being Called" << endl; getch();}
};





int main(int argc, char *argv[])
{


 Tee s;



  return 0;
}

By the way: there is another useful mechanism in C++: the pure virtual function. In essence, declaring one in the base class forces each derived class to define it's own definition of the function!

Compile this and see what I mean:

Code:

class Foo{ public:

virtual void Required() = 0;

};



class Bar : public Foo{ public:


};









int main(int argc, char *argv[])
{


 Bar s;



  return 0;
}

There is auto_ptr, which is pretty nice for transferring ownership and making damn sure the owner is responsible for deletion, but it makes sharing objects impossible.

http://www.gotw.ca/publications/usin...ffectively.htm