Why Interface-like behavior in C++? - Purpose & Use Cases

The Big Idea

What if you could control many different devices with just one simple set of commands?

The Scenario

Imagine you have several different types of devices, like a printer, scanner, and fax machine, each with their own way of working. You want to write code that can use any of these devices without knowing the details of how each one works.

The Problem

Without a common way to interact with these devices, you would have to write separate code for each device type. This means repeating similar code many times, which is slow to write and easy to get wrong. If you add a new device, you must change lots of code everywhere.

The Solution

Using interface-like behavior, you define a common set of functions that all devices must have. Then, your code can work with any device through this common interface, without caring about the details. This makes your code cleaner, easier to maintain, and ready for new devices.

Before vs After

✗ Before

class Printer { void print(); };
class Scanner { void scan(); };
// Need separate code to handle each device

✓ After

struct IDevice { virtual void operate() = 0; virtual ~IDevice() = default; };
class Printer : public IDevice { void print(); void operate() override { print(); } };
class Scanner : public IDevice { void scan(); void operate() override { scan(); } };

What It Enables

You can write flexible programs that work with many different types of objects through a shared interface, making your code easier to extend and maintain.

Real Life Example

Think of a remote control that works with any TV brand because all TVs follow the same basic commands. Similarly, interface-like behavior lets your program control different objects in a uniform way.

Key Takeaways

Manual handling of different types leads to repeated and error-prone code.

Interface-like behavior defines a common set of functions for different types.

This approach makes code flexible, reusable, and easier to maintain.

Practice

1. What is the main purpose of an interface-like class in C++?

easy

A. To store data members for derived classes

B. To provide full function implementations for reuse

C. To define functions that derived classes must implement

D. To create objects directly without inheritance

Solution

1. Step 1: Understand interface concept

   Interfaces specify what functions a class must have but do not provide their code.

2. Step 2: Identify interface role in C++

   In C++, interfaces are created using pure virtual functions that derived classes must implement.

3. Final Answer:

   To define functions that derived classes must implement -> Option C

4. Quick Check:

   Interface = function declarations only [OK]

Hint: Interfaces declare required functions without code [OK]

Common Mistakes:

• Thinking interfaces provide function code
• Assuming interfaces hold data members
• Believing interfaces can be instantiated

2. Which of the following is the correct syntax to declare a pure virtual function in a C++ class?

easy

A. virtual void func() = 0;

B. virtual void func();

C. void func() override;

D. virtual void func() = 1;

Solution

1. Step 1: Recall pure virtual function syntax

   Pure virtual functions are declared with '= 0' after the function signature.

2. Step 2: Check options for correct syntax

   virtual void func() = 0; uses '= 0' correctly, others do not match pure virtual syntax.

3. Final Answer:

   virtual void func() = 0; -> Option A

4. Quick Check:

   Pure virtual = '= 0' [OK]

Hint: Pure virtual functions end with '= 0;' [OK]

Common Mistakes:

• Using '= 1' instead of '= 0'
• Omitting 'virtual' keyword
• Confusing override with pure virtual

3. Consider the following code:

class IShape {
public:
    virtual double area() const = 0;
};

class Circle : public IShape {
    double radius;
public:
    Circle(double r) : radius(r) {}
    double area() const override { return 3.14 * radius * radius; }
};

int main() {
    Circle c(2);
    std::cout << c.area();
    return 0;
}

What is the output of this program?

medium

A. 4

B. Compilation error

C. 3.14

D. 12.56

Solution

1. Step 1: Calculate area of circle with radius 2

   Area = π * r² = 3.14 * 2 * 2 = 12.56

2. Step 2: Confirm code compiles and runs correctly

   Circle implements pure virtual function area(), so no error; output is area value.

3. Final Answer:

   12.56 -> Option D

4. Quick Check:

   Area = 3.14 * 4 = 12.56 [OK]

Hint: Calculate area formula carefully [OK]

Common Mistakes:

• Forgetting to implement pure virtual function
• Using wrong radius value
• Expecting compilation error

4. What is wrong with this code snippet?

class IAnimal {
public:
    virtual void speak() = 0;
};

class Dog : public IAnimal {
public:
    void speak() { std::cout << "Woof"; }
};

int main() {
    IAnimal a;
    a.speak();
    return 0;
}

medium

A. Missing override keyword in Dog::speak()

B. Cannot create object of abstract class IAnimal

C. speak() should return a value

D. Dog class must be abstract

Solution

1. Step 1: Identify abstract class usage

   IAnimal has a pure virtual function, so it is abstract and cannot be instantiated.

2. Step 2: Check main() for object creation

   Code tries to create IAnimal a; which is illegal and causes compilation error.

3. Final Answer:

   Cannot create object of abstract class IAnimal -> Option B

4. Quick Check:

   Abstract class objects cannot be created [OK]

Hint: Abstract classes cannot be instantiated [OK]

Common Mistakes:

• Ignoring abstract class instantiation rules
• Thinking override keyword is mandatory
• Assuming pure virtual functions must return values

5. You want to create an interface-like class IPrinter with a pure virtual function print(). Then create two classes ConsolePrinter and FilePrinter that implement print(). Which of the following code snippets correctly demonstrates this?

hard

A. class IPrinter {
public:
virtual void print() = 0;
};

class ConsolePrinter : public IPrinter {
public:
void print() override { std::cout << "Console output"; }
};

class FilePrinter : public IPrinter {
public:
void print() override { /* write to file */ }
};

B. class IPrinter {
public:
void print() { }
};

class ConsolePrinter : public IPrinter {
public:
void print() { std::cout << "Console output"; }
};

C. class IPrinter {
public:
virtual void print();
};

class ConsolePrinter : public IPrinter {
};

D. class IPrinter {
public:
virtual void print() = 1;
};

Solution

1. Step 1: Define interface with pure virtual function

   IPrinter declares print() as pure virtual with '= 0', making it an interface.

2. Step 2: Implement print() in derived classes

   ConsolePrinter and FilePrinter override print() with their own code, fulfilling interface contract.

3. Final Answer:

   Code snippet D correctly defines interface and implementations -> Option A

4. Quick Check:

   Pure virtual = 0 + override implementations [OK]

Hint: Use '= 0' for pure virtual and override in derived [OK]

Common Mistakes:

• Using '= 1' instead of '= 0' for pure virtual
• Not implementing pure virtual functions in derived classes
• Defining interface functions with bodies