C++ Programming Tutorial 97 - Inheritance And Polymorphism

[@splendidzr123]

Hands up if you watch this right b4 the final..

[@bucketzzz.]

yes

[@PunmasterSTP]

"The teachers are going to start teaching and the students are going to start studying." Perhaps in an ideal world...

[@harshaljadhav4564]

Great video - where can one practice problems for C++ inheritance and polymorphism concepts ?

[@tessal435]

I appreciate the simplicity of this, thank you!

[@maxim25o2]

rather saying child and parent, more acurate meaning is using #include .... because base class You include in to new class, and You have access to all components as it is made by You. Each new obiect are copying code to him self, difference is only to us, that we have nicer grouped functions.

[@southhippysa3054]

You still use Rad Studio? I’m planning on developing an application so your insight would be helpful.

[@d4m4s74]

I just tested it. Do you have to remake custom constructors? (for example copy user(std::string first_name, std::string last_name) to teacher(std::string first_name, std::string last_name) or is there another trick to it?

[@PunmasterSTP]

I think he'll get to it in the next, final videos. It's been a long road, and I'm kind of sad that it is at an end (at least for C++).

[@MadhuMitha-vu4tu]

Super explaination 😍😍😍😍😍😍

[@zamadahmad]

Love your C++ i am following full series of C++ programming

[@maxim25o2]

About the isomorphism, I have long time to understand what that means, and I notice that polymorphic is related to pointers, compiler somehow knows that trick and creating pointer USER and assigning to it TEACHER compiler knows that he need exclude from object Teacher address of User. That address is unique because it is in side of object of Teacher. That's why we can have many pointers of User which are related to differed child classes like Teacher or Student. Otherwise there was no sense for me creating return type of pointer of user and assigning to it teacher, because teacher is different returning type. But because of inheritance, there compiler knows which type of object assign to pointer.

[@PunmasterSTP]

I read both of your comments on this video, and I'm sorry but I'm not quite sure I understand what you are trying to say. I'm not sure how the #include preprocessor directive is directly related to class inheritance, or how polymorphism is directly related to pointers. I'm interested to learn more about your observations; could you clarify things a bit?

[@xiaonaiheme]

Great video