Cherno: "That's the end of Cherno." Me:"NOOOOOOOOOOOOOOOOO!!!!!" Cherno:"I am still here though" Me: "Oh thank GOD"

Better series than Game of Thrones

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'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!

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 KZfaq 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 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.

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.

*My takeaways:* Scope could be function, if statement, for loop or even empty scope (i.e. { } ) etc 4:51

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 liking that you're starting to pick up the pace with this series!!!

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 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!

Thanks for the video man! Watching your videos has become a part of my daily routine.

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!

Awesome video. Very explanatory!! Thanks for posting these. These are very good explanations.

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!

Straight to the point. Thank you for the clear explanation!

I have found you are by far one of the best programming teachers on KZfaq. I was god awful at c++ and understood practically nothing until I started watching this series. Keep it up!

You made me start loving c++ 🤩. Thank you so much 💕

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

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 ^^

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!

Fantastic video Cherno

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)

Finally, the best way to understand dereferencing, stack and heap allocation! Best video of all the series so far!

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.

We're getting there! This series are a authentic practical C++ book ;D

man, i really love your videos. You're such a great teacher Greetings from Guadalajara

Exceptionally useful video. Many Thanks for sharing your knowledge.

Great video. Keep making them.

Thank you so much sir ! You helped me so much!

this is the highest quality of tutorial on a programming topic on utube

Thank you for these tutorials :)

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)?

Great you solved one headache for me, thanks

Thanks for the video

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).

Every time I watch this video I understand more, probably the most useful / richest lesson so far!

Bro you are awesome!

so much soon video, cant wait!

Amazing, thanks

“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.

cherno i love you man

Once again, you have saved me tons of time and googling

"It's gonna be in the HaHa" This was pure gold.

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 )

i knew this, but these videos are a great review!

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 :)

I love how it's not just "This is how do it" like other tutorials on youtube

Best managed C++ series!

Thanks !

Hi Cherno, Please start a series with Data Structures and Algorithms.

great video!🤫

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!

u are my new god

I don't know what the hand stuff is, got me every time :)

Pure quality

Great explanation, thank you. Coming from a Java background, the different ways of instantiating and releasing objects in C++ has been a bit confusing.

Saving my ass once again the night before my exam. Thanks a lot, man!

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!

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

The Cherno's Future Videos are like promises with the keyword const

reallly good

your channel deserve million subs at least.

my favorite programming language! sea pluspus

Make a list of future video card things: - Video title, ID: timestamps with card and subject that way you can fill them in later quite easily :p

you're just great

"It'll be in the... Haha I'm done"😂

Would absolutely love to see *"more videos!"* )) 10:15

Hi Cherno, thanks for the videos! In C # when changing a struct's member variable the entire struct is copied over again, that's why structs should be limited in size < 28bytes. This is not true with classes on the heap. Is this similar in C++? If I change a member variable of a class on the stack is the entire class recreated?

drinking game! take a shot whenever cherno says 'im gonna make a video about...'

Quick question, so does the new keyword change that which it precedes into a memory address? At least in this case. i.e. Is "new Entity("Cherno")" an address of the location of that object? Thanks.

When you allocate a class instance on the heap, are methods and attributes automatically allocated there as well?

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.

Hi Cherno, thanks a lot for the video. I have a question for you. Is there any fundamental diference between instantiating an object with the "new" keyword like you did and with the "static" keyword like in "static ClassName objName"? Apart from in this second you can never delete the object, is there any other fundamental diference? I imagine that static variables are also stored in the heap. Aren't they?

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)

When I create a scope within a function, eg the main function, is that also a stack that later gets popped?

Nice video, really informative, charno

What on earth is that default constructor syntax (at around 4:00)? Why is the string assigned in that weird way?

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?

No music at the end. BTW really enjoying tutorials!!

Being the C# chad that I am, you had me at 8:03.

Hey there mate! I am from Melbourne too...In Entity class why did you declare the return type as "String&" and not "String", when all the method was doing is to return the the data member that is a string?

You forgot to insert the music at the end haha (That was a nice ending music tho, I was expecting to hear that)

If you allocate an obj on the stack you won't be able to use late binding, correct?

So how much of a performance hit is it really to allocate on the heap? I come from java and oh boi you are creating a shit ton of classes on the heap all the time, but it is still decently fast.

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

So does it mean that language like Java/C# allocates everything in heap and it would then also mean that CACHE miss is something that is default in Java/C# (Because they store nothing in Stack and hence caching the item is not possible) which makes them implicitly slower than C++. P.S: C# allocates struct in Stack and not in Heap

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?

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

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, KZfaq is great, C++ is great, I love the world we created in Computers.

In a game that I am making I have stored the data of each item in the heap. All the alocation is being done before the game even starts( so there are no lagging problems ) and there is also no need to delete them since the setUp function ( the function that creates every idivindual item ) is not being repeated. Do you thing that this is a good way of storing them? should be storing them in stack instead?

you should post a card at the beggining of the c++ list with a link to this for people that are used to c# and JAVA

Is it correct to say that allocating on the stack is ~= temporary, and allocating on the heap is ~= permanent unless explicitly destroyed?

C# introduced stackalloc a while back, so you can allocate some things on the stack.

LOL "I don't know what this hand stuff is" neither me bruh xD