Відео

This is a fair criticism. This was a deliberate decision though. With CMake there are many ways to do things in an outdated way. I did not want to bring those up focusing on the current best practices to the degree of my knowledge instead.

@@hurainjinnath I’m using VS Code exclusively in this course.

@@hurainjinnath oh and there is also the standard macOS terminal

@@CodeForYourself thanks ☺

Sure, my pleasure!

@@toby9999 I don’t fully agree. The modern CMake infrastructure is actually not too complex anymore. The benefit is that this system is something that we can use across any system without attachment to a specific compiler or ecosystem. It is much easier to design something when you are in control on where it is used and that’s the benefit that MS has. That being said, I never grew to like any IDE and my experience with VS (many years ago) was not the best. I guess what I’m trying to say is that to each their own but we all can benefit from a cross platform solution that is flexible enough to satisfy needs of most.

Радий, що вийшло плюс/мінус зрозуміло! 🙏

@@arkadiuszszulc3303 I think I largely agree with you nowadays and that’s why in the recent videos I’ve done away with clocks altogether. That being said, it is a thing of personal preference and I do know people who prefer it with clicks because they like it aesthetically. It is hard to tailor to everybody. 😅 At this point I just hope it is not too distracting.

@@muhammedkocaer8373 thanks for the question! These are all confusing things. Let’s try to break them down. The pragma once is a preprocessor directive that can be seen by a # in front of it. This means that the compiler never sees it. Instead the preprocessor replaces it with some unique guard for this file so that when this file is included twice, it actually only gets included once. The include is also a preprocessor directive, so the compiler does not see it either. Instead, the preprocessor just textually replaces an include with the content of the underlying file. But only once because of the pragma once. Does this somewhat answer your question?

​@@CodeForYourself Now I get it. I asked this question as if it were performing a function task. But I forgot that it was a preprocessor. Thanks.

@@muhammedkocaer8373 awesome! Glad I could help!

@@mohammedkamil5320 ok, to me we seem to be quite different but I like these types of connections. What would you say is similar? 😅

@ interesting, I would say your face is mostly similar, but the other guy’s face is a bit more broad. I think you guys have mostly the same eyes, same nose and same mouth, except for the hair. I showed you both for some of my friends just to make sure that I’m not the only one and most of them agreed that you guys look similar to each other except for one or two, but they also agreed that you have similarities😁

@ I don’t mind at all. Maybe one day I’ll have as many subscribers too 😅

Please note that this video is intended for providing enough intuition for people who are not familiar with lambdas at all.

@@marwanzaghloul6065 thanks! Noted! 🙃

Just in case I can make anything clearer just tell 😉

@@bsdooby could be. Sounds logical. Would need to check

@@HomeofLawboy thanks so much! Every comment you guys make kinda brings this closer 😅🙏

@@Maximus98245 coroutines probably won’t happen. Everything else might 😉

@@CodeForYourself Yeah, coroutines are for library developers. Not something that can be explained in a 10-20 minute youtube video.

Don't forget modules. Which we will get. Eventually...

@@segfault4568 yes, absolutely! I hope to be able to get to it at some point. But as I mentioned before to properly talk about std::function I would kinda need to chat about type erasure and I’m not sure if I should or if I can do it in a simple enough way. Thinking about it anyway.

Yes, exactly. Let’s see if I get to record a video about this.

@@zamf thanks! All good points! I’m still mostly targeting C++17 here just to make sure I have something finished before moving on to new standards. So no goodies that you described. Also, I’m not trying to completely copy cppreference here. The aim is to give people enough knowledge to be able to dig further. Hope this explains a bit better some choices I make in these videos.

​@@CodeForYourself I agree. I just think that std::function is a good candidate for a future video as a follow up to this one.

@@zamf definitely. That video I really want to record at some point but a proper deep dive into how it works requires type erasure and I’m not sure how long it will take me to distill it into a manageable explanation 😅

The biggest issue with std::function is that it doesn't respect the const-ness (other than a smaller issue of it might need to allocate and takes up 32 bytes as opposed to 8 for function pointer) struct Functor { int x = 0; void operator()() { ++x; } }; const Functor func; //func(); // good, this will not compile const std::function<void()> stdfunc = Functor{}; stdfunc(); // compiles, I can mutate const std::println("stdfunc.target<Functor>()->x == {}", stdfunc.target<Functor>()->x);

@@Maximus98245 That is weird, I agree. But it's a similar behaviour to const pointers and even to const std::reference_wrapper. So not that unexpected. At least it modifies a local copy of the data, so nothing else in the program is modified.

@@viktordiadkov8768 thanks! Highly appreciate it! 🙌

@@Maximus98245 thanks! 🙏 You’re making a good point. I felt like this was more introductory video so skipped that. I probably should eventually talk about it but don’t know when I’ll manage. 😅

@@ozimandias1858 well, deprecated is a strong word for it, you’re right. But it is discouraged. The suggested way is to “live at head” as mentioned in their readme: github.com/google/googletest#live-at-head

@@ozimandias1858 they also only provide the fetch_content example in their docs: google.github.io/googletest/quickstart-cmake.html

Okay, thank you!

I guess the closest video to this would be this one on various STL containers: STL sequence containers (and friends) in modern C++ ua-cam.com/video/dwkSVkGsvFk/v-deo.html

I largely agree. Towards later videos I converged to a very different format.

Oh yes! That is a great idea! I wanted to make a video like that for a long time. It will take me a bit of time though as I have just started a new job and all my time is spent there for now. But I’ll get to it one of these days.

Glad I was of some help. One recommendation to debug this type of linking errors is to start small and try to get to the smallest reproducible example first. Good luck!

@@alperzobu9534 thanks for such a high praise!

Дякую за хороші відгуки! Стосовно змінних, загалом всі змінні в cmake це просто текст. І більшість цього тексту зберігається в кеші який потрібен для того щоб зберігати конфігурацію між запусками. А все інше про за я розказую то наслідки цього.

@@CodeForYourself Да, только момент с кешем не уловил. Все остальное кристально. Особенно понравилась презентация на гитхабе. Я вот раньше просто смотрел, ничего не повторяя. Сейчас Вы сказали "не тупить" и выполнить все самостоятельно. Начал это практиковать. Времени намного больше занимает, но после ощущение будто сам все сделал. А если вопросы есть, гпт использую. Еще раз спасибо :-). Подписка, лайк

@ozimandias1858 будьте обережні з гпт, адже він хронічно бреше. Будь які конкретні запитання можна також задавати тут або на гітхабі. Я відповідаю повільніше за гпт, але сподіваюсь що менше брешу 😅

Thanks for the compliments! Whenever you see code animations I use motioncanvas.io The rest of the animations, including the last diagram animation here about shared pointers, I make by creating images with the Apple's Freeform, import them into Davinci Resolve where I edit my videos, and do the rest of the animations there.

That is it make sure that when we call these functions we look up the actual functions to be called in the vtable. In the end of the example we pass a reference to an *IoInterface* object. So try to make sure you understand exactly what will happen when we call *Write* on such an object reference. Does this help?

​@@CodeForYourself I understand what you mean but in the video you used "void Write(const std::filesystem::path& path, const std::vector<Color>& data) const override { std::cout << "Writing PNG to path: " << path << std::endl; }" function but on github you used "virtual void Write(const std::filesystem::path& path, const std::vector<Color>& data) const override { std::cout << "Writing PNG to path: " << path << std::endl; }" function for both png and jpeg. I expected and understood first function but did not understand second one.

@@erkamkocaer2097 oh! Now I understand! Thanks for pointing it out! It's a bug I have on GitHub. We *can* have *virtual* and *override* for the same functions but generally we should just use *override* as the *virtual* is implied here. So basically what I'm trying to say is that *override* implies *virtual*. I'll remove *virtual* from my GitHub code as it was probably a copy-paste error on my side. Thanks again!

@@erkamkocaer2097 I've updated the code on GitHub to not have *virtual* in the last example. Thanks again for bringing it up!

@@CodeForYourself thank you for your attention. I like your cpp videos. They are really impressive.

Thanks a lot! Happy to hear it was useful!

That is a valid question. The main reason is that some people prefer a video format and a video allows me to do both, have a markdown article and a video. You can find the markdown under the video. The downside is of course that errors are harder to fix.

@@CodeForYourself I'm one of those people who prefers a video format and I appreciate the work you do. I truly believe if you keep up the good work this channel will explode within the programming community. I'm recommending it to all my co-workers.

@JaredAlanXyz thank you sooo much for these kind words. I haven’t had the time to properly record new videos lately. But a couple are in the pipeline. 🙏

@@JaredAlanXyz do you not find that to be an issue? if the only way or most efficient way you can learn today is via videos, you're now wholly dependent on youtube/internet and also the cadence at which the presenter rolls the video

@@PerriPaprikash I want to note that _all_ of the things I say in every single video is available as text (markdown) in this GitHub repository: github.com/cpp-for-yourself/lectures-and-homeworks So I hope that people are getting the best of both worlds - a video explanation + all of the text and code for offline reading. Finally, I just want to note that recording and processing a video is not my main time sink. It takes me roughly 2-3 evenings at this point. Designing what I want to talk about, how I want to present it, what examples I need to provide to make it intuitive enough but not overly simple takes a much longer time, sometimes weeks-worth of evenings after work and some weekends. I would need to do the same work for text-only tutorials.

@@richardbennett4365 Same explanation as for the first change. The blank T-shirt is the original recording and the “save the earth” one is the follow-up 😅

@@richardbennett4365 simple. I recorded everything and then, when editing found that the story wouldn’t add up. So had to re-record and add a part. But the old tshirt was already in the laundry basket 😅

@@segfault4568 yes, my experience exactly. That mess is exactly the reason for all the smart pointers 😬

@@leonardodosanjoschaves6204 awesome! Glad to hear it was useful and good luck!

@@leonardodosanjoschaves6204 happy to hear that! 🙏

Arena allocators definitely have their use! However, if we allocate a lot of objects we will quickly need to manage memory in complex ways. This lecture targets largely the default behavior for beginners. I believe that using the heap for allocations should be completely fine in most domains. Also, heap implementations benefit from years of optimization and as far as I know they basically use arena like allocations for small objects. That being said, if one really writes a safety critical application and cannot use heap memory at runtime then yeah, we’ll probably need to allocate stuff from an arena. Also, I don’t agree with putting garbage collection and smart pointers in the same row. They are very different mechanisms. Smart pointers are definitely reliable and in case of a unique pointer have nearly no overhead. So if one wants to allocate on a heap, smart pointers are definitely a way to go.

@@advik-b thanks for your kind words! Spread the word then. Let’s fix it. 😅

Glad you liked it! 🙏

Glad it was helpful! 🙏

Thanks! I’ll try my best 👌

@@SanjeevKumar-nm7ps thanks so much for your kind words! You make me blush! ☺️ Glad that it is useful to you! 🙏

Oh, that’s very easy. You just mess up in the script, spend a week editing, then see that it’s wrong and that you have to re-record parts. 😅

Not yet, but maybe some day once I finish a full course here.

Could you elaborate a bit on how unique_prt is obsolete? This is the first time I hear about it.

How is Unique pointer obsolete? it executes the same instructions as Raw pointer, same size as well, Scott Myers even recommended them to be used in tight cycles. Shared pointer though not to be confused with Auto GC is still a deterministic destructor so plenty useful, the only inefficient thing I can recall about Shared pointer is that it is twice the size because of control block pointer.

@@segfault4568 I have a similar view (thus my original question to the OP). As for the shared pointer the reference count is atomic if I remember correctly, which requires synchronization and therefore might cost additional resources and instructions.

Thanks! The font is Fira Code. The theme that you see in the animations is a custom one that more or less resembles the default vscode one.

@@CodeForYourself Thanks!

@@tirthasg sure, anytime!

Thanks so much! 🙏