There must be a lot of static keywords, and everyone knows about them. What is the point of discussion?
But when I think back to some previous things, I can't help thinking about them ......
The cause is that some classes in a project are all methods, but they are designed as non-static classes. So I tried a lot to persuade my colleagues to design these classes as static ones. After my colleagues understood it, I was exhausted.
Do you have the following ideas?
- Static is a legacy product from process-oriented to object-oriented. In the past, development was process-oriented, so many static classes and static methods were used. After the process-oriented approach, this keyword is retained. Therefore, it is recommended that you do not need or use less static keywords in object-oriented development.
- Whether it is a static or non-static class, the effects are the same and there is no difference.
- If you want me to use static classes, what does this mean?
- If I use a non-static class as a static class, will there be any problems?
The following are some of the above points of view. I will explain my understanding. If there is something wrong with writing, please also point out.
- Static keywords are indeed some keywords in the era of process-oriented development, but they do not mean that static keywords should be avoided as much as possible during object-oriented development.
- Static classes and non-static classes certainly have different effects.
- Based on my experience, static classes are generally used for classes unrelated to States. So what is a class unrelated to the status? In my understanding, when there is no attribute in a class and there is only a method, we can think that this class is state-independent. Recall that a non-static class instantiates an object. Where is the purpose? The purpose is to save the class State through this instantiated object.
Isn't it? For example
A a = new ();
A. Name = "Kevin ";
A. Sex = "male ";
......
By instantiating object a, the class state is maintained by object.
If our class has no attributes and is full of methods, is it necessary to instantiate an object first to call methods in the class?
Therefore, the author suggests that when designing a class, if the class is a class unrelated to the State, it is recommended to design it as a static class.
As for the significance of doing so: first, the performance loss of constructing an object is omitted, although negligible. Secondly, it is more friendly to programmers and more convenient to call class methods.
- As long as a class is not related to the status class, it is no problem to design it as a static class.
The above points are purely personal experiences. If you have different opinions, please share them with us.
