Is this some kind of bizarre heresy to use itemless classes?

Question

It might be a stupid question, but it annoyed me.

I wrote what, in my opinion, is procedural code, but I use classes that combine related public and private functions in accordance with the goals. Instead of using objects and methods, I call functions, when necessary, with a scope resolution operator. i.e.: db::execute($sql)

I know this is funny, but I just realized that everyone immediately associates classes with OOP. Am I doing some kind of perverse heresy?

Answer 1

you basically abuse one language construct (class) to emulate another (namespace). This is absolutely normal if you use a language that does not support the latter (php 5.2 -).

Answer 2

If you know the difference between classes and "using OOP classes", then I think this is not a real problem ...

Answer 3

Perverted heresy may take a little bit, but you are certainly missing out on most of the organizational strength of object-oriented programming.

Answer 4

It seems to me that you use classes as namespaces.

I do not see anything special in this - it provides a logical separation of problems and, apparently, facilitates your development / support.

You are definitely better off learning more about object-oriented programming so that you can take advantage of the benefits it offers.

Answer 5

Unless you claim to be doing OOP, I see nothing wrong with using static methods for procedural programming to make up for the lack of a namespace in PHP.

Answer 6

You are not doing anything wrong.

Some classes are used only to contain utility functions (for example, the Arrays class in Java), which are actually called "static methods".

What you do is use this function when replacing namespaces. For clarity, you should use the latter.