Util classes are great to gather protocol
TL;DR: Don't add an accidental protocol to your classes
Problems
Readability
Single Respo...
For further actions, you may consider blocking this person and/or reporting abuse
I know this is an example, and such a class would usually have more methods and some state, but with the example like that, it's the perfect example of something that shouldn't be a class, but a simple subroutine.
Hi
Objects have protocols and behavior
Subroutines don't.
This is another Code Smell called 'Helpers'
This sentence has more flaws than words and that's kind of impressive.
hi
1 - The behavior is on the real world objects. I could never have a real world metaphore for a subroutine.
2 - Having behavior is always related to real world objects
3 - I don't do structured programming. So I don't know about subroutines. I am fine with them in structured paradigm.
So you don't use methods on your objects?
of course.
Methods are the way to implement the accidental 'how' and to perform the essential 'what'
An object is what it does.
And methods fullfill the object's contract
Changed! Thank you very much!