Menu
What are the cons of creating static utility classes? The more I've made, the more I find them extremely useful. I understand that they lack object oriented design, but I still love them probably more than I should. Are there any other cons for their use?
326
in static method we cannot call normal functions that is non - static functions. The static method can not use non static data member or call non-static method directly. this and super cannot be used in static context. Access only static type data (static type instance variable).
If the same can be said for your utility class, definitely make it static. This hold true for all methods that do not rely on the state of the object. Not just utility class methods.
Static classes have several limitations compared to non-static ones: A static class cannot be inherited from another class. A static class cannot be a base class for another static or non-static class. Static classes do not support virtual methods.
They avoid trouble. Use static methods as often as possible. That's because static methods can't access the object's attributes. Static methods aren't part of the object, so they don't have access to anything that belongs to the object.
There is nothing wrong with them, in the right context. If you have free-standing, stateless methods (such as those found in java.lang.Math), then a static class is the perfect place for them. The only reason they're in a class at all is because Java has no concept of free-standing methods.
136
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
