Abstract classes in C++ - Time & Space Complexity
When using abstract classes, we want to know how the program's running time changes as we create and use objects from these classes.
We ask: How does the time to run methods from abstract classes grow with the number of objects?
Analyze the time complexity of the following code snippet.
class Shape {
public:
virtual void draw() = 0; // abstract method
};
class Circle : public Shape {
public:
void draw() override {
// drawing circle code
}
};
void drawShapes(std::vector<Shape *> &shapes) {
for (auto shape : shapes) {
shape->draw();
}
}
This code defines an abstract class Shape with a pure virtual method draw. It then draws all shapes in a list by calling draw on each.
Identify the loops, recursion, array traversals that repeat.
- Primary operation: Calling the draw() method on each shape object.
- How many times: Once for each shape in the vector, so as many times as the number of shapes.
As the number of shapes increases, the total time to draw all shapes grows directly with that number.
| Input Size (n) | Approx. Operations |
|---|---|
| 10 | 10 draw calls |
| 100 | 100 draw calls |
| 1000 | 1000 draw calls |
Pattern observation: The time grows in a straight line with the number of shapes.
Time Complexity: O(n)
This means the time to draw all shapes grows directly with how many shapes there are.
[X] Wrong: "Using abstract classes makes the program slower because of extra overhead in method calls."
[OK] Correct: The main time cost comes from how many times methods run, not from the abstract class itself. Calling virtual methods has a small fixed cost, but the total time depends mostly on how many objects you process.
Understanding how abstract classes affect time helps you explain design choices clearly and shows you know how code structure relates to performance.
"What if we added nested loops inside the draw() method? How would the time complexity change?"
Practice
Solution
Step 1: Understand abstract class instantiation rules
Abstract classes have at least one pure virtual function, so they cannot create objects directly.Step 2: Check other options
The other options are incorrect because abstract classes can have member functions and data members.Final Answer:
It cannot be instantiated directly. -> Option BQuick Check:
Abstract class = no direct objects [OK]
- Thinking abstract classes can create objects
- Believing abstract classes cannot have data members
- Confusing abstract classes with interfaces
Solution
Step 1: Recall pure virtual function syntax
Pure virtual functions are declared with 'virtual' keyword and '= 0' at the end.Step 2: Analyze options
virtual void func() = 0; matches the correct syntax. void func() = 0; misses 'virtual'. virtual void func(); is a normal virtual function. void func() {}; is a normal function with a body.Final Answer:
virtual void func() = 0; -> Option AQuick Check:
Pure virtual = virtual + '= 0' [OK]
- Omitting 'virtual' keyword
- Adding function body to pure virtual
- Confusing normal virtual with pure virtual
#include <iostream>
class Base {
public:
virtual void show() = 0;
};
class Derived : public Base {
public:
void show() { std::cout << "Hello"; }
};
int main() {
Derived d;
d.show();
return 0;
}Solution
Step 1: Check abstract class and derived implementation
Base has a pure virtual function 'show'. Derived overrides it with a concrete implementation.Step 2: Analyze main function output
Derived object 'd' calls 'show()', which prints "Hello".Final Answer:
Hello -> Option CQuick Check:
Derived implements pure virtual, so prints output [OK]
- Expecting compilation error without implementation
- Thinking pure virtual functions run by themselves
- Confusing output with no output
#include <iostream>
class Abstract {
public:
virtual void display() = 0;
};
class Concrete : public Abstract {
public:
void display() { std::cout << "Hi"; }
};
int main() {
Abstract a;
Concrete c;
c.display();
return 0;
}Solution
Step 1: Check instantiation of abstract class
Abstract class 'Abstract' has a pure virtual function, so cannot create object 'a'.Step 2: Verify other parts
Concrete implements display(), so no error there. Syntax is correct.Final Answer:
Cannot instantiate abstract class 'Abstract' directly. -> Option AQuick Check:
Abstract objects not allowed [OK]
- Trying to instantiate abstract class
- Ignoring pure virtual function rules
- Assuming implementation missing in derived
Solution
Step 1: Understand requirement for enforcing area() implementation
Using a pure virtual function in an abstract class forces all derived classes to implement area().Step 2: Evaluate options
Create an abstract class Shape with a pure virtual function double area() = 0; and derive specific shapes implementing area(). uses pure virtual function, which is the best way. Create a class Shape with a normal function double area() that returns 0, and override it in derived classes. returns 0 by default, which may hide missing implementations. Create a class Shape with no functions and add area() only in derived classes. does not enforce area() in base. Create a class Shape with a virtual function double area() with empty body. has virtual but not pure, so no enforcement.Final Answer:
Create an abstract class Shape with a pure virtual function double area() = 0; and derive specific shapes implementing area(). -> Option DQuick Check:
Pure virtual enforces implementation [OK]
- Using normal virtual instead of pure virtual
- Not enforcing method in base class
- Returning default values hiding missing overrides
Ready to prove it?
Pass the test and this pattern moves unknown
