Object oriented programming (Introduction) - Article 1

Hi Folks,

Let's start off on OOP and C++. This is an introductory article for the bigger things coming in the future weeks.

What is OOP or Object oriented programming?

OOP stands for object oriented programming. C#, C++ and Java are examples of object oriented languages, where as C, Pascal are examples of procedural languages.

Modularity, extensibility, reusability and maintainability are some of the advantages of OO languages. In OOP, the software programs are organized as OBJECTs. All the entities in OOP are modelled as objects.

Suppose a problem is given, in procedural langauge like C, the problem is divided into functions (actions on data) and data are declared, whereas in C++, the problem is modelled as objects. For example, a problem on car in C will look like,

float brake;
float acceleration;

main() {
    accelerate_the_car();
        if(obstacle == true)
            apply_brake();
}

void accelerate_the_car() {

}

void apply_brake() {

}

The same in C++ would look like:

class car {
    float brake;
    float acceleration;

    public:
    void accelerate_the_car();
    void apply_brake();
};

main() {
    car ford;
    ford.accelerate_the_car();
    if(obstacle == true)
        ford.apply_brake();
}

Don't worry, I am going to explain the things in detail.

Classes & Objects

The dictionary meaning of object is as below:

Object - a material thing that can be seen and touched.

Simply put, objects have phyical existance. Imagine all the real world objects, the laptop, mobile or PC you have been using to read this blog, the car you drive, books you read, etc. Let us take example of car. All cars have properties like engine, brakes, accelerator, windows, etc. All cars exhibit behaviours - drive, accelerate, apply_brake, close_windows, etc.

A small exercise: Think of objects around you and list out their properties and behaviours.

From above, it's clear that all objects have two characteristics: properties and behaviour. As we are concerned about software and C++, let's map these. The properties are nothing but variables or data and behaviours are nothing but methods of functions acting on data.

In C++, variables and corresponding functions are bundled into objects.

So then what is a class and what is the difference between class and object? A class is nothing but CLASSification of objects. i.e., a group of related objects form a class. A class provides blue print for the object and does not have physical existence, where as we have seen that objects have physical existance.

Let me give a real world example. Ford company manufactures cars. Suppose they plan to come up with new model. They design the blue print of the car, i.e., how the car should look like, type of engine, petrol or diesel, etc, etc, etc. The same goes to the factory and using this blue print, cars are manufactured. So, this blue print forms the class for cars that are manufactured.

In C++, objects are created using the class type. In the example program shown, class car is the blue print. In main(), we made an object ford.

Comments

Post a Comment

Popular posts from this blog

Synchronization primitives: Mutex and Semaphore (Serialization & Mutex problems using Semaphore) - Article 6

Hi Friends, In the previous articles, we have gained knowledge about Mutex and Semaphore. In this article, we shall see how a Semaphore can be used to solve serialization problem and Mutual Exclusion (Mutex) problem. Serialization problem: Thread 1: Event A; // Could be any code Thread 2: Event B; // Could be any code The problem is, we have to ensure that Event B or a particular code or instructions should always be executed after Event A or some other particular code. Basically, we are serializing the instructions irrespective of how the threads are scheduled to run. Solution: There are no resources here, we need to just signal, initialize Semaphore to 0. Semaphore SignalThread2 = 0; Thread 1: Event A; SignalThread2.signal(); Thread 2: SignalThread2.wait(); Event B; The code for Thread 1 and Thread 2 is as above. Irrespective of which thread is scheduled, Event A always occurs before Event B. How? Let's say Thread 2 is scheduled first, it executes
Read more

Synchronization primitives: Mutex and Semaphore (Readers & Writers problem) - Article 8

Hi Friends, In this article, we shall solve the Readers & Writers problem. Readers & Writers problem: There may be m writers & n readers related to a shared data structure or a record in the database (some shared data). Only one writer thread can be updating the data, but there can be many readers accessing the data. The constraints are: 1. Any number of readers can be accessing the data in critical section. 2. Only one writer thread should be allowed to update the data in critical section. Solution: int readers = 0; // Shared variable to keep track of number of readers,                  // yes this also needs to be protected Semaphore readersProtect = 1; Semaphore roomEmpty = 1; Writers thread code: roomEmpty.wait();     // Update shared data, critical section for writers roomEmpty.signal(); Readers thread code: readersProtect.wait();     readers = readers + 1;     if(readers == 1)         roomEmpty.wait(); // First reader locks and bars wri
Read more

Copy constructor in C++ (Part 2)

Now, the important question comes is regarding the signature of copy constructor. That is, why copy constructor takes a reference as parameter. Let's copy by value from previous example. CopyDemo(const CopyDemo obj) {     ptr = new int;     *ptr = *obj.ptr; } Now from main(), CopyDemo o2 = o1; Let me explain in detail. We have called copy constructor to copy o1 to o2. But, since we are passing by value, first o1 has to be copied to obj. So internally, statement will be, const CopyDemo obj = o1; Now, what happens is again copy constructor is invoked. Already, we can sense some problem, copy constructor is called again. Internally, the statement is repeated again. const CopyDemo obj = o1; This goes into a recursive loop and following statements get repeated till stack overflow happens and ultimately program crashes. const CopyDemo obj = o1; const CopyDemo obj = o1; const CopyDemo obj = o1; . . .
Read more