Virtual functions in C++ - Time & Space Complexity
When using virtual functions in C++, the program decides at runtime which function to call. This adds a small extra step compared to normal function calls.
We want to understand how this extra step affects the program's running time as the input grows.
Analyze the time complexity of the following code snippet.
class Base {
public:
virtual void show() { /* base version */ }
};
class Derived : public Base {
public:
void show() override { /* derived version */ }
};
void callShow(Base* arr[], int n) {
for (int i = 0; i < n; ++i) {
arr[i]->show();
}
}
This code calls a virtual function show() on each object in an array of pointers.
- Primary operation: Calling the virtual function
show()on each object. - How many times: Exactly
ntimes, once per element in the array.
Each call to show() requires a small extra step to find the right function version, but this step happens once per element.
| Input Size (n) | Approx. Operations |
|---|---|
| 10 | 10 virtual calls |
| 100 | 100 virtual calls |
| 1000 | 1000 virtual calls |
Pattern observation: The total work grows directly with the number of elements, so doubling the input doubles the work.
Time Complexity: O(n)
This means the time to run grows in a straight line with the number of objects we call the virtual function on.
[X] Wrong: "Virtual functions make the program run much slower, so the time complexity becomes worse than linear."
[OK] Correct: Each virtual call adds a tiny fixed cost, but it still happens once per element. The overall time still grows linearly with input size.
Understanding how virtual functions affect time helps you explain performance trade-offs clearly. This skill shows you know how features impact program speed in real situations.
"What if the virtual function called inside the loop itself contained a loop over the input size? How would the time complexity change?"
Practice
virtual in a C++ base class?Solution
Step 1: Understand virtual function role
A virtual function in a base class allows derived classes to provide their own implementation that will be called at runtime.Step 2: Recognize runtime polymorphism
This mechanism enables dynamic dispatch, meaning the program decides which function to call based on the actual object type, not the pointer type.Final Answer:
To allow derived classes to override the function and enable runtime polymorphism -> Option AQuick Check:
Virtual function = runtime polymorphism [OK]
- Confusing virtual with inline functions
- Thinking virtual prevents overriding
- Assuming virtual makes function static
display in a base class?Solution
Step 1: Recall correct virtual function syntax
The keywordvirtualmust come before the return type and function name.Step 2: Check each option
virtual void display(); correctly placesvirtualbeforevoid display();. Others have incorrect order or placement.Final Answer:
virtual void display(); -> Option AQuick Check:
virtual before return type = correct syntax [OK]
- Placing virtual after function name
- Mixing order of keywords
- Adding virtual at the end of declaration
class Base {
public:
virtual void show() { std::cout << "Base"; }
};
class Derived : public Base {
public:
void show() override { std::cout << "Derived"; }
};
int main() {
Base* ptr = new Derived();
ptr->show();
delete ptr;
return 0;
}What is the output when this program runs?
Solution
Step 1: Analyze pointer and object types
The pointer is of typeBase*but points to aDerivedobject.Step 2: Understand virtual function call
Becauseshow()is virtual, theDerivedversion is called at runtime, printing "Derived".Final Answer:
Derived -> Option CQuick Check:
Virtual function calls derived version [OK]
- Assuming base class function runs
- Confusing override keyword effect
- Expecting compilation or runtime errors
class Base {
public:
void display() { std::cout << "Base"; }
};
class Derived : public Base {
public:
void display() override { std::cout << "Derived"; }
};Solution
Step 1: Check base class function declaration
The base class functiondisplay()is not declaredvirtual.Step 2: Understand override keyword usage
Theoverridekeyword requires the base function to be virtual; otherwise, it causes a compilation error.Final Answer:
Base class function must be declared virtual to allow override -> Option DQuick Check:
Override needs virtual base function [OK]
- Ignoring missing virtual in base
- Thinking override is optional
- Assuming same name always means override
class Animal {
public:
virtual void sound() { std::cout << "Animal sound "; }
};
class Dog : public Animal {
public:
void sound() override { std::cout << "Bark "; }
};
class Cat : public Animal {
public:
void sound() override { std::cout << "Meow "; }
};
int main() {
Animal* animals[3];
animals[0] = new Animal();
animals[1] = new Dog();
animals[2] = new Cat();
for (int i = 0; i < 3; i++) {
animals[i]->sound();
}
for (int i = 0; i < 3; i++) {
delete animals[i];
}
return 0;
}Solution
Step 1: Analyze array of Animal pointers
The array holds pointers to objects of types Animal, Dog, and Cat respectively.Step 2: Understand virtual function calls in loop
Callingsound()on each pointer calls the overridden version based on actual object type, printing "Animal sound ", "Bark ", and "Meow ".Final Answer:
Animal sound Bark Meow -> Option BQuick Check:
Virtual calls print actual object sounds [OK]
- Expecting base class sound for all
- Confusing array pointer syntax
- Assuming compilation error with polymorphism
Ready to prove it?
Pass the test and this pattern moves unknown
