You're very welcome Brandon, I'm glad you enjoyed it! :-)

You’re welcome, I’m glad that you found the explanation clear and concise! :-)

I'm really happy that you're enjoying the content, thank you for the kind feedback! :-D

You’re welcome Miss, I’m glad you’re enjoying the tutorials! :-)

You're welcome Erman! :-)

You're welcome, and thank you for the kind words! :-)

Thank you Gabriel! 🙂

I'm glad you found it clear! :-D

I'm really glad to hear that you enjoyed the video Ömer, and thank you for the kind words! :-) And by the way your written english seems pretty good to me!

I'm glad you enjoyed the video! :-)

You’re welcome Bozian, I’m really glad to hear the video helped you out! :-)

You’re very welcome, thank you for watching! :-)

These are great questions! :-) Objects that are instantiated using local variables of a function will exist in a portion of memory called 'the stack' that is managed for us automatically, they will have the lifetime of that function call (i.e. the memory that object uses on the stack will be freed when the function returns). But objects that are dynamically allocated (e.g. with 'new') exist on 'the heap', a separate portion of memory that we need to manually manage (e.g. by calling 'delete' to free the memory that object is using). We use pointers to refer to objects that have been dynamically allocated on the heap. Technically, we can use pointers to refer to objects on the stack as well. But using pointers allows to keep a "pointer" (i.e. memory address) to these objects on the heap, and that pointer can be passed around to different functions so they can access the same object too. Sometimes we'll have code where one function creates the object with dynamic memory allocation, and much later, a different function will free the memory associated object, using the pointer to the object. And I do not believe it is possible to implement runtime polymorphism without pointers, as the idea with runtime polymorphism is that the exact method to be called is determined at runtime when the member function of the object the pointer is pointing to is accessed. I don't know how that could really be possible without pointers, but sometimes in languages like C++ that are so large and have so many features, I'll find out there are ways of doing things that I'm totally unaware of. :-) This comment on stackoverflow also seems to suggest that it is not possible though: stackoverflow.com/a/7223724

@@PortfolioCourses great answer, thank you :)

You're welcome! :-)

I'm glad you enjoyed the video Joel! :-)

I'm not sure, it's hard to know without seeing your code. The original code for the video is found here: github.com/portfoliocourses/cplusplus-example-code/blob/main/abstract_class.cpp. Do you get the error if you use this code? Maybe there is a difference between this code and the code you're using? Apparently this error can happen if you use "end" instead of "endl" when outputting values, so maybe check for that, but the error can occur for other reasons as well.

@@PortfolioCourses uhm I found the solution to it myself. Apparently if you use a method that uses cout command in a cout statement, then that error shows up. So I fixed it by simply calling the method outside of the cout statement. Thanks for replying though.

@@animeIsle That makes sense, I'm glad you figured it out! 🙂

@@PortfolioCourses Yea and oh boy, figuring it out yourself gives you a lot of satisfaction. You're surprisingly replying to the comments even if the video was uploaded quite a while ago. Hard to find people like you ngl. I respect you for that.

@@animeIsle I totally agree that figuring it out yourself feels great, that's the "addiction" of programming. 🙂 And thanks for the kind words!

You’re welcome Mohannad! :-)

The short answer is "not really". Rather than use templating, something like a function would be a better approach to reducing code duplication in this case.

@@PortfolioCourses damn. Didn’t think about that. Thanks master!!

@@Victor-fl8ex Haha you're welcome! :-D