Re: Class Naming in Core
| From: | lists@rhsoft.net | Date: | Sun, 04 Jun 2017 09:22:49 +0000 |
| Subject: | Re: Class Naming in Core | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-99349@lists.php.net to get a copy of this message | ||
Am 04.06.2017 um 11:10 schrieb Tony Marston:
If there was never a standard to begin with then there should be proper justification for introducing one now, and I'm afraid that "to be consistent" is not a valid argument. What problems are caused by this inconsistency? What is the cost, both in core developer time and application developer time, to change it? If the benefits are smaller than the costs then can the change actually be justified?seriously, if you don't understand the obvious benefits of consistency when a lot of different people have to deal with source code over a long period of time likely the discussion with you is pointless and just wasted time for everybody involved in the time you wasted with your mails i typically cleanup inconsistency here and there in a project with 250000 lines of code which dates back to 2003 to make my own life as core-developer and everybody elses easier