The main purpose of interfaces is to provide a type and a vocabulary of operations (methods) on that type. They’re useful and flexible because they allow multiple implementations, and indeed they are designed to allow implementations that are otherwise unrelated in the class hierarchy. The question asks, Is it right to have an interface that … Read more
No, C# does not support this. You can come close with: private static System.Text.RegularExpressions.Regex re = new System.Text.RegularExpressions.Regex(“\\(copy (\\d+)\\)$”); private static string AppendCopyToFileName(string f) { } The only difference here is the visibility of ‘re’. It is exposed to the classm not just to the method. The re variable will be initialized the first time … Read more
The collision is actually with Object.equals(). All classes are inherited from Object and therefore have the Object.equals() method which leads to this collision. You’re importing by name, not by signature. You actually can’t import a static method named equals because of this. Or rather, you can import it, but not use it. I do agree … Read more
You definitely want to check sigal (demo). It is the cutest generator I’ve tried so far. It’s also the most recent and up-to-date (inspired by pelican, the popular static blog engine – now powering kernel.org). There is an extensive list here. Lazygal would be my second choice.
Click on the small triangle in the upper right corner of the problems view and select “Configure Contents”. In that dialog check “Show all items” and uncheck “Use item limits” to show all warnings.
Well this is a strange case. It appears that the problem is: In this case, the private member should be accessible (6.6.1.): Otherwise, the member or constructor is declared private, and access is permitted if and only if it occurs within the body of the top level class that encloses the declaration of the member … Read more
Instance, not static For this case I think the second choice is clearly better. If you think about it, any method could be implemented as static if you are willing to pass the object to it, this only seems to be a special case because the other parameter is also an instance. Therefore, our search … Read more
What you’re trying to do is not achievable with simple class inheritance; a method cannot be both static and virtual. You need a static method to be able to call a function without an object (an instance); and you need bar to be virtual so that bar<int>::foo() calls derived::bar() when called from a derived instance. … Read more
Generally, usage like this is better done by just using functions in a module, without a class at all.
In Java there is no way to extend the functionally of an array. Arrays all inherit from Object but this gives very little. IMHO This is a deficiency of Java. Instead, to add functionality for arrays, static utility methods are added to classes like Array and Arrays. These methods are static as they are not … Read more