Would you agree this is the definition of a PHP framework?

[s_molinari]

@tony_marston404

our view is that I must be breaking SRP simply because I have a class with 120 methods. Coming to that opinion based on nothing more than a count is not an acceptable method. That class represents nothing more than the Model in MVC. It does not contain any control code as that is held is separate Controllers. It does not contain any view code as that is held in separate Views. It does not contain any Data Access code as that is held in separate Data Access Objects. It does not contain any code which does not belong in the Model, so it does not violate SRP. Others may have a different opinion, but that is their concern, not mine.

You are again talking about SoC and not SRP. They are different. One is about the architectural split of main tasks or services within a software and the other is about single reason for change within a class.

SoC

Separation of concerns

SRP

Single-responsibility principle

You said,

@tony_marston404

That class represents nothing more than the Model in MVC.

The model in MVC holds a good bit of different functionalities for the application. Actually, it holds all of it really, or it is extended to hold the rest of the functionality. This goes seriously against SRP stated in Wikipedia.

every class should have responsibility over a single part of the functionality provided by the software, and that responsibility should be entirely encapsulated by the class.

So I don’t have to do much more proving. You prove you break SRP on your own, through your own statement.

Scott