Some additional runtime costs are acceptable to make the COST of actually programming it smaller. And hay, people even use python to program which gives you a heavy runtime penalty compared to C/C++...
Let's say, I just touch your cheeks using a fingertip and then I slap you. Both are impacts. The first 1 will just hurt you mentally (some feeling of awkwardness) but the second 1 will hurt you both physically and mentally). You may ignore the 1st one and move on with your life, but you won't be able to forget about the second one for quite a while. I hope I have made my point.
For the newcomers, my suggestion would be to watch "stack vs heap memory in C++", "how to create/instantiate objects in c++" and "the new keyword in c++" before watching this.
Brief explanation of uncovered topics (yet) in this video: Since strings is not a primitive type of C++ we need to import the header #include To use string without namespace std is like this: std::string MyString("hello") This is equivalent to: std::string MyString = "Hello" Pointer instances: new keyword returns a pointer std::string* MyString = new std::string("Hello") And if is a pointer you access their properties with -> instead of a dot (.) std::cout length()
Thanks, this was really helpful. There is one more thing that was not explained before (as far as I can recall). In the constructor of the player class, he uses a constant string "name", which he passes by reference (first, I don't understand why this has to be a constant or a reference) and then he goes on to add the colon and m_name(name). I think I have seen in some other tutorial series that this is the way to load a value into a constant but I am not sure now.
So what's "Player(const std::string& name) : m_Name(name) {}" exactly? Could u give me a keyword of this stuff to search? I have no idea what it is and how to search it for details.
Figured id give you a thumbs up your 30 second explanation of what a virtual function does explained what my teacher could not do in 2 hours. Appreciate it sir.
Beautiful set of tutorials. Probably the best I've seen so far for any programming language. I also like how it is divided into the different episodes that you can watch whenever you are only interested in a specific topic. Thank you for your time and please keep going like this!
One of my lecturers actually went and dissembled the function calls for a Virtual function and for non-virtual functions for us to look at. The Normal function call executed 4 assembly instructions where as the Virtual function call executed 6, the additional 2 were dereferencing the pointer to the function pointer in the Vtable and then dereferencing the function pointer in the Class-specific function list. The overhead of 2 extra x86 instructions is next-to unnoticeable compared to the penalty of setting up a new stack-frame (which you have to do for both anyway) so the performance hit really in negligible.
Most of the time I've seen a tutorial about virtual functions/vtables it works pretty well to make some diagrams on paper about how it works because it's such an abstract concept that in general people, especially newbies, find a hard time trying to understand what's happening under the hood.
Gotta say this video helped me understand virtual functions a lot more than anything else so far. Going to have to hunt down the other things that confuse me. I've been following a C++ tutorial app at work during breaks and such and these were stumbling blocks that undermined my whole understanding of polymorphism.
Very nice explanation. Short and right to the point. It's easy to agree with your assessment that v-tables have such minimal cost that the inconvenience of not using them makes using them a no-brainer. Thank you very much!
Let me tell you, I've been going to school for Software Engineering, and I have taken a bunch of different languages. Not a single one of them I really understood, just got it well enough to pass the class. But ever since I've found your CPP series, it's really helped, and I think I finally "get" it. This is the first language where I'm able to code without having to look up the solution 5 minutes into trying. Thank you for this series!
I don’t know if it’s this guys videos that influence my feelings but I feel like C++ is the most intuitive programming language I’ve ever used. I feel like the newer higher level languages abstract things away to the point where they actually miss their goal of being easier, and wind up being much more confusing because there is so much going on behind the scenes that you never really know what exactly your code is doing.
Personal notes: - Virtual functions help us to override functions in subclasses - Normally, without virtual functions, when you call a fucntion, that funtion is called according to the type the variable is declared, not according to the real type that variable points to(see video) - Virtual function helps you to call the proper fucntion, not according to the declared type, but according to the actual type it points to - Override keyword is used to specify that that function overrides another func in base class(u don’t have to use though)
Thanks for your video. One thing I could add for virtual keyword is to add this keyword on destructor of the parent class to prevent memory leak when a derived class is deleted through the parent pointer.
1. Virtual function: declared in the base class, which enables the derived object to use its override function. 2. Override: declared after the function in the derived class. not required, but avoid misspelling the function name or overriding the non-virtual function in the base class. 3.V Table : stores the virtual function in the base class to dispatch, which cost space, int * pointer to the override function. 4. in specific embedded systems, using v table might impact the performance .
In 2:10 an entity pointer is pointing to a memory area assigned to a player object. It will get converted this way: Entity *e = (class Entity*)p; Great video!
This series Applies in 2022 Meets the standards for my school's conventions (industry standards) Is more articulate and understandable than the "C++ For Dummies" series Has a loving/lovable character directing it I (with next to no rep or qualifications) award the Cherno with best C++'s best resource award I said it here Now I'm going to say it everywhere else.
Awesome video as always Yan. I know for the general use of virtual functions this video is absolutely enough, but I would love to see an explanation of how early and late binding comes into play with these functions and the concept of a vtable. Thanks!
Yes, that will be covered in the vtable video. Late binding doesn't _really_ exist in C++ since everything must be known at compile time, and the vtable essentially just allows dispatching to a number of preset values (that are contained in the table), not to _anything_ which would be the case with late binding.
Thank God for these videos. My professor is super chill, but he's so bad at explaining things. He reads the book at us and then explains things as though we already know it and moves way too fast and gets way too complicated.
Good stuff. Knew and used virtual functions already and funnilly enough I already learned this morning about the word "override" (also spoiler alert: final and volatile classes/member functions :O so much to learn!).
Dude you are great at explaining these things. Probably won't ever see this comment but thank you. I don't write comments a lot but I am teaching myself c++ and I've watched several of your vids and they are awesome and extremely helpful. Thanks again!
-> in c++ ~~~ An operator in C/C++ allows to access elements in Structures and Unions. It is with a pointer variable pointing to a structure or union. The operator is formed by using a minus sign, followed by the geater than symbol as shown below but bro we didn't reach union yet
If I was new to this I would have struggled to understand. Your explanation is very good but it is impossible to pause the video to see all code to be able to imagine this scenario. It would be nice to have this simple code all on the screen and then You explaining it. In Your video, You jumping between screens and this create a lot of confusion for all newbies I imagine. Maybe a smaller font :) ..the point is If I explaining this to anybody I Print the example code on a single page and then explain, If I jump pages from declarations to the main function this is very confusing ...but this is just me ...Anyway I like Your videos Regardless :) Regards
Certainly, this is not a topic for a newbie... virtual function is a complex feature of class heritance that I don't think there is an easy way to explain to people who have never coded anything in their life. This guy is obviously an expert and knows what he is talking about because he must have been programming for years.
In Bjarne's book he states the cost of a vtbl as two memory accesses plus the function call, exactly. The vtbl is just a collection of pointers to pointers. Two accesses is proportionally huge for some special cases and totally insignificant for others.
you kinda ran away at the beginning there. You've not gone over the Player(const std::string& name) : m)Name(name) {} syntax, nor the e->GetName() syntax. You kinda just left a lot of people in the dust there my guy.
Virtual functions are basically backups for functions. So it tells the complier that if a function is overwritten then it knows that it originally meant.
What is the difference between Player(const std::string& name):m_name(name) {} and Player(const std::string& name) { m_name = name; } Is it some kind of syntactic sugar?
There's no _real_ practical difference between the two, however there is a difference. Since m_Name is a class member which has the type std::string (which is stack-allocated), it will actually be instantiated twice in your second example (firstly with an empty string, and secondly copied from the name parameter), but only once in your first example (via the constructor's intiailiser). Definitely going to be a video on this in the future. :)
I can't say how useful your series has been. My son is twelve and is into robotics and programming and switching from python to C++. He loves your series and I'm playing catchup to help him though I'm the one lagging behind. Thank you, and let me know, if you read this, if you ever considered doing something about OpenCV or anything machine learning? :-D
So far your videos have been good. But this is the first one I do not like. You're using and refering way too much, you actually did not use at this point of the series. Initialationlits, the ->, randomly using a pointer with the keyword new as an object and so on. WAY too much new stuff that has not been covered yet.
Yes. Agreed! Please reorganize the playlist. At least put this tutorial after the -> tutorial and the new keyword tutorial. And as far as I can tell you still haven't done a dedicated tutorial to polymorphism so why refer to it here.
@@explorerofworlds512 the -> is essentially just a shorthand for dereferencing a struct or class pointer and then trying to access a member. // declare a new pointer to a myClass object and then use new to allocate enough memory for it myClass* myclass = new myClass(); myclass->some_func(); // is equivalent to *(myclass).some_func();
@@masondaub9201 Yeah, i came back to it later. It makes a lot more sense after watching later tutorials. Like I said needs would be great to have the playlist rearranged a bit.
Okay Cherno... we get it... we are dumb. You happy now? Guess I'll just have to watch more of your videos to understand these unexplained concepts, which I was going to anyways because you're the best teacher ever. :D
On the flip side, the ease of Java comes at the expense of the level of control and optimization that C++ gives you. I started out with Java and now, after getting used to C++, Java just feels so limited.
@@jscorpio1987 Java's strength is in enterprise application ,it's toolset and frameworks are perfect for that . Yes it doesn't have much control over small low level optimisation due to jvm ,but platform independence compensates it perfectly .
@@jscorpio1987 I also started with Java. And, even now, I still prefer Java over C++ but I see the strengths of it too. For example, anything related to graphics in Java to me seems like it hasn't really been thought about too much. Mean, games built with it are (usually) a lot slower and even basic interfaces are difficult to make. With C++, there are many more libraries built to help with this. While these libraries are often ported to Java, it just doesn't feel complete.
These videos started out so exceptionally great but it seems he has grown weary of this subject now, rushing through them and using unexplained code all the time.
There is Zero problem with this video. If you don't get it then you haven't actually practiced inheritance enough to learn why we needed the virtual functions in the first place. Just watching videos will never get you anywhere in programming. You will have to actually write the code, test it with all possible conditions you can think of, try to do illegal stuff and then understand why it is not working, is the only way you can truly learn any topic.
@@deleater I think he is not refering to virtual functions. Cherno introduced many other subjects in this video without explaining them, but all these are explained in future videos, so the only thing to take out of this video is the type "Virtual" subject
Because the *new* keyword dynamically allocates memory and returns a pointer to the address of that allocated memory, hence why we need a pointer type. Check out my video on pointers if you haven't already, and I will definitely be making a video on memory allocation in the future.
I will just add that in Java classes are by default reference types, while in C++ everything is value type, so if you need to refere to the same value, then you need to use pointers. So you can use same class definition as reference or value type. For example if you have new class Vector (position) , and you pass it to function as Vector (by value) or as Vector * ( as pointer only). If you embed Vector in Entity you can embed entire Vector or only a pointer to Vector.
Not sure if this will get seen this many years later, but I have a quick question. Does this mean that we should always define all of the functions in the base class as “virtual” as a rule of thumb? Thank you for the videos yan love your content
There's no such thing as "minimal impact" in my opinion, there's impact or no impact. I'd rather avoid impact altogether. :P
If you live your life without recognising levels of impact and absorbing some, you're not going to get anything done.
I was just kidding, but the topic of optimization in programming is very interesting to me. ;)
Some additional runtime costs are acceptable to make the COST of actually programming it smaller. And hay, people even use python to program which gives you a heavy runtime penalty compared to C/C++...
Interesting.
Let's say, I just touch your cheeks using a fingertip and then I slap you. Both are impacts. The first 1 will just hurt you mentally (some feeling of awkwardness) but the second 1 will hurt you both physically and mentally). You may ignore the 1st one and move on with your life, but you won't be able to forget about the second one for quite a while. I hope I have made my point.
For the newcomers, my suggestion would be to watch "stack vs heap memory in C++", "how to create/instantiate objects in c++" and "the new keyword in c++" before watching this.
thanks man, this is exactly what I was wondering
thx :)
thanks man!
Thanks a lot.
also inheritance in C++ really clears up the class Player : public Entity
Brief explanation of uncovered topics (yet) in this video:
Since strings is not a primitive type of C++ we need to import the header
#include
To use string without namespace std is like this:
std::string MyString("hello")
This is equivalent to:
std::string MyString = "Hello"
Pointer instances:
new keyword returns a pointer
std::string* MyString = new std::string("Hello")
And if is a pointer you access their properties with -> instead of a dot (.)
std::cout length()
Thanks for explaining. Now it all makes sense.
Thank you for your detailed explanation!
Thanks, this was really helpful. There is one more thing that was not explained before (as far as I can recall). In the constructor of the player class, he uses a constant string "name", which he passes by reference (first, I don't understand why this has to be a constant or a reference) and then he goes on to add the colon and m_name(name). I think I have seen in some other tutorial series that this is the way to load a value into a constant but I am not sure now.
thank u bro, love u every much
So what's "Player(const std::string& name) : m_Name(name) {}" exactly? Could u give me a keyword of this stuff to search? I have no idea what it is and how to search it for details.
My English captions: "my name is HMO and welcome back to my syphilis gloss series".
This is fax, i just tried it 🤣
To better understand his code, go through these topics first:
1. String Class
2. Initialisation list
3. Arrow Operator
4. New keyword
Figured id give you a thumbs up your 30 second explanation of what a virtual function does explained what my teacher could not do in 2 hours. Appreciate it sir.
By far the best channel on youtube to learn anything about c++! Thanks a lot cherno!
Beautiful set of tutorials. Probably the best I've seen so far for any programming language.
I also like how it is divided into the different episodes that you can watch whenever you are only interested in a specific topic.
Thank you for your time and please keep going like this!
One of my lecturers actually went and dissembled the function calls for a Virtual function and for non-virtual functions for us to look at. The Normal function call executed 4 assembly instructions where as the Virtual function call executed 6, the additional 2 were dereferencing the pointer to the function pointer in the Vtable and then dereferencing the function pointer in the Class-specific function list. The overhead of 2 extra x86 instructions is next-to unnoticeable compared to the penalty of setting up a new stack-frame (which you have to do for both anyway) so the performance hit really in negligible.
Excellent comment. I'm having an error now which mentions the vtable and I think I know what's going on now thanks to this explanation . Thanks!
Thanks for sharing!
Doesn't it matter how big your vtable is though?
Dereferencing the function pointer can cost you 1000 instructions, because RAM has a high latency.
@@ronensuperexplainer depends. Couldn't one develop a prefetcher for this problem to reduce memory latency?
Guests: That's a very nice sofa, how comfy is it to sit on..?
Cherno: No, it's just for the Aesthetics, I sit on the ground.
You are the best Cherno. I am visiting your c++ series regularly. Basically when I run into a concept I need to get familiar with on the go :D
Virtual functions at first seemed harder than pointers for me... You've simplified it so elegantly... Thank you :)
Most of the time I've seen a tutorial about virtual functions/vtables it works pretty well to make some diagrams on paper about how it works because it's such an abstract concept that in general people, especially newbies, find a hard time trying to understand what's happening under the hood.
Gotta say this video helped me understand virtual functions a lot more than anything else so far.
Going to have to hunt down the other things that confuse me. I've been following a C++ tutorial app at work during breaks and such and these were stumbling blocks that undermined my whole understanding of polymorphism.
Very nice explanation. Short and right to the point. It's easy to agree with your assessment that v-tables have such minimal cost that the inconvenience of not using them makes using them a no-brainer. Thank you very much!
This is short and beautiful, man! Please, continue doing what you do now
Let me tell you, I've been going to school for Software Engineering, and I have taken a bunch of different languages. Not a single one of them I really understood, just got it well enough to pass the class. But ever since I've found your CPP series, it's really helped, and I think I finally "get" it. This is the first language where I'm able to code without having to look up the solution 5 minutes into trying. Thank you for this series!
I don’t know if it’s this guys videos that influence my feelings but I feel like C++ is the most intuitive programming language I’ve ever used. I feel like the newer higher level languages abstract things away to the point where they actually miss their goal of being easier, and wind up being much more confusing because there is so much going on behind the scenes that you never really know what exactly your code is doing.
@@jscorpio1987 +1
@@jscorpio1987 hell no
Personal notes:
- Virtual functions help us to override functions in subclasses
- Normally, without virtual functions, when you call a fucntion, that funtion is called according to the type the variable is declared, not according to the real type that variable points to(see video)
- Virtual function helps you to call the proper fucntion, not according to the declared type, but according to the actual type it points to
- Override keyword is used to specify that that function overrides another func in base class(u don’t have to use though)
Thanks for your video. One thing I could add for virtual keyword is to add this keyword on destructor of the parent class to prevent memory leak when a derived class is deleted through the parent pointer.
1. Virtual function: declared in the base class, which enables the derived object to use its override function.
2. Override: declared after the function in the derived class. not required, but avoid misspelling the function name or overriding the non-virtual function in the base class.
3.V Table : stores the virtual function in the base class to dispatch, which cost space, int * pointer to the override function.
4. in specific embedded systems, using v table might impact the performance .
Rewording content in summary form is actually a great way to learn and reinforce knowledge 👍🏽
In 2:10 an entity pointer is pointing to a memory area assigned to a player object. It will get converted this way: Entity *e = (class Entity*)p; Great video!
Please make a video on V Table and Memory allocation. I have been watching C++ playlist, your videos are very good to get concepts more clear.
It is the luckiest moment in this year that i found these series right after i started learning cpp
Dude ! You are wonderful, you are smart not to explain unnecessary stuff. Explain the important things and other important related aspects ! wow ..
Thank you! You explained VTable so easily. I can continue my Reverse Engineering tutorials in peace now. Keep up the good work!
Excellent explanation. Something I'm looking for. Thank you so much.
I'm working on an assignment and this is so helpful, thanks so much!
Haha loving the "is he going to be in focus or not?" game I'm playing watching through these videos 😂 such an epic series though mate, thanks!
This series
Applies in 2022
Meets the standards for my school's conventions (industry standards)
Is more articulate and understandable than the "C++ For Dummies" series
Has a loving/lovable character directing it
I (with next to no rep or qualifications) award the Cherno with best C++'s best resource award
I said it here
Now I'm going to say it everywhere else.
Awesome video as always Yan. I know for the general use of virtual functions this video is absolutely enough, but I would love to see an explanation of how early and late binding comes into play with these functions and the concept of a vtable. Thanks!
Yes, that will be covered in the vtable video. Late binding doesn't _really_ exist in C++ since everything must be known at compile time, and the vtable essentially just allows dispatching to a number of preset values (that are contained in the table), not to _anything_ which would be the case with late binding.
Right on. Thanks.
So many new concepts in this video, I wish you would just explain them quickly lol. All the other videos have been perfect. Thanks though.
Thank God for these videos. My professor is super chill, but he's so bad at explaining things. He reads the book at us and then explains things as though we already know it and moves way too fast and gets way too complicated.
Good stuff. Knew and used virtual functions already and funnilly enough I already learned this morning about the word "override" (also spoiler alert: final and volatile classes/member functions :O so much to learn!).
I don't know if I particularly like the fact that the override keyword comes after the function signature. I come from C#, so it's strange to look at.
You must unlearn what you have learned.
Dude you are great at explaining these things. Probably won't ever see this comment but thank you. I don't write comments a lot but I am teaching myself c++ and I've watched several of your vids and they are awesome and extremely helpful. Thanks again!
This is really complicated for me a new learner.
Me too
Excellent, just what I needed.
-> in c++ ~~~ An operator in C/C++ allows to access elements in Structures and Unions. It is with a pointer variable pointing to a structure or union. The operator is formed by using a minus sign, followed by the geater than symbol as shown below but bro we didn't reach union yet
If I was new to this I would have struggled to understand. Your explanation is very good but it is impossible to pause the video to see all code to be able to imagine this scenario. It would be nice to have this simple code all on the screen and then You explaining it. In Your video, You jumping between screens and this create a lot of confusion for all newbies I imagine. Maybe a smaller font :) ..the point is If I explaining this to anybody I Print the example code on a single page and then explain, If I jump pages from declarations to the main function this is very confusing ...but this is just me ...Anyway I like Your videos Regardless :) Regards
ikr its confusing where he keeps on jumping everywhere i cant keep up
Certainly, this is not a topic for a newbie... virtual function is a complex feature of class heritance that I don't think there is an easy way to explain to people who have never coded anything in their life. This guy is obviously an expert and knows what he is talking about because he must have been programming for years.
That's true! I kept on pausing the screen to get it
In Bjarne's book he states the cost of a vtbl as two memory accesses plus the function call, exactly. The vtbl is just a collection of pointers to pointers.
Two accesses is proportionally huge for some special cases and totally insignificant for others.
tysm! every topic you explain is so clear and simple
you kinda ran away at the beginning there. You've not gone over the Player(const std::string& name) : m)Name(name) {} syntax, nor the e->GetName() syntax. You kinda just left a lot of people in the dust there my guy.
Its was a very good and technical explanation, thank you.
Employer in the interview: "Where did you study?"
Me: "The Cherno University..."
Employer in the interview: "Where is that located?"
Me: "RUclips..."
Virtual functions are basically backups for functions. So it tells the complier that if a function is overwritten then it knows that it originally meant.
Super helpful gosh
Thanks for this - excellent refresher, and I learned a few new tidbits! Keep these coming.
Hey Cherno! Got to say great channel to learn c++, awesome channel to get used to the australian accent!! :)
Your videos are amazing tools for learning this stuff.
6 years later and I am still waiting for your VTable Video Cherno. 😆 I love your series. Please link me to the vtable video if there is one.
Wait wait wait... Why did I just understand virtual functions in one video. Dude you're good. Thanks man.
This is the C++ apocalypse. Probably one positive side effect of Chernobyl.
thanks Cherno
What is the difference between
Player(const std::string& name):m_name(name) {}
and
Player(const std::string& name) {
m_name = name;
}
Is it some kind of syntactic sugar?
Lightslinger Deadeye many thanks for your explanation!
There's no _real_ practical difference between the two, however there is a difference. Since m_Name is a class member which has the type std::string (which is stack-allocated), it will actually be instantiated twice in your second example (firstly with an empty string, and secondly copied from the name parameter), but only once in your first example (via the constructor's intiailiser). Definitely going to be a video on this in the future. :)
TheChernoProject thanks :)
+TheSunscratch Also you cannot use the first approach if the data member is static.
Does the compiler (with -O2 or -O3 ) optimize it so that there is no difference eventually?
this is virtually the best tutorial on youtube (:
Super easy explanation. Many thanks mate
thank you, i always come back to reference your videos.
Love u dude
More than 3 years now, still waiting for VTABLE video 😆
Hey. Thank you so much! Had been waiting for this :)
TheCherno, thank you for your great tutorials! Are you planning on making a tutorial on generic programming and C++ templates?
Excellent
This was perfect! Thank you 💕
I can't say how useful your series has been. My son is twelve and is into robotics and programming and switching from python to C++. He loves your series and I'm playing catchup to help him though I'm the one lagging behind. Thank you, and let me know, if you read this, if you ever considered doing something about OpenCV or anything machine learning? :-D
good videos, keep it up. so glad you dropped the backgroundmusic
Great explanation
If you're confused by this video and the next video... come back to it after watching more of his videos in the playlist. They are a bit out of order.
whew... that's a relief :D
Thanx man
ty
Can confirm, just revisited this and it makes so much more sense
You a life saver. keep up the good work!
Your hair reminds me of that scene in There's Something About Mary. You know which one.
Concise... Like always😊
So far your videos have been good. But this is the first one I do not like. You're using and refering way too much, you actually did not use at this point of the series. Initialationlits, the ->, randomly using a pointer with the keyword new as an object and so on. WAY too much new stuff that has not been covered yet.
Absolutely agree
Yes. Agreed! Please reorganize the playlist. At least put this tutorial after the -> tutorial and the new keyword tutorial. And as far as I can tell you still haven't done a dedicated tutorial to polymorphism so why refer to it here.
@@explorerofworlds512 the -> is essentially just a shorthand for dereferencing a struct or class pointer and then trying to access a member.
// declare a new pointer to a myClass object and then use new to allocate enough memory for it
myClass* myclass = new myClass();
myclass->some_func();
// is equivalent to
*(myclass).some_func();
@@masondaub9201 Yeah, i came back to it later. It makes a lot more sense after watching later tutorials. Like I said needs would be great to have the playlist rearranged a bit.
+
After surfing the internet for more than 10 minutes, and this tutorial was much more helpful.
guys this is the hardest in c++ so dont quit
Thanks for that timely and apt reminder! You got this all of you!!
Thank You!!
Cherno, you are an absolute legend!
Türkçe altyazı ekleyenin eline sağlık.
Thanks to the contributor for the Turkish subtitles.
player(const std:string& name):m_name(name){} // this is an example of initializer list
what a wonderful tutorial! Love it!
Genius level teaching.. 10/10
Okay Cherno... we get it... we are dumb. You happy now?
Guess I'll just have to watch more of your videos to understand these unexplained concepts, which I was going to anyways because you're the best teacher ever.
:D
I've watched alot of your series, and it's really good, I've learned alot so thank you. BUT this video is waay too fast, I just couldn't follow it 😢
yea he messed up with this video big time. he tried to be a hero and overcomplicate it too much
thanks
c++ community:
language gives us this feature😘. but it comes with 'cost' 🥺
javascript community:
we don't care about cost. we are rich 🥳
this is the best
After watching this I realised Java is so easy compared to cpp.
On the flip side, the ease of Java comes at the expense of the level of control and optimization that C++ gives you. I started out with Java and now, after getting used to C++, Java just feels so limited.
@@jscorpio1987 Java's strength is in enterprise application ,it's toolset and frameworks are perfect for that . Yes it doesn't have much control over small low level optimisation due to jvm ,but platform independence compensates it perfectly .
@@jscorpio1987 I also started with Java. And, even now, I still prefer Java over C++ but I see the strengths of it too. For example, anything related to graphics in Java to me seems like it hasn't really been thought about too much. Mean, games built with it are (usually) a lot slower and even basic interfaces are difficult to make. With C++, there are many more libraries built to help with this. While these libraries are often ported to Java, it just doesn't feel complete.
After looking at the sky I realized it's blue
Me using java: Why isn't this applet working? It worked last time I used java!
About 1.5 years ago...
2:39 that resignation in his voice lmao
dynamic polymorphism is factor 8 as opposed to static polymorphism. Use it at a high level and you won't notice. Make 100000 calls and you notice.
you are genius
I was wondering why you used the x->object style instead of x.object but it turns out that x.object won't use a vTable. Baby steps for me I guess.
Nice video, thanks bro
A+ video. Very helpful.
I dont get it... hard to understand at this point.
These videos started out so exceptionally great but it seems he has grown weary of this subject now, rushing through them and using unexplained code all the time.
Go review the video on Inheritance.. That should help you understand it better.
@@loveboat wat
There is Zero problem with this video. If you don't get it then you haven't actually practiced inheritance enough to learn why we needed the virtual functions in the first place. Just watching videos will never get you anywhere in programming. You will have to actually write the code, test it with all possible conditions you can think of, try to do illegal stuff and then understand why it is not working, is the only way you can truly learn any topic.
@@deleater I think he is not refering to virtual functions. Cherno introduced many other subjects in this video without explaining them, but all these are explained in future videos, so the only thing to take out of this video is the type "Virtual" subject
Congrats, fellow hacker, i recognise you as one of them 'Non-pasters', have a nice journey hooking them VMT-s!
A very basic question (coming from java).
Why do you write Entity* e = new Entity()? Why do you add that pointer * ?
Because the *new* keyword dynamically allocates memory and returns a pointer to the address of that allocated memory, hence why we need a pointer type. Check out my video on pointers if you haven't already, and I will definitely be making a video on memory allocation in the future.
I will just add that in Java classes are by default reference types, while in C++ everything is value type, so if you need to refere to the same value, then you need to use pointers. So you can use same class definition as reference or value type. For example if you have new class Vector (position) , and you pass it to function as Vector (by value) or as Vector * ( as pointer only). If you embed Vector in Entity you can embed entire Vector or only a pointer to Vector.
I have learned a lot from your videos. Can you create a tutorial on setting up C++ in Visual Studio Code? Visual Studio is still too heavy for me.
Hey Cherno! Are these tutorials going to be by the C++ 14 and up standart? I mean like will these tutorials be of modern C++?
Yup. Many of these will work on pre C++11, but most are C++24, especially the later videos, which are strictly C++14 and up
Not sure if this will get seen this many years later, but I have a quick question. Does this mean that we should always define all of the functions in the base class as “virtual” as a rule of thumb? Thank you for the videos yan love your content
pretty cool! ... well explained.
This is amazing, first time watching one of your videos and I'm in for more! Thanks!
Like the speed... Good.
awesome video man