Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:99264 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 33367 invoked from network); 30 May 2017 13:18:26 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 May 2017 13:18:26 -0000 X-Host-Fingerprint: 62.31.75.76 76.75-31-62.static.virginmediabusiness.co.uk Received: from [62.31.75.76] ([62.31.75.76:8602] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id BD/E0-34073-0217D295 for ; Tue, 30 May 2017 09:18:26 -0400 Message-ID: To: internals@lists.php.net References: <9dffe898-e550-c6d6-46bd-86dcf74735ea@fleshgrinder.com> <84.AD.34073.59B2D295@pb1.pair.com> In-Reply-To: Date: Tue, 30 May 2017 14:18:21 +0100 Lines: 1 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Newsreader: Microsoft Windows Live Mail 16.4.3564.1216 X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3564.1216 X-Posted-By: 62.31.75.76 Subject: Re: [PHP-DEV] Re: Class Naming in Core From: TonyMarston@hotmail.com ("Tony Marston") "Rowan Collins" wrote in message news:DC66F890-A033-4EFA-8F2B-CB365C8A4FAC@gmail.com... > >On 30 May 2017 09:21:38 BST, Tony Marston wrote: >> Different >>projects/teams/organisations are free to use whatever naming convention >>they >>like, be it snake_case, CamelCase, studlyCaps or whatever > >I think the discussion here is which convention we, as the PHP Internals >project/team/organisation, want to use. It's nothing to do with forcing >anyone else to do anything at all. > >Regards, > It does not matter. If there was no agreed "standard" to begin with, why should the core developers be forced to make unnecessary changes just because someone that there should now be a standard. Who gives this "someone" the right to demand a change in the name of consistency when the definition of "consistency" has not even been agreed? If it does not cause a problem then no time should be wasted in working on a solution. -- Tony Marston