Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8350339
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 9, 20262026-06-09T08:17:13+00:00 2026-06-09T08:17:13+00:00

Would it be a bad design, that a child class inherit a parent class

  • 0

Would it be a bad design, that a child class inherit a parent class that has no destructor (only the default generated by compiler) ? Some books claimed it’s not good, but didn’t mention under what situation it would.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-09T08:17:15+00:00Added an answer on June 9, 2026 at 8:17 am

    Deleting an object of a derived type through a pointer to a base type with no virtual destructor is undefined behavior. If you expect to do this, and so in general if you expect your class to be extended, you should provide a virtual destructor.

     struct A
     {};
     struct B : A
     {}
    
     //...
     A* a = new B;
     delete a;       //undefined behaviour
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I understand that it's considered bad design to use a normal, threaded webserver (e.g.,
I need to build a small JavaScript library that would only be a couple
I realize (having read other posts on SO as well) that it's bad design
AdventureWorks tables have Insert/Update/Delete anomalies. Isn't that considered bad design? Let's take for example
In subsystem design, I sometimes see software designs that have one high-level class that
I understand that, if S is a child class of T , then a
Preamble : Is it bad design for a base class to be aware of
In some situations using C/C++, I can syntactically indicate to the compiler that a
Ok I have some code that boils down to a pattern like this class
I currently have a routes object that has several regular pages, and would like

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.