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

[tony_marston404]

@TomB

You need to explain how “Single responsibility” means the same thing as “Separate responsibilities”

Take a look at what I said in Would you agree this is the definition of a PHP framework? - #483 by tony_marston404

You take a class that deals with several concerns/responsibilities (note the plural) and separate it into a collection of smaller classes each of which deals with a single concern/responsibility (note the singular). The number of concerns/responsibilities remains the same, but they are now in their own separate classes instead of being in the same class.

@TomB

tony_marston404:
Your question is ridiculous as it is based on the assumption that SoC and SRP are different. I keep telling you, even by pointing to articles written by other people, that they are NOT different, but you fail to acknowledge that point. SoC and SRP are the SAME, not DIFFERENT.

You have stated they are different:

No I did not. I simply said that they were the same idea but expressed in different ways. Robert C. Martin’s article on SRP made references to coupling and cohesion while the description of SoC did not.

[tony_marston404]

@s_molinari

You can have good SoC and still break SRP, so they simply can’t be the same.

Using YOUR logic unless the article specifically says that SRP and SoC are NOT the same (which it does not) then it is reasonable to assume that they ARE the same which is precisely what this person said in a different article.

[DaveMaxwell]

This topic is now closed. New replies are no longer allowed.

OK. I think this thread has run it’s course. I think after 500+ posts, most of which is circular arguments, I don’t see any point in continuing it. Everyone agree to disagree and quit trying to prove that their point of view is MOST RIGHT.

If you have a REAL problem with me closing this, and can come up with a good reason other than this, I’ll consider it.