The reason defining an external variable inside a function does not make sense is the following: When you declare a symbol extern, you are telling the compiler to link all such occurrences of this value into the same symbol. Any occurences of extern int i; in your program would link to the externally defined i. … Read more
Small correction – for success resolving name by clinet extern “C” must be as on export side as on import. extern “C” will reduce name of proc to: “_GetName”. More over you can force any name with help of section EXPORTS in .def file
When you talk about informing other readers, consider the compiler itself as a reader. If a variable is declared static, that can affect the degree to which optimizations kick in. Redefining a static variable as extern is impossible, but the compiler will (as usual) give you enough rope to hang yourself. If I write static … Read more
It’s because const implies internal linkage by default, so your “definition” isn’t visible outside of the translation unit where it appears. In this case, by far the best solution is to put the declaration (extern int const n;) in a header file, and include that in both a.cpp and b.cpp. The linkage is determined by … Read more
Because the variable isn’t odr-used. You have a constexpr if there that always discards the branch that could use it. One of the points of constexpr if is that the discarded branch need not even compile, only be well-formed. That’s how we can place calls to non-existing member functions in a discarded branch.
After a bit of googling I’ve found the official coding guidelines for Cocoa. To sum up: Start with a two- or three-letter prefix in ALL-CAPS Rest in UpperCamelCase Same criteria for extern constants I agree with itaiferber that the k prefix style is clearer and also much more useful for autocompletion. It would be interesting … Read more
static in Objective-C means a different thing than static in a C++ class, in the context of static class data members and static class methods. In C and Objective-C, a static variable or function at global scope means that that symbol has internal linkage. Internal linkage means that that symbol is local to the current … Read more
The ‘extern “C”‘ should not be required on the function defintion as long as the declaration has it and is already seen in the compilation of the definition. The standard specifically states (7.5/5 Linkage specifications): A function can be declared without a linkage specification after an explicit linkage specification has been seen; the linkage explicitly … Read more
Global variables are not extern nor static by default on C and C++. When you declare a variable as static, you are restricting it to the current source file. If you declare it as extern, you are saying that the variable exists, but are defined somewhere else, and if you don’t have it defined elsewhere … Read more
A function definition with static inline defines an inline function with internal linkage. Such function works “as expected” from the “usual” properties of these qualifiers: static gives it internal linkage and inline makes it inline. So, this function is “local” to a translation unit and inline in it. A function definition with just inline defines … Read more