Analyze this destructor implementation:

Person::~Person() {
if(childrenList != nullptr) {
delete childrenList; // Note: delete, not delete[]
}
}
What is the primary issue with this code?

Question

Analyze this destructor implementation:

Person::~Person() {
    if(childrenList != nullptr) {
        delete childrenList;  // Note: delete, not delete[]
    }
}
What is the primary issue with this code?

Accepted Answer

Using `delete` instead of `delete[ ]` for an array causes undefined behavior

Answer

The destructor should also set `childrenList` to `nullptr`

Answer

The destructor should delete `name` as well

Answer

The null pointer check is unnecessary

Crowdly

Analyze this destructor implementation: Person::~Person() { if(childrenLi...

Want instant access to all verified answers on dle.plaksha.edu.in?