Absolutely brilliant! The entire series is so well made!

I wish I had a professor like you in Uni. Would you please include the use of "placement new" in some episode? Thanks

I couldn't understand "It doesn't live on the stack nor heap but in the executable" because from what I have understood, When the program is executed it will be loaded to the stack. Maybe I'm missing something and hope I can find it. But I could understand how static keyword works from a high level perspective. Very neatly explained as always. Thank you.

Could you do a course on the contents of an executable and also how the executable is executed by the os ?

So a static s_thing is basically a confined global_thing. It exists from start to end of the program and is effectively handled by reference rather than a value copy, but it is only accessible by the local scope where it was declared (whether the scope is a simple block{}, function definition, class, or compilation unit). I don't fully understand the implications for linking behavior, although some experimenting may clarify it. If starting with main.cpp func.hpp func.cpp someother.cpp and func() has a "static s_variable" in its definition, will calling func() in both main.cpp and in someother.cpp access the same s_variable memory address? In otherwords will s_variable actually be created in func.o so a call from any number of other compilation units will access the same instance of s_variable? Then I get to the question of a header defined function or class containing static s_var2, will that cause multiple unassociated instances of s_var2 if the header is included in multiple compilation units?

Hallo Mike, I have so loved the topic. Great pictorial explanation ! But i did not get why the s_variable didnt increment when you remove the static qualifier. what do you mean by the variable static is save in the Binary? Looking forward for your explanation.

Great discussion on the static keyword but I'm curious as to what happens under the hood when the ` static int x = 0 ` is executed each time. Does the compiler throw out initializations after the first instantiation? This is in reference to my comment on the Singleton design pattern. I think ultimately the take home point is that now matter how many times a static variable is instantiated, only the first is concrete.

Hum , watched the video again and have a flair of what is happening. what would happen if declare const, which means you can not reassign a value to it as you did in main. What if declared glabally? we were thought at school that static member variable is shared between the objects of the same class

Mike, do plan on teaching assembly?