Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:99357 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 83265 invoked from network); 5 Jun 2017 11:37:01 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Jun 2017 11:37:01 -0000 Authentication-Results: pb1.pair.com header.from=lists@rhsoft.net; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=lists@rhsoft.net; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain rhsoft.net designates 91.118.73.15 as permitted sender) X-PHP-List-Original-Sender: lists@rhsoft.net X-Host-Fingerprint: 91.118.73.15 mail.thelounge.net Received: from [91.118.73.15] ([91.118.73.15:27033] helo=mail.thelounge.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 6C/C7-12681-95245395 for ; Mon, 05 Jun 2017 07:36:59 -0400 Received: from srv-rhsoft.rhsoft.net (Authenticated sender: h.reindl@thelounge.net) by mail.thelounge.net (THELOUNGE MTA) with ESMTPSA id 3whCTL3Y9yzXMn for ; Mon, 5 Jun 2017 13:36:54 +0200 (CEST) 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> Message-ID: Date: Mon, 5 Jun 2017 13:36:54 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 MIME-Version: 1.0 In-Reply-To: <03.F6.12681.AF215395@pb1.pair.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: de-CH Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Class Naming in Core From: lists@rhsoft.net ("lists@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