Googlerome9
New Member
What are valid reasons NOT to use keywords public, private, protected in php?The story: I've started a project with a team that actively uses access modifiers in their code (even "public" explicitly) and wants to convince me to do the same. I always find this kind of stuff totally useless in a dynamic language like php, but I realize that my gut feeling is hardly an argument in a technical discussion. Therefore I'm looking for a solid, clear explanation why access modifiers are useless (or even harmful) in php.I'm aware that some similar topics already exist
- http://stackoverflow.com/questions/2146271/importance-of-protected-private-in-php-classes
- http://stackoverflow.com/questions/196737/why-not-use-protected-or-private-in-php
- http://stackoverflow.com/questions/419844/best-to-use-private-methods-or-protected-methods
- I am not asking if I should use "public" or not. I'm already not using it.
- I am explicitly not interested to hear why access modifiers are good (I know they're bad, I just need an expert to confirm that).
- If you're about telling me about "best practices" and "principles of OOP", please do not bother.