Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:99389 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 78693 invoked from network); 6 Jun 2017 08:01:29 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Jun 2017 08:01:29 -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:8074] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 9B/0B-27119-75166395 for ; Tue, 06 Jun 2017 04:01:29 -0400 Message-ID: <9B.0B.27119.75166395@pb1.pair.com> To: internals@lists.php.net References: <9dffe898-e550-c6d6-46bd-86dcf74735ea@fleshgrinder.com> <3cfc0130-e530-64ed-36e8-372b044811a8@rhsoft.net> <03.F6.12681.AF215395@pb1.pair.com> In-Reply-To: Date: Tue, 6 Jun 2017 09:01:23 +0100 Lines: 1 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=response 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] Class Naming in Core From: TonyMarston@hotmail.com ("Tony Marston") wrote in message news:a6f250ec-c72a-0522-cbf0-2c7b29ed9aef@rhsoft.net... > > > >Am 05.06.2017 um 10:14 schrieb Tony Marston: >> wrote in message news:3cfc0130-e530-64ed-36e8-372b044811a8@rhsoft.net... >>> >>> >>> >>> 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 >> >> Seriously, can you explain in words of one syllable the precise benefits >> of such a consistency? Can you measure the benefits? Just because some >> OCD sufferers like consistency is not a good enough reason. I have been >> programming for over 30 years, and in that time I have had to deal with >> both snake_case and CamelCase, and while I personally find that >> snake_case is more readable, especially with names that contain more than >> 3 or 4 words, I have no trouble reading either. Having a mixture of >> styles does not cause a problem (except in the minds of OCD sufferers) so >> IMHO it does not require a solution. Anybody who says that they cannot >> work with a mixture of naming styles is either a liar or Illiterate > >it feels like talking with a blind guy about colors >who said "cannot"? > >i can mess up my living room and life still goes on >but i won't > >i can live without taking a shower over weeks >but i won't > >i could work with someone which has a terrible coding style >but i won't Anybody whose says that using snake_case instead of CamelCase for names causes any sort of "problem" is exaggerating. I have been using a mixture of naming conventions for several decades, the only "rule" being that each name must convey a proper meaning, and I have never had a problem. This matter does not cause a genuine problem, so it does not need any sort of solution. -- Tony Marston