RE: Abstract base class / virtual destructor
If I have a totally abstract base class A (essentially an interface):
class A
{
virtual void DoSomething() = 0;
}
and I have a derived class B
{
int m_Bint;
virtual void DoSomething();
}
Importantly, it is known that class B does not allocate memory on the
heap. is it absolutely correct, good-manners or incorrect to include a
virtual destructor in base class A? For the case:
A* p = new B;
Whether it is important in this particular case or not is not relevant IMO.
Btw, it does not only depend on heap allocations, but also on resources you
open in the constructor and other things. basically, if your destructor does
anything at all, you should ensure that it runs.
Suppose you decide not to add a virtual destructor because it is safe in
this case. Some time later, you want to use A for deriving another class, or
B changes.
Then you suddenly have a lot of uncorrect code on your hands that may cause
strange behavior.
In effective C++, Scott Meyers warns that you should always use virtual
destructors for base classes.
This is like discussing how close you can safely walk near the edge of a
cliff.
While the discussion itself can be entertaining, the best idea is to just
stay away from it.
--
Kind regards,
Bruno.
bruno_nos_pam_van_dooren@hotmail.com
Remove only "_nos_pam"