Object-Oriented Programming Basics in C++

# CHAPTER 14

Object-Oriented Programming Basics #

1. Introduction #

2. Learning Objectives #

• Explain what OOP is and why it is used.

• Define Classes and Objects.

• Understand the 4 Pillars of OOP:

• Encapsulation

• Abstraction

• Inheritance

• Polymorphism

3. What are Classes and Objects? #

• Class: A blueprint or a template. Think of it as the architectural drawing of a house.

• Object: An instance of a class. Think of it as the actual physical house built from that drawing.

// This is just a conceptual preview; syntax is covered in Chapter 15.
class Car {
    string color; // Data
    void drive(); // Behavior
};

Car myCar; // myCar is an Object of the Car class

4. Pillar 1: Encapsulation #

Real-world analogy: A digital watch. You can see the time and press buttons to change it (public interface), but the intricate gears and circuits inside are hidden and protected (private data).

5. Pillar 2: Abstraction #

Real-world analogy: Driving a car. You know that pressing the accelerator makes the car go faster. You don't need to know the complex thermodynamics and fuel injection processes happening inside the engine. The complexity is abstracted away behind a simple interface (the pedal).

6. Pillar 3: Inheritance #

Real-world analogy:

• Base Class: Animal (has properties like age, and behavior like eat()).

• Derived Class: Dog (inherits age and eat() from Animal, but adds its own behavior like bark()).

7. Pillar 4: Polymorphism #

Real-world analogy: The command "Speak".

• If you tell a Dog to speak, it barks.

• If you tell a Cat to speak, it meows.

• Both share the same interface (Speak), but the implementation takes *many forms* depending on the object.

8. Why use OOP? #

1. 1. Modularity: Troubleshooting is easier. If a car object is broken, you fix the car class, not the whole program.

1. 2. Reusability: Code can be reused through inheritance.

1. 3. Security: Encapsulation hides sensitive data from the rest of the program.

1. 4. Scalability: It is much easier to manage a 1,000,000-line codebase when it is organized into logical objects.

9. OOP vs. Procedural #

10. Common Mistakes for Beginners #

• Thinking OOP is just syntax: OOP is a *mindset*. You have to train yourself to look at a problem and identify the "nouns" (Objects) and the "verbs" (Methods) instead of just writing a list of instructions.

• Over-engineering: Making a class for absolutely everything. Sometimes, a simple function is enough.

11. Exercises #

1. 1. Look around your room and identify 3 potential Objects. For each object, list 2 attributes (data) and 2 behaviors (functions).

1. 2. Write down how a Smartphone class might inherit from a broader ElectronicDevice class.

12. MCQ Quiz with Answers #

13. Interview Questions #

• Q: Explain the 4 pillars of Object-Oriented Programming with real-world examples.

• Q: How does Encapsulation differ from Abstraction?

• Q: Why was C++ created when C already existed?

14. Summary #

15. Next Chapter Recommendation #