What if your program could choose the right action all by itself, no matter the object type?
Why Virtual functions in C++? - Purpose & Use Cases
Imagine you have different types of animals, like dogs and cats, and you want each to make its own sound. Without virtual functions, you have to write separate code for each animal type everywhere you use them.
This manual way is slow and confusing because you must check the animal type each time and call the right function yourself. It's easy to make mistakes and hard to add new animals later.
Virtual functions let you write one general code that calls the right sound for each animal automatically. The program decides which function to use based on the actual animal type at runtime, making your code cleaner and easier to manage.
if (animalType == DOG) { dog.bark(); } else if (animalType == CAT) { cat.meow(); }
animal->makeSound(); // Calls dog or cat sound automaticallyVirtual functions enable flexible and extendable programs where objects behave correctly without extra type checks.
In a drawing app, different shapes like circles and squares can draw themselves correctly using virtual functions, so the app just calls draw() on any shape without worrying about its type.
Manual type checks make code complex and error-prone.
Virtual functions let objects decide their behavior automatically.
This leads to cleaner, easier-to-maintain, and extendable code.
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
