Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:99349
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain rhsoft.net designates 91.118.73.15 as permitted sender)
To: internals@lists.php.net
References: <9dffe898-e550-c6d6-46bd-86dcf74735ea@fleshgrinder.com>
 <CA+kxMuRoMvy6vB0YKd6Ejqu8AsKxrO2x6F9y5i9+cxfJSJ-ihg@mail.gmail.com>
 <A4.5C.12681.20F62395@pb1.pair.com> <op.y09fz0b4twp9n2@charlie>
 <F9.E2.12681.8AEC3395@pb1.pair.com>
Message-ID: <3cfc0130-e530-64ed-36e8-372b044811a8@rhsoft.net>
Date: Sun, 4 Jun 2017 11:22:49 +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: <F9.E2.12681.8AEC3395@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 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