inline variables (C++ 17 and beyond) | Modern Cpp Series Ep. 110

[@chillrelax5056]

Your videos are like masala chai! Refreshing and insightful!

[@MikeShah]

Hehe cheers!

[@sanjaygatne1424]

your videos are just awesome. makes the stuff easy to understand.

[@MikeShah]

Cheers!

[@qcnck2776]

Thanks. Looking forward to more C++ vids

[@MikeShah]

Cheers, more coming!

[@monty6393]

Thanks mike for the video..

[@MikeShah]

Cheers!

[@bffever8803]

your video is amazing ,i love it

[@MikeShah]

Cheers!

[@nicksklenicka8926]

Much appreciated.

[@MikeShah]

Cheers!

[@Byynx]

Hi can you explain why we can declare the var "static int SomeValue" and then write "int Struct::SomeValue=63" with the same syntax as if we were creating a variable? And is it because the compiler knows "SomeValue" var has to be initialized that the linker trys to find that initialilization in each source file and that's why it executes the line "int Struct::SomeValue=63" from "Struct.cpp" file?

[@MikeShah]

Struct::SomeValue is part of the scope (Struct:: that is). For static variables, you typically declare in the implementation (.cpp file) the value to build the symbol.

[@RobBCactive]

This could have been clearer, an example the main.c variable Struct s isn't apparently used and struct Struct with one member, is not concretely useful. Fundamentally the hpp file attempts to both declare the type and an instance of it, allocating static memory, while consts are replicatable compile time values so implicitly non-extern non global (not lvalues). When Struct.cpp was used static is meaninglessly contradictory as it wasn't in a function scope and it wasn't a file variable. How on earth is this cleaner? It just looks like hacking an erroneous data concept until it compiles. A hint is the compiler error message reminding that it considers Struct a class.