Overv
Overv

Reputation: 8529

Destructing derived class by deleting base class

I have a situation that looks like the following code:

#include <iostream>

class A
{
public:
    A() { std::cout << "A created!" << std::endl; }
    ~A() { std::cout << "A destroyed!" << std::endl; }

    virtual const char* Name() { return "A"; }
};

class B : public A
{
public:
    B() { std::cout << "B created!" << std::endl; }
    ~B() { std::cout << "B destroyed!" << std::endl; }

    const char* Name() { return "B"; }
};

int main()
{
    A* a = new B();

    std::cout << a->Name() << "\n";

    delete a;

    return 0;
}

I want B to be destroyed when A is destroyed too. Is this possible in its destructor or do I have to implement a virtual Destroy() method or something like that?

Upvotes: 1

Views: 986

Answers (3)

user396672
user396672

Reputation: 3166

If you apply operator "delete" to base class pointer, destructor MUST be virtual (existence of other virtual methods does not matter). For instance, in case of multiple inheritance "delete" operator applied to base class pointer will cause memory fault since compiler doesn't even know were the memory occupied by derived object begins.

Upvotes: 0

SigTerm
SigTerm

Reputation: 26409

Is this possible in its destructor or do I have to implement a virtual Destroy() method or something like that?

Make destructor of A virtual.

 virtual ~A() { std::cout << "A destroyed!" << std::endl; }

If your class have virtual methods, it should use virtual destructor. At least some compilers will complain if you aren't using virtual destructor in class with virtual methods.

Upvotes: 1

tdammers
tdammers

Reputation: 20721

As a rule of thumb, if any of your methods are virtual, the destructor must also be virtual. If it isn't, the declared type of a variable decides which destructor gets called, which is almost never what you want. 99.9% of all cases, you want the destructor from the runtime type.

Upvotes: 3

Related Questions