"Go" writing high-quality Code 157 recommendations for improving C # programs--recommendation 107: Distinguishing between static classes and singleton

Recommendation 107: Distinguish between static classes and single cases

There is a view that static classes can be used as a way to implement a single-piece mode. In fact, this is not appropriate. From a traditional standpoint, a singleton is an instance object. Static classes do not meet this point. Static classes also directly violate the two object-oriented three characteristics: inheritance and polymorphism.

An instance of a static class that cannot inherit from another type is as follows:

    Interface Isample    {            }    staticclass  sampleclass:isample    {            }

The above code compiles directly but does not pass. At the same time, static classes cannot be passed as parameters and return values, as follows:

        Static void SampleMethod (SampleClass sample)        {        }

This method can also cause compilation problems.

In essence, in C #, a static class is not considered a "real object." In the case of Singleton, there is no such problem. Singleton, which is an instance object, is implemented by itself as only one object in the entire system because of the special requirements.

Turn from: 157 recommendations for writing high-quality code to improve C # programs Minjia

"Go" writing high-quality Code 157 recommendations for improving C # programs--recommendation 107: Distinguishing between static classes and singleton