Re: Class Naming in Core
| From: | Tony Marston | Date: | Sat, 03 Jun 2017 08:10:39 +0000 |
| Subject: | Re: Class Naming in Core | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-99332@lists.php.net to get a copy of this message | ||
"Dan Ackroyd" wrote in message news:CA+kxMuRoMvy6vB0YKd6Ejqu8AsKxrO2x6F9y5i9+cxfJSJ-ihg@mail.gmail.com...
On 29 May 2017 at 23:13, Fleshgrinder <php@fleshgrinder.com> wrote:It can only be the "standard" if it has been documented as such and everyone follows it. If it was not documented as such from the start of the project then it does not qualify. It may have become the most commonly used in a selection of alternatives, but that does not give anyone the right to now say that it has become the standard and should be enforced. That strikes me as being dictatorial and authoritarian, as well as requiring large amounts of effort without offering any tangible benefits. I'm "consistency" is not a valid benefit in my book. -- Tony MarstonHey guys! People are complaining over at Reddit [1]While the "STD" is slightly humorous, it is unneeded verbosity, and will lead to pointless arguments in the future of whether other features in the future should catch the STD name, or whether they should be directly under PHP. I would recommend not using it. I don't care about case, though there may be a slight argument that upper-casing initialisations is the 'standard' in PHP core.