Class Abuse
This situation arose recently and it got me curious...
What if you needed to access an algorithm in a very simple class method, but the functionality of the class is significant and would be a pain in the ass to set up and create an object in, not to mention resource-intensive, all to use one small function...
You could copy the algorithm, but what if it changes? Then you'll have to change it twice. That's no good. I don't like either option.
Leave a comment