In the definition in the .cpp file, remove the keyword static: // No static here (it is not allowed) std::string neighborAtt::intToStr(int number) { … } As long as you have the static keyword in the header file, the compiler knows it’s a static class method, so you should not and cannot specify it in the … Read more
You will have to initialize the static variable in a .cpp file and not in the class declaration. When you declare a static variable in the class, it can used without instantiating a class. //Header file class Test { public: static int j; }; //In cpp file //Initialize static variables here. int Test::j = 0; … Read more
Try an extension method instead: public interface IMyInterface { string GetClassName(); } public static class IMyInterfaceExtensions { public static void PrintClassName<T>( this T input ) where T : IMyInterface { Console.WriteLine(input.GetClassName()); } } This allows you to add static extension/utility method, but you still need an instance of your IMyInterface implementation. You can’t have interfaces … Read more
I don’t believe GNU ld has any such options; Ulrich must have meant objcopy, which has many such options: –localize-hidden, –localize-symbol=symbolname, –localize-symbols=filename. The –localize-hidden in particular allows one to have a very fine control over which symbols are exposed. Consider: int foo() { return 42; } int __attribute__((visibility(“hidden”))) bar() { return 24; } gcc -c … Read more
You cannot override static methods or fields of any type in Java. public class User extends BaseModel { static String table = “user”; //snip } This creates a new field User#table that just happens to have the same name as BaseModel#table. Most IDEs will warn you about that. If you change the value of the … Read more
To restate the problem: you want your per-file-type classes to have statically available information on the type (e.g., name and description). We can easily get part-way there: create a separate class for your type info, and have a static instance of this (appropriately instantiated) in each per-file-type class. package myFileAPI; public class TypeInfo { public … Read more
The non-static inline function declaration refers to the same function in every translation unit (source file) that uses it. The One Definition Rule requires that the body of the function definition is identical in every TU that contains it, with a longish definition of “identical”. This is usually satisfied provided that the source files all … Read more
First of all, Xaqron makes a good point that what you’re talking about probably doesn’t qualify as caching. It’s really just a lazily-loaded globally-accessible variable. That’s fine: as a practical programmer, there’s no point bending over backward to implement full-on caching where it’s not really beneficial. If you’re going to use this approach, though, you … Read more
It just follows a design guideline, that classes that contain only static methods should be marked as static. More information can be found here. There is no problem in making your Program class not static, the only thing that is required is the static Main method as an entry point, as you’ve already noticed. You … Read more
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