For future videos, Cherno. 1:35 Stack and heap video 2:50 Why I don't like std namespace 7:40 The new keyword 10:10 Arrow operator 11:30 Smart pointer Now you can come back and put comments on your video. You're welcome :D - Love this series!
I think we'd try harder to motivate Cherno. I've tried really a little bit effort to be kinda TH-camr more then 3 years before. At that time, I even only have had a freelancer job, which means I had a lot more time then now, but still can not easiely keeps that on. So may be we should build a much better community around / based on this series, and do use the patreon thing to support Cherno. (I've checked out that discordapp, but really not get the point easiely)
I've been learning C++ for more than a year now, and you've just made me have a revelation with this one. It litteraly made me stop the video, grab onto my forhead and shout "I GET IT NOW!!!" out loud. It's like I've ascended, opened my third eye, activated all my chacras and connected to the cosmose all at the same time. Thank you!
Lol this was literally me I never really understood the { type* name=new type } until I finally got the difference between stack and heap. And then it just clicked. It really feels amazing when the confusions fades away and you can finally answer your questions yourself.
This is probably the best series I've found so far on TH-cam among all the series for learning different languages. You make it so easy, and you give just the right amount of information so that we feel like we know just enough about what's going on under the hood without also feeling bogged down by too much technical information.
I love the amount of videos you put out and I also love each single one of them! Keep up the great work, I'm so hyped for the in depth videos we are more and more getting in to!
Well, I even already "knew" all of the concepts so far, however it is a really nice reminder to see everything explained in such an order again. And for most of the parts you can learn something new too. Especially when it comes down to analyzing the generated assembly code underneath all the c++ stuff. Just to show what exactly happens internally. I love to know such things, without even considering if you might need them at any point. But when it comes down to optimization it is great to know how stuff will be like in assembly code so you can alter everything at your own pleasure.
Java/C#/Kotlin dev here. I also did my fair share of C, but never tried C++. Watching your videos now to learn a new language. The difference between "Entity()" and "new Entity()" has been an eye opener for me. It all makes so much more sense now! Nice job!
Cherno, I love your videos, anyways for completion of information, one of the main problems you may have forgot to mention about allocating on the heap with new operator, is that if an exception is thrown (and not properly caught) between the new and the delete operator, then the delete operator will never be called, thus never freeing that piece of memory from the heap. Thanks for the whole series tho, you made a wonderful job :)
Stack: → faster and better all around, if you can create an object on the stack then do it. → shorter lifespan then when allocated on the heap Heap: → If you need to extend the lifespan of the object outside of the function where it was defined, then allocate on the heap. → Use the new keyword to allocate on the heap → Anytime we use the new keyword, we must also use the delete keyword to clear that memory space when we are finished with the object.
I love this series. You don't hesitate to go a bit deep in every video, even short ones, and I love it. I think the reason is that you are speaking with all your professional knowledge in heart, while many other videos are taught by academics.
I'm an experienced developer with some C experience (in the distant past). But I'm finding these videos very helpful in learning C++ - much more so than the book I was reading, A Tour of C++. Even when they cover familiar topics, I always learn something new. I especially appreciate that you occasionally break out of C++'s abstractions to discuss their lower-level implications. I also have to say, having watched some other programming videos, that I appreciate the lack of dumb jokes.
I have found you are by far one of the best programming teachers on TH-cam. I was god awful at c++ and understood practically nothing until I started watching this series. Keep it up!
Seriously ur videos are the best in learning. Its more addictive than "The Breaking Bad". Also, I've to say the way of teaching is awesome. Video Quality and Audio Quality, Editing is awesome
I know most of C/C++, but your videos are soooo cool, fast and up to the point yet still very clear and understandable. Can you do a video about allocators (C++17 feature)?
Sorry if i am wrong and for my poor english .I thought we were overwriting a stackframe everytime because when you call a function this happens. -> push ebp (a general purpose register where you can save some value. the value gets saved so that it won't be overwritten) -> mov ebp, esp (copying the current stack address to that register which we moved so that we can come back to it) so now all the variables get allocated after this address, then after the function is done, this happens -> mov esp, ebp (NOTE: we saved the last address in ebp[ HERE is where the magic happens current address in esp will be overwritten with that old value we stored in ebp ]) -> pop ebp (restoring the value that was in the ebp before the function call )
“Lets create some code that will actually fail. “ Lol. I’m good at that. It’s a great teaching tool actually. We learn from our mistakes. Great video series. I’m learning a lot. Thanks for making this.
you got such good time management control, going just far enough off topic for it to satisfy first questions but not so far we lose track of where we were and was going ^^ you are really good, could easily be a lecture if you ever wanted to go that route ^^
8:42 May not be entirely true since heap allocation is only a language specification for Java, if you looked at HotSpot you'll notice a lot of heap and stack operations are just abstractions to register based allocation at the lowest level (Java really hates allocating to anything besides registers and if it really has no other choice, the native thread stack, for some reason)
So I'm understanding this right, you don't delete 'entity' because it went out of scope at the brace. But you can still delete 'e' because it's pointing to the right place on the heap?
Since I'm super rusty on C++ but planning to get back to it, this has been a great video to remind me (I sling c# by day). Great coverage of stack vs heap (I thought I was going to have to correct you on c# but you took care of it yourself heh).
10:11 😎. I think you pretty tell the main reason why C++ is so powerful, but still has its hard time on adoption in companys. If I say writing Javascript is like driving a normal car, then writing Java & C# is driving sport cars, ==> writing C++ code is no more about car-driving, we talk about fight-jet controlling! 🎁🚀 Another neat tutorial, Thanks Cherno, you are great, TH-cam is great, C++ is great, I love the world we created in Computers.
Awesome video! Could you talk about uniform initialization at some point soon? I think a lot of people might prefer using this method if they knew it existed :)
Great Videos as usual! You are a hero, sir! Just a quick side note, doesn't Java actually store the methods as well as the references to the objects in the stack (08:42)? Cheers!
10:10 "i'm getting tired of this " "but yeah.. moRE Videosss" it was so funny to me.. noticing how many times he has said that he will make videos about a topic which extends from the previous videos.
This is amazing! You teach better than school! A quick question - What happens if you do this - Entity& GetEntity() { Entity* entity = new Entity(); return *entity; } int main() { Entity e = GetEntity(); std::cout
Great explanation, thank you. Coming from a Java background, the different ways of instantiating and releasing objects in C++ has been a bit confusing.
instead of specifying "delete entity", could you have defined a destructor that deletes "this" and that way it is implicitly done any time you dynamically allocate space for instantiation of an object?
The main difference is the scope of #define vs using. #define can leak out of the scope whether or not it is written in middle of a class (as long as the header is included), rather than using, if you declare the latest in place of a class member for example this using definition will be only available in the scope of that class.
In C# local variable (even reference types i..e classes) are stored on the stack sortof ... well the address i, its instance variables/ members are on the heap.
It all finally clicked when you mentioned the variable scope in the function, I remembered each call as a new stack frame and it all clicked... if I need something outside of this scope, I will require something stored on the heap... what about function returns? Coming from Java this was super Confusing until this video. Thanks Cherno
Cherno: "If you CAN create an object like this in the simplest possible manner, then do create an object like this!" The creators of the ridiculously complex framework I heavily depend on: "I will NEVER create an object like this."
Java stores primitive type in stack, object in heap, though its not important since there are no pointer, JVM manages memory, and finalize(). C++ has to explicitly free memory. Python stores everything in heap except C functions.
4:20. Isn't there a difference between: Entity entity("Cherno"); and Entity entity = Entity("Cherno"); It seems to me that there should be. In the first case, the Entity object named entity is constructed using a string parameter "Cherno". In the second case, anonymous object is constructed with a string parameter "Cherno" and then that anonymous object is used as a parameter for a copy-constructor to construct the Entity object named entity. However, you haven't defined the copy-constructor, so the second one shouldn't work, but it works. How so? Does C++ just interprets the line Entity entity = Entity("Cherno"); as the constructor Entity(const String& name) is being used?
The other seems like you are assigning to entity object the string more directly... but it's the same, because it still calls default constructor. It's like if you were turning a bolt nut with two different brands of adjustable wrench. They both get the job done the same way, but one wrench looks different on the outside from the other.
So the heap is like the pile of junk in the corner of the room. The stack is the things that sit on my desk. The difference is that I trash the things that sit on my desk when I'm done with them. This can't be said for the junk on the other side of the room.
I think one major reason for choosing heap vs. stack wasn't mentioned here. Even if the size isn't too big for the stack, if we don't know the size at compile time, then it should be allocated on the heap. Mainly an issue for arrays.
I did the option and went from c++ to c#, and I certainly remember wondering why all of a sudden EVERYTHING had to be instantiated with new which I rarely do in c++ lol
When a topic is as vast as a programming language, with this type of approach (very much in style of Bjarne's Tour of C++ only way more comprehensive ) you have to wave your hand at a bunch of of other related topics.
Tested the Entity pointer thingie at 6:33 as in the below, but it seems e2 still holds the name! Entity* e2; { Entity entity2("Entity2"); // created on the STACK e2 = &entity2; std::cout
Soo, I'm a bit late to the party, but I do have a question: How do you handle heap de-/allocation within functions? Let's suppose you have a function that allocates memory on the heap and then returns a pointer to that object. Is there some convention to signal the user that "this function allocates memory, remember to free the result"? Is it generally considered bad to even do that? Another question I have: For my first job, we were mostly coding with ObjectPascal. It was considered a sin to not immediately follow up an instantiation with a try/finally that ensures the memory is always freed. Would you do the same in C++?
because on line 22 "entity" is assigned to "e" both pointers now point to the same memory location After line 22, you could also get rid of the pointer as follows: 22 e = entity; 23 entity = nullptr;
Hi Cherno, I have another question for you.... You showed two ways of scope instantiating objects. They are "ClassName objName(8)" and "ClassName objName = ClassName(8)". But quite often I see the following sintax: "ClassName objName = 8" Is this the same as the others?
finally i know how to do that class Location{} class Zone{ public: Zone(){ a[0]=new Location(4,2); b[1]=new Location(3,2); } Location** a=new Location*[20]; }
For future videos, Cherno.
1:35 Stack and heap video
2:50 Why I don't like std namespace
7:40 The new keyword
10:10 Arrow operator
11:30 Smart pointer
Now you can come back and put comments on your video.
You're welcome :D - Love this series!
I think we'd try harder to motivate Cherno. I've tried really a little bit effort to be kinda TH-camr more then 3 years before. At that time, I even only have had a freelancer job, which means I had a lot more time then now, but still can not easiely keeps that on. So may be we should build a much better community around / based on this series, and do use the patreon thing to support Cherno. (I've checked out that discordapp, but really not get the point easiely)
he made all of EM!
@@iyappansriram9854 But he forgot to put it inside the card :-(
Still not there :(
@@prototy :(
I've been learning C++ for more than a year now, and you've just made me have a revelation with this one. It litteraly made me stop the video, grab onto my forhead and shout "I GET IT NOW!!!" out loud. It's like I've ascended, opened my third eye, activated all my chacras and connected to the cosmose all at the same time. Thank you!
yup we tapped into C++ Akashic Record
@@exoticcoder5365 🤣🤣🤣🤣
Lol this was literally me I never really understood the { type* name=new type } until I finally got the difference between stack and heap. And then it just clicked. It really feels amazing when the confusions fades away and you can finally answer your questions yourself.
and what would be the piece of knowledge that enlightened you?
Arent we all
Cherno: "That's the end of Cherno."
Me:"NOOOOOOOOOOOOOOOOO!!!!!"
Cherno:"I am still here though"
Me: "Oh thank GOD"
Imagine that's how he ended his channel
Screaming Michael reference
Better series than Game of Thrones
AMEN
Not really, but it's close!
You bet
As if it was hard to achieve
this comment made my day.
you don’t even realize how much this short video helped me understand what I’ve been learning for months
This is probably the best series I've found so far on TH-cam among all the series for learning different languages. You make it so easy, and you give just the right amount of information so that we feel like we know just enough about what's going on under the hood without also feeling bogged down by too much technical information.
I love the amount of videos you put out and I also love each single one of them! Keep up the great work, I'm so hyped for the in depth videos we are more and more getting in to!
could be more in my opinion xD i understand his hints fast and i dont Need Long to adapt them
Well, I even already "knew" all of the concepts so far, however it is a really nice reminder to see everything explained in such an order again. And for most of the parts you can learn something new too. Especially when it comes down to analyzing the generated assembly code underneath all the c++ stuff. Just to show what exactly happens internally. I love to know such things, without even considering if you might need them at any point. But when it comes down to optimization it is great to know how stuff will be like in assembly code so you can alter everything at your own pleasure.
im an old rabbit in c++ too but its a really nice refresh
That's what I was about to comment XD Every week was too long ;-; WE NEED IT EVER 12 HOURSS! but actually quality > quantity of course :)
Java/C#/Kotlin dev here. I also did my fair share of C, but never tried C++. Watching your videos now to learn a new language. The difference between "Entity()" and "new Entity()" has been an eye opener for me. It all makes so much more sense now! Nice job!
Cherno, I love your videos, anyways for completion of information, one of the main problems you may have forgot to mention about allocating on the heap with new operator, is that if an exception is thrown (and not properly caught) between the new and the delete operator, then the delete operator will never be called, thus never freeing that piece of memory from the heap. Thanks for the whole series tho, you made a wonderful job :)
Thanks for the video man! Watching your videos has become a part of my daily routine.
same here
Even after 2yrs, same here as well
Dude you are so entertaining to watch. The amount of value you have added to thousands of people's lives through these videos can't be fathomed.
I'm gonna start a list with all the concept 'he's gonna make a video about', this series will be HUGE (keep up the good work)
There must be over 50 at this point
Mathew McCloskey probably close, yeah
Hahaha I'm not the only one who's thought about this
Stack:
→ faster and better all around, if you can create an object on the stack then do it.
→ shorter lifespan then when allocated on the heap
Heap:
→ If you need to extend the lifespan of the object outside of the function where it was defined, then allocate on the heap.
→ Use the new keyword to allocate on the heap
→ Anytime we use the new keyword, we must also use the delete keyword to clear that memory space when we are finished with the object.
thanks
Nice
*My takeaways:*
Scope could be function, if statement, for loop or even empty scope (i.e. { } ) etc 4:51
I love this series. You don't hesitate to go a bit deep in every video, even short ones, and I love it. I think the reason is that you are speaking with all your professional knowledge in heart, while many other videos are taught by academics.
I'm an experienced developer with some C experience (in the distant past). But I'm finding these videos very helpful in learning C++ - much more so than the book I was reading, A Tour of C++. Even when they cover familiar topics, I always learn something new. I especially appreciate that you occasionally break out of C++'s abstractions to discuss their lower-level implications. I also have to say, having watched some other programming videos, that I appreciate the lack of dumb jokes.
I have found you are by far one of the best programming teachers on TH-cam. I was god awful at c++ and understood practically nothing until I started watching this series. Keep it up!
Finally, the best way to understand dereferencing, stack and heap allocation! Best video of all the series so far!
Seriously ur videos are the best in learning. Its more addictive than "The Breaking Bad". Also, I've to say the way of teaching is awesome. Video Quality and Audio Quality, Editing is awesome
I wander when we'll be getting back to the Log project we made earlier on. 10/10 video once again here. Loving the content. C++ sensei.
I love that you always compare it with Java, this helps me understand it better! Thank you so much for all this free videos, it's gold for me!
this is the highest quality of tutorial on a programming topic on utube
I know most of C/C++, but your videos are soooo cool, fast and up to the point yet still very clear and understandable.
Can you do a video about allocators (C++17 feature)?
Sorry if i am wrong and for my poor english .I thought we were overwriting a stackframe everytime because when you call a function this happens.
-> push ebp (a general purpose register where you can save some value. the value gets saved so that it won't be overwritten)
-> mov ebp, esp (copying the current stack address to that register which we moved so that we can come back to it)
so now all the variables get allocated after this address, then after the function is done, this happens
-> mov esp, ebp (NOTE: we saved the last address in ebp[ HERE is where the magic happens current address in esp will be overwritten with that old value we stored in ebp ])
-> pop ebp (restoring the value that was in the ebp before the function call )
Broo, I've been programming for some years now, but still there's a lot of new things that I'm keep learnig from this guy!!!! really good content!
“Lets create some code that will actually fail. “ Lol. I’m good at that. It’s a great teaching tool actually. We learn from our mistakes. Great video series. I’m learning a lot. Thanks for making this.
you got such good time management control, going just far enough off topic for it to satisfy first questions but not so far we lose track of where we were and was going ^^
you are really good, could easily be a lecture if you ever wanted to go that route ^^
I'm liking that you're starting to pick up the pace with this series!!!
8:42 May not be entirely true since heap allocation is only a language specification for Java, if you looked at HotSpot you'll notice a lot of heap and stack operations are just abstractions to register based allocation at the lowest level (Java really hates allocating to anything besides registers and if it really has no other choice, the native thread stack, for some reason)
I love how it's not just "This is how do it" like other tutorials on youtube
We're getting there! This series are a authentic practical C++ book ;D
"It's gonna be in the HaHa"
This was pure gold.
So I'm understanding this right, you don't delete 'entity' because it went out of scope at the brace. But you can still delete 'e' because it's pointing to the right place on the heap?
You made me start loving c++ 🤩. Thank you so much 💕
1:30 you actualy made it :) add the card
oh a bunch missing, oh, 11:30 lol
The amount of videos makes me feel like it's Christmas when i was still a kid! they are top notch as always keep it up!
What on earth is that default constructor syntax (at around 4:00)? Why is the string assigned in that weird way?
He's way better in teaching than my computer teacher. And he looks much better too.
I'll be coming here more often than my actual computer class xD
God this series is so good! Perfect blend of knowledge and humor. Great work Cherno!
Every time I watch this video I understand more, probably the most useful / richest lesson so far!
man, i really love your videos. You're such a great teacher
Greetings from Guadalajara
Hi Cherno, Please start a series with Data Structures and Algorithms.
Good idea
Check out 6:25 The code :std::cout
Will you ever get through a video where you don't say "I will cover more on this in a later video" haha. Good work though so far, loving the series!
Well C++ has more features than you can possibly imagine.
It's an extremely complicated language.
Thank you Man, you are good tutor, as java dev, i find this vidéo very important.
Since I'm super rusty on C++ but planning to get back to it, this has been a great video to remind me (I sling c# by day). Great coverage of stack vs heap (I thought I was going to have to correct you on c# but you took care of it yourself heh).
Straight to the point. Thank you for the clear explanation!
Awesome video. Very explanatory!! Thanks for posting these. These are very good explanations.
Being the C# chad that I am, you had me at 8:03.
Fantastic video Cherno
Saving my ass once again the night before my exam. Thanks a lot, man!
Best managed C++ series!
cherno i love you man
10:11 😎.
I think you pretty tell the main reason why C++ is so powerful, but still has its hard time on adoption in companys.
If I say writing Javascript is like driving a normal car, then writing Java & C# is driving sport cars, ==> writing C++ code is no more about car-driving, we talk about fight-jet controlling! 🎁🚀
Another neat tutorial, Thanks Cherno, you are great, TH-cam is great, C++ is great, I love the world we created in Computers.
hey thecherno, reminder to add the smart pointer card 11:30
Great you solved one headache for me, thanks
Cherno is better than my whole university
Awesome video! Could you talk about uniform initialization at some point soon? I think a lot of people might prefer using this method if they knew it existed :)
Great Videos as usual! You are a hero, sir! Just a quick side note, doesn't Java actually store the methods as well as the references to the objects in the stack (08:42)? Cheers!
Exceptionally useful video.
Many Thanks for sharing your knowledge.
I don't know what the hand stuff is, got me every time :)
10:10
"i'm getting tired of this "
"but yeah.. moRE Videosss"
it was so funny to me.. noticing how many times he has said that he will make videos about a topic which extends from the previous videos.
This is amazing! You teach better than school!
A quick question -
What happens if you do this -
Entity& GetEntity() {
Entity* entity = new Entity();
return *entity;
}
int main() {
Entity e = GetEntity();
std::cout
Great explanation, thank you.
Coming from a Java background, the different ways of instantiating and releasing objects in C++ has been a bit confusing.
Once again, you have saved me tons of time and googling
instead of specifying "delete entity", could you have defined a destructor that deletes "this" and that way it is implicitly done any time you dynamically allocate space for instantiation of an object?
The Cherno's Future Videos are like promises with the keyword const
2:40 what is the difference between using String = std::string; & #define String std::string?
The main difference is the scope of #define vs using. #define can leak out of the scope whether or not it is written in middle of a class (as long as the header is included), rather than using, if you declare the latest in place of a class member for example this using definition will be only available in the scope of that class.
@@Arwahanoth got it, thx very much
@@sakuraema914 it is also semantic, using is meant for things like it. Macros are way more powerful than using. Keep it simple.
my favorite programming language! sea pluspus
In C# local variable (even reference types i..e classes) are stored on the stack sortof ... well the address i, its instance variables/ members are on the heap.
your channel deserve million subs at least.
so much soon video, cant wait!
It all finally clicked when you mentioned the variable scope in the function, I remembered each call as a new stack frame and it all clicked... if I need something outside of this scope, I will require something stored on the heap... what about function returns?
Coming from Java this was super Confusing until this video.
Thanks Cherno
Cherno: "If you CAN create an object like this in the simplest possible manner, then do create an object like this!"
The creators of the ridiculously complex framework I heavily depend on: "I will NEVER create an object like this."
Would absolutely love to see *"more videos!"* )) 10:15
Java stores primitive type in stack, object in heap, though its not important since there are no pointer, JVM manages memory, and finalize(). C++ has to explicitly free memory. Python stores everything in heap except C functions.
"It'll be in the... Haha I'm done"😂
at 4:20, doesn't that create two Entities and copy one into the other technically? Just curious what the difference is.
4:20. Isn't there a difference between:
Entity entity("Cherno");
and
Entity entity = Entity("Cherno");
It seems to me that there should be. In the first case, the Entity object named entity is constructed using a string parameter "Cherno". In the second case, anonymous object is constructed with a string parameter "Cherno" and then that anonymous object is used as a parameter for a copy-constructor to construct the Entity object named entity. However, you haven't defined the copy-constructor, so the second one shouldn't work, but it works. How so? Does C++ just interprets the line
Entity entity = Entity("Cherno");
as the constructor Entity(const String& name) is being used?
Your putting a string to Entity constructor and assigning it to the object entity.
I don't see how it could be different syntactically.
The other seems like you are assigning to entity object the string more directly... but it's the same, because it still calls default constructor.
It's like if you were turning a bolt nut with two different brands of adjustable wrench. They both get the job done the same way, but one wrench looks different on the outside from the other.
So the heap is like the pile of junk in the corner of the room. The stack is the things that sit on my desk. The difference is that I trash the things that sit on my desk when I'm done with them. This can't be said for the junk on the other side of the room.
Is it correct to say that allocating on the stack is ~= temporary, and allocating on the heap is ~= permanent unless explicitly destroyed?
u are my new god
I think one major reason for choosing heap vs. stack wasn't mentioned here. Even if the size isn't too big for the stack, if we don't know the size at compile time, then it should be allocated on the heap. Mainly an issue for arrays.
I primarily code in Java. I was about to go insane but got saved by your video.
So, Java is easier?
@@sleepyNovember_project Way easier than C++.
@@sleepyNovember_project Yes bro. It is way easier than C++.
Why did his intro sound exactly like @happydaysgames 😂
drinking game! take a shot whenever cherno says 'im gonna make a video about...'
Great video.
Keep making them.
Thank you for these tutorials :)
I did the option and went from c++ to c#, and I certainly remember wondering why all of a sudden EVERYTHING had to be instantiated with new which I rarely do in c++ lol
When a topic is as vast as a programming language, with this type of approach (very much in style of Bjarne's Tour of C++ only way more comprehensive ) you have to wave your hand at a bunch of of other related topics.
Thank you so much sir ! You helped me so much!
Bro you are awesome!
if I create integer pointer using new keyword should I also have to delete it at the end of scope or when we done with it?
Tested the Entity pointer thingie at 6:33 as in the below, but it seems e2 still holds the name!
Entity* e2;
{
Entity entity2("Entity2"); // created on the STACK
e2 = &entity2;
std::cout
Soo, I'm a bit late to the party, but I do have a question:
How do you handle heap de-/allocation within functions?
Let's suppose you have a function that allocates memory on the heap and then returns a pointer to that object.
Is there some convention to signal the user that "this function allocates memory, remember to free the result"?
Is it generally considered bad to even do that?
Another question I have:
For my first job, we were mostly coding with ObjectPascal. It was considered a sin to not immediately follow up an instantiation with a try/finally that ensures the memory is always freed.
Would you do the same in C++?
i knew this, but these videos are a great review!
Why at 10:31 on line 27 you are deleting e instead of Entity? Entity is heap allocated ptr not e? Please help me understand it Thanks.
because on line 22 "entity" is assigned to "e"
both pointers now point to the same memory location
After line 22, you could also get rid of the pointer as follows:
22 e = entity;
23 entity = nullptr;
@@sleepyNovember_project thank you buddy
Thanks for the video
Hi Cherno, I have another question for you....
You showed two ways of scope instantiating objects. They are "ClassName objName(8)" and "ClassName objName = ClassName(8)".
But quite often I see the following sintax: "ClassName objName = 8"
Is this the same as the others?
finally i know how to do that
class Location{}
class Zone{
public: Zone(){
a[0]=new Location(4,2);
b[1]=new Location(3,2);
}
Location** a=new Location*[20];
}