Virtual Functions, Dynamic Dispatch, and the vtable Mechanism

Intermediate14 min read•Updated: 2026-10-22

🎪 Virtual Functions, Dynamic Dispatch, and the vtable Mechanism

Introduction

Polymorphism ("many forms") allows a single pointer or reference to a base class to invoke overridden methods in derived classes at runtime. In C++, this dynamic dispatch is unlocked via the virtual keyword and implemented through compiler-generated vtables (virtual method tables).

⚠️ Early Binding (Without `virtual`) vs Late Binding

1#include <iostream>
2#include <vector>
3#include <memory>
4 
5class Shape {
6public:
7    // Virtual enables Dynamic Dispatch (Late Binding)
8    virtual void draw() const {
9        std::cout << "Drawing generic shape.\n";
10    }
11    virtual ~Shape() = default; // Crucial! Always use virtual destructors
12};
13 
14class Circle : public Shape {
15public:
16    void draw() const override {
17        std::cout << "Drawing Circle with radius and smooth curves.\n";
18    }
19};
20 
21class Rectangle : public Shape {
22public:
23    void draw() const override {
24        std::cout << "Drawing Rectangle with width and height.\n";
25    }
26};
27 
28int main() {
29    Circle c;
30    Rectangle r;
31 
32    // Base class pointers pointing to derived objects:
33    std::vector<const Shape*> shapes = {&c, &r};
34 
35    for (const auto* s : shapes) {
36        s->draw(); // Dynamically routes to Circle::draw() and Rectangle::draw() at runtime!
37    }
38 
39    return 0;
40}

🔍 Under the Hood: The vtable and vptr Mechanism

1[ Shape Object Memory ]             [ vtable for Circle ]
2┌─────────────────────┐             ┌─────────────────────┐
3│  vptr (Hidden Ptr)  │ ──────────► │ &Circle::draw()     │
4├─────────────────────┤             ├─────────────────────┤
5│  Member Data        │             │ &Circle::~Circle()  │
6└─────────────────────┘             └─────────────────────┘

1
vtable: A static lookup table created per class containing pointers to virtual member functions.
2
vptr: A hidden pointer automatically inserted into every class instance that possesses at least one virtual function. It points directly to that class's vtable.
3
When calling s->draw(), the CPU performs an indirect jump: s->vptr[0](). The microsecond overhead is negligible for 99% of business logic.

Next Lesson

Pure Virtual Functions, Abstract Classes, and Interface Design

Continue learning with hands-on practice, examples, and exercises in the upcoming topic.

Related Lessons

Previous Lesson	Next Lesson
Constructor and Destructor Call Order in Inheritance	Pure Virtual Functions, Abstract Classes, and Interface Design

Practice Quiz

Test your understanding of this lesson with 1 questions. Each question has one correct answer.

Previous Next

PreviousPrevNext

MSK Institute • Shikohabad

Loading Page Content...

Preparing courses, live labs, and learning resources.सामग्री लोड हो रही है, कृपया प्रतीक्षा करें...

Connecting serverPlease wait...

💻 Practical Labs🚀 Free Demo📜 Verified Certificates

⚠️ Early Binding (Without virtual) vs Late Binding

1#include <iostream>
2#include <vector>
3#include <memory>
4 
5class Shape {
6public:
7    // Virtual enables Dynamic Dispatch (Late Binding)
8    virtual void draw() const {
9        std::cout << "Drawing generic shape.\n";
10    }
11    virtual ~Shape() = default; // Crucial! Always use virtual destructors
12};
13 
14class Circle : public Shape {
15public:
16    void draw() const override {
17        std::cout << "Drawing Circle with radius and smooth curves.\n";
18    }
19};
20 
21class Rectangle : public Shape {
22public:
23    void draw() const override {
24        std::cout << "Drawing Rectangle with width and height.\n";
25    }
26};
27 
28int main() {
29    Circle c;
30    Rectangle r;
31 
32    // Base class pointers pointing to derived objects:
33    std::vector<const Shape*> shapes = {&c, &r};
34 
35    for (const auto* s : shapes) {
36        s->draw(); // Dynamically routes to Circle::draw() and Rectangle::draw() at runtime!
37    }
38 
39    return 0;
40}

🔍 Under the Hood: The vtable and vptr Mechanism

1[ Shape Object Memory ]             [ vtable for Circle ]
2┌─────────────────────┐             ┌─────────────────────┐
3│  vptr (Hidden Ptr)  │ ──────────► │ &Circle::draw()     │
4├─────────────────────┤             ├─────────────────────┤
5│  Member Data        │             │ &Circle::~Circle()  │
6└─────────────────────┘             └─────────────────────┘

vtable: A static lookup table created per class containing pointers to virtual member functions.

vptr: A hidden pointer automatically inserted into every class instance that possesses at least one virtual function. It points directly to that class's vtable.

When calling s->draw(), the CPU performs an indirect jump: s->vptr[0](). The microsecond overhead is negligible for 99% of business logic.

Previous Lesson

Next Lesson

Constructor and Destructor Call Order in Inheritance

Pure Virtual Functions, Abstract Classes, and Interface Design

🎪 Virtual Functions, Dynamic Dispatch, and the vtable Mechanism

Introduction

⚠️ Early Binding (Without virtual) vs Late Binding

🔍 Under the Hood: The vtable and vptr Mechanism

Pure Virtual Functions, Abstract Classes, and Interface Design

Related Lessons

Practice Quiz

Loading Page Content...

🎪 Virtual Functions, Dynamic Dispatch, and the vtable Mechanism

Introduction

⚠️ Early Binding (Without virtual) vs Late Binding

🔍 Under the Hood: The vtable and vptr Mechanism

Pure Virtual Functions, Abstract Classes, and Interface Design

Related Lessons

Practice Quiz

⚠️ Early Binding (Without `virtual`) vs Late Binding

⚠️ Early Binding (Without `virtual`) vs Late Binding