Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
If you search on the reasons why static methods are bad the first thing you find it is because you can’t override it when you are unit testing.
So is this still true considering in PHP 5.3 you can do whatever you want with the introduction of static::?
http://sebastian-bergmann.de/archives/883-Stubbing-and-Mocking-Static-Methods.html
Note he explains even how to use singleton without any testing problem:
If you have a static member function, it could usually be a free function. The usual reaction is then that the coder has opted for a static member function only because of the myth that “everything must be in an object”.
That’s why people discourage them.
And, because it’s not a very convincing argument, those people pointed to unit testing instead. Not sure what they’ll do now.