The field y is not declared by class Checks. Reading static fields doesn’t trigger initialization of the referenced class (Checks), unless that class is the one in which the field is declared (see JLS quote below). In this example, even if y is accessed through Checks, that will only trigger the initialization of Par because … Read more
A .LIB file is a collection of .OBJ files concatenated together with an index. There should be no difference in how the linker treats either.
You’re basically referring to the section §7.3.1.1/2 from the C++03 Standard, The use of the static keyword is deprecated when declaring objects in a namespace scope; the unnamed-namespace provides a superior alternative. Note that this paragraph was already removed in C++11. static functions are per standard no longer deprecated! Nonetheless, unnamed namespace‘s are superior to … Read more
Instead of bar use self.bar or Foo.bar. Assigning to Foo.bar will create a static variable, and assigning to self.bar will create an instance variable.
Fundamentally this is because static members must be defined in exactly one translation unit, in order to not violate the One-Definition Rule. If the language were to allow something like: struct Gizmo { static string name = “Foo”; }; then name would be defined in each translation unit that #includes this header file. C++ does … Read more
No. You can’t have local static variables. From MSDN: C# does not support static local variables (variables that are declared in method scope). And here: The static modifier can be used with classes, fields, methods, properties, operators, events, and constructors, but it cannot be used with indexers, destructors, or types other than classes. As you … Read more
Yes, it does normally translate into an implicit if statement with an internal boolean flag. So, in the most basic implementation your declaration normally translates into something like void go( int x ) { static int j; static bool j_initialized; if (!j_initialized) { j = x; j_initialized = true; } … } On top of … Read more
Your description of a static variable is more fitting to that found in C. The concept of a static variable in Object Oriented terms is conceptually different. I’m drawing from Java experience here. Static methods and fields are useful when they conceptually don’t belong to an instance of something. Consider a Math class that contains … Read more
Unfortunately, it has different effects depending on where you use it. Static Functions: By default, all functions have a global scope. The static specifier lets you limit the function’s scope to the current file. Static Local Variables: When you use the static modifier on a local variable, the function “remembers” its value across invocations. For … Read more
You have answered your own question. Static initialization order is undefined, and the most elegant way around it (while still doing static initialization i.e. not refactoring it away completely) is to wrap the initialization in a function. Read the C++ FAQ items starting from https://isocpp.org/wiki/faq/ctors#static-init-order