Object creation and destruction flow in C++ - Cheat Sheet & Quick Revision

Recall & Review

beginner

What happens first when an object is created in C++?

The constructor of the object is called to initialize it.

beginner

What is the role of a destructor in C++?

A destructor is called automatically when an object goes out of scope or is deleted to clean up resources.

intermediate

In what order are constructors called when creating an object with inheritance?

Base class constructors are called first, then derived class constructors.

intermediate

In what order are destructors called when an object with inheritance is destroyed?

Derived class destructors are called first, then base class destructors.

intermediate

What happens if you forget to define a destructor for a class that manages dynamic memory?

Memory leaks can occur because the allocated memory is not freed properly.

Which function is called automatically when an object is created?

A Constructor

B Destructor

C Copy constructor

D Assignment operator

The constructor initializes the object when it is created.

When is a destructor called?

A When an object is created

B When a class is defined

C When an object goes out of scope or is deleted

D When a function is called

Destructors clean up resources when an object is destroyed.

In inheritance, which constructor is called first?

A Derived class constructor

B Base class constructor

C Destructor

D Copy constructor

Base class constructors run before derived class constructors.

What is the order of destructor calls in inheritance?

A Base class destructor then derived class destructor

B Only derived class destructor

C Only base class destructor

D Derived class destructor then base class destructor

Derived class destructors run before base class destructors.

What problem can occur if a destructor is missing for a class managing dynamic memory?

A Memory leak

B Syntax error

C Faster execution

D No problem

Without a destructor freeing memory, leaks happen.

Explain the flow of object creation and destruction in C++ including inheritance.

Think about the order constructors and destructors run in inheritance.

Why is it important to define a destructor in classes that allocate dynamic memory?

Consider what happens if memory is not freed.

Practice

1. Which of the following statements about object creation and destruction in C++ is correct?

easy

A. Constructors run only when an object is destroyed.

B. Destructors are called before an object is created.

C. Constructors are called automatically when an object is created.

D. Destructors run only when an object is created.

Solution

1. Step 1: Understand constructor timing

   Constructors are special functions that run automatically when an object is created to initialize it.

2. Step 2: Understand destructor timing

   Destructors run when an object is destroyed or goes out of scope, not before creation.

3. Final Answer:

   Constructors are called automatically when an object is created. -> Option C

4. Quick Check:

   Constructor = on creation [OK]

Hint: Remember: constructor = create, destructor = destroy [OK]

Common Mistakes:

• Confusing when constructors and destructors run
• Thinking destructors run before creation
• Believing constructors run on destruction

2. Which of the following is the correct syntax to declare a destructor for a class named Car in C++?

easy

A. ~Car();

B. Car();

C. void ~Car();

D. destructor Car();

Solution

1. Step 1: Recall destructor syntax

   In C++, a destructor is declared with a tilde (~) followed by the class name and parentheses, no return type.

2. Step 2: Check options

   ~Car(); matches the correct syntax: ~Car();. Others are invalid syntax.

3. Final Answer:

   ~Car(); -> Option A

4. Quick Check:

   Destructor syntax = ~ClassName() [OK]

Hint: Destructor always starts with ~ and no return type [OK]

Common Mistakes:

• Adding return type to destructor
• Using wrong keywords like 'destructor'
• Confusing constructor syntax with destructor

3. Consider the following C++ code:

class Test {
public:
  Test() { std::cout << "C"; }
  ~Test() { std::cout << "D"; }
};

int main() {
  Test t1;
  {
    Test t2;
  }
  std::cout << "E";
  return 0;
}

What is the output when this program runs?

medium

A. CCDEE

B. CCDED

C. CDEC

D. CCED

Solution

1. Step 1: Trace object creation

   t1 is created first, prints 'C'. Then t2 is created inside inner block, prints another 'C'.

2. Step 2: Trace object destruction and output

   When inner block ends, t2 is destroyed, prints 'D'. Then 'E' is printed. Finally, t1 is destroyed at program end, prints 'D'.

3. Final Answer:

   CCDED -> Option B

4. Quick Check:

   Creation C twice, destruction D twice, E in middle [OK]

Hint: Destructors run when objects go out of scope [OK]

Common Mistakes:

• Forgetting destructor runs at block end
• Mixing order of destruction
• Ignoring output inside main

4. Identify the error in the following C++ code snippet related to object destruction:

class Sample {
public:
  Sample() { std::cout << "Created"; }
  void ~Sample() { std::cout << "Destroyed"; }
};

int main() {
  Sample s;
  return 0;
}

medium

A. Destructor has a return type which is not allowed.

B. Destructor name is incorrect; it should be 'destruct'.

C. Constructor is missing a return type.

D. Destructor should be public static.

Solution

1. Step 1: Check destructor declaration

   Destructor must not have a return type. Here, 'void' before '~Sample()' is invalid syntax.

2. Step 2: Verify other options

   Destructor name is correct with '~Sample'. Constructors have no return type but that is correct here. Destructors cannot be static.

3. Final Answer:

   Destructor has a return type which is not allowed. -> Option A

4. Quick Check:

   Destructor = no return type [OK]

Hint: Destructor never has a return type, not even void [OK]

Common Mistakes:

• Adding void or other return types to destructor
• Misnaming destructor
• Making destructor static

5. You have a class Resource that opens a file in its constructor and closes it in its destructor. Which of the following code snippets correctly ensures the file is closed automatically when the object goes out of scope?

hard

A. void useFile() {
Resource* r = new Resource();
// use file
delete r;
} // file closed here automatically

B. void useFile() {
Resource* r = new Resource();
// use file
} // file closed here automatically

C. void useFile() {
Resource r;
// use file
delete &r;
} // file closed here

D. void useFile() {
Resource r;
// use file
} // file closed here automatically

Solution

1. Step 1: Understand automatic destruction

   Objects created on stack (like 'Resource r;') are destroyed automatically when going out of scope, calling destructor to close file.

2. Step 2: Analyze dynamic allocation

   Objects created with 'new' must be deleted manually; otherwise destructor won't run automatically, risking resource leaks.

3. Final Answer:

   void useFile() { Resource r; // use file } // file closed here automatically -> Option D

4. Quick Check:

   Stack objects auto-destroyed, heap objects need delete [OK]

Hint: Use stack objects for automatic destructor calls [OK]

Common Mistakes:

• Forgetting to delete heap objects
• Trying to delete stack objects
• Assuming destructor runs without delete on heap