😂

Lol

Useless comment stating the obvious

Gilpow he’s just being a nice guy and giving Cherno a compliment. Which is something we need more of in this cold, heartless world.

there isn't any real competition!!!!

@gilpow check thenewboston, you will be forced to take back your words.

@@jscorpio1987 *brainless world.

→The delete keyword also calls the destructor.

best comment

- The* Charno* The Great! xD

It's really true if you just want something that works use python or some other language. Coding isn't about "pick your favourite language and stick to it". You pick the language that's best for what you're doing

Sai Surisetti I think I don't fit the criteria... I started learning C++ because it has more data structures than Python, it's a common language and Python hates recursive functions. Python has that nasty recursion limit of 1000. And even if I increase that limit (with setrecursionlimit function), it won't go to 50,000.

@@darkbolt333 I started learning C++ because it worked with hardware the best, for arduino. But then when I really got started with C++ I loved the syntax and I hate the Python syntax.

just here to learn the syntax for fun idk might be going to jail now

We talk about in soon™

One day it will be complete!

Don't give him a hard time :D, I'm sure he'll go over the advanced topics once he's gone through the basics. As he said, he's trying to make the series as perfect as he wants

no worry, take your time, excellent video as usual

..or he could make one 10 hour video that no one would watch and get it all in one shot.

Well unless the program is selected by the user at the time. I read that every process in the computer is being maintained by the cpu just flopping through them very very quickly over and over; programs unselected by the user are just put on pause if they have that feature in them, I guess.

Those are actually about data structures, it's not something about the C++ itself.

I wouldn't say they are "really important". Yes, they are a phenomenal way to implement sequential data when you know you will be performing many insertions and concatenation. As well as when you want to implement something like a tree. But in day to day you are either going to use them because they are your language's preferred way to handle lists, like Haskell or Scala. Or you are not really going to use them very much. They actually tend to get overused by beginners. Since when all you have is a hammer everything looks like a nail. Most of the time a Dynamic Array (So a Vector in C++) is what we really want. You wouldn't default to storing you data in a linked list unless you have a particular optimization or algorithm in mind you would want to use

but you can use free()

+Роман Капуста yes

He just said "A Integer is 4 bytes" for us to imagine how that stuff works. Not to specifically declare "YES! A INTEGER IS 4 BYTES EVERYTIME"

I can't speak for his mind, only what some proportion of viewers will take from that. His videos are excellent but it's better for someone to point out the small stuff that could lead to hours of confusion for lots of people down the line.

Good point! My mistake.

For people who are coming from a managed language, C++ by itself is pretty confusing and complicated. We need to learn such things at some point, but I think a beginner-series is the wrong place for such a conversation. If I happen to debug a program and I notice some unexpected behaviour from the program, I will search for the reason and learn more details. This will lead me to being a more skilled programmer over time. But for now, simplification has to be done, otherwise I (and many others) will give up and be frustrated.

I disagree, debugging is a great way to learn but that doesn't mean you should purposefully make life harder over trivial matters. It's a tiny thing to bear in mind, datatypes are given a minimum range by the standard and not an exact size. You remember something like that early and on then you spend your hours debugging more interesting things, than finding out that you've expected the size to be 4 bytes because all the books and videos you learnt from said it was 4 bytes. A beginner series should cover the fundamentals in some depth so that you have a foundation upon which to build your knowledge base. A beginner series is not the place for poor examples and obscurity, even if you appreciate the value of learning from debugging. A matter of opinion but there are all too many tutorials favouring your side of the fence and not enough favouring ours. This was one of very few oversights in this series thus far(in time, not just up to this video) and to point out the small issues that could be misleading or unhelpful does not diminish his content. If anything, a good comment section with good discussion is just as important as having good content. It's easier to trust content when it is followed by good discussion and it is easier to trust your knowledge when any bad habits or misguided ideas when are being pointed out by the audience.

lmao

delete(); After it... it's old. You can do like: #define delete old (not serious advice)

it got deprecated. ;)

hello dad

"this" is not the new keyword. "new" is the new keyword. "this" is used to refer to the object currently being considered. Hope that helped!

malloc doesn't call the constructor

Any time creates a brand new func or class, he calls them definitions. There's a difference between Def and init/declaration

Thanks. Good point =)

Yes, when we start talking about cross-platform development.

TheChernoProject Awesome! Love your videos, keep it up!

Yes, there is

Thread stacks are usually native, it's usually heap allocations that need the OS's help