If utility class is an anti pattern, what is the alternatives in PHP?

Question

I am trying to build my own MVC framework (of course to learn it better) by following latest OOP design pattern. I was wondering, what is the best practice for placing repeatable codes (which are used to stay in the utility classes as static methods, which is consider not a good patterns).

For example, we want to traverse an multi dimensional array using dot separated string, and I have to utilize this algorithm in several classes (which are subclasses from other base classes). How can I do that without using utility class and without repeating the same code multiple times?

Answer 1

There's nothing wrong with a utility class, just don't lump all your unrelated utility functions into a single giant class. Separate (and namespace) them by what they do. For example, see Zend Filter or Symfony Filesystem.

Alternatively, if the classes that need this function all have a common parent, you can put the function in the top-most class or abstract.

Or if the classes do not have a common parent, you could create a Trait with a method called extractArrayFromDottedString() or similar.