The book provides complete guidance for the students from beginning to advanced level. The language is very simple and easy to understand.
To cover the requirements of the students with respect to examination, there are hundreds of questions, multiple choice, fill in the blanks and true/false questions in the book so that the students may prepare for the examination from different point of views. each chapter ends with an exercise for practice.
The book is basically meant for students but it can also be used by any person who wants to get in-depth knowledge of programming in c++.
This book is published by IT Series Publications and authors of the book are Tasleem Mustafa, Tariq Mahmood, Imran Saeed and Ahsan Raza Sattar.
Ideas of OOP
At the center of protest situated writing computer programs are simply the articles. These articles are masterminded into classes, which enable individual items to be assembled together. These articles communicate with each other. With the items given traits and practices, engineers can set these aside to focus on programming how these articles cooperate with each other.
When one question obtains every one of the properties and practices of parent protest this is known as legacy. A class that is utilized as the reason for legacy is named a superclass. A class that acquires from a superclass is named a subclass or determined class. Parent class and youngster class are likewise adequate terms. Legacy gives OOP code reusability and is utilized to accomplish runtime polymorphism.
Polymorphism is the place a solitary assignment can be performed in various ways. This implies OOP has the ability to choose the correct called work at runtime relying upon the present setting. There are two kinds of polymorphism; abrogating and over-burdening. Abrogating (run-time polymorphism) is the place two techniques have a similar strategy name and parameters (i.e. technique signature). One strategy is in the parent class and the other is in the youngster class. Over-burdening (arrange time polymorphism) happens when at least two strategies in a single class have a similar strategy name however extraordinary parameters.
Reflection is the place a software engineer can hide everything aside from the applicable information around a question keeping in mind the end goal to diminish intricacy and increment effectiveness. As it were, speaking to highlights without including foundation subtle elements or clarifications.
Embodiment is where information and strategies that work on that information are packaged together in one unit. It’s utilized to hide esteems or condition of an organized information protest inside a class, averting unapproved guide access to them.
Reflection and embodiment may sound comparable, yet the two vary in that deliberation covers up undesirable subtle elements while giving out most fundamental points of interest, while exemplification implies concealing the code and information into a solitary unit.