Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:70676
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain cerny-online.com from 83.220.144.26 cause and error)
SMTP-policy: ok
Message-ID: <52AF6CA1.4030501@cerny-online.com>
Date: Mon, 16 Dec 2013 22:12:01 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <52ABFE84.8010404@cerny-online.com> <52AF4383.3070406@gmail.com> <52AF4DD3.1090609@cerny-online.com> <CAAa_vJ=de+5nZUht+ycXkG-V2GfDx4WKSWQbYgUwhksKrVD5_w@mail.gmail.com>
In-Reply-To: <CAAa_vJ=de+5nZUht+ycXkG-V2GfDx4WKSWQbYgUwhksKrVD5_w@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Flexible function naming
From: robert@cerny-online.com (Robert Cerny)

Alexander wrote:
> On Mon, Dec 16, 2013 at 8:00 PM, Robert Cerny <robert@cerny-online.com> wrote:
>> My emphasis is on consistency *within* a project, not between. I am thinking
>> of applications mainly, not libraries.
> I don't normally post here ... but in this instance I felt compelled.
> Given enough developers, this RFC will not help you attain consistency
> without your project, quite the contrary, as each developer will
> finally reach for "her preferred way".
It *is* possible to control the coding style of a team, e.g. by 
preventing commits that violate the style. I made the experience that 
there is no single right way of naming, but consistency within a project 
is very helpful. A new senior developer will adjust to the coding style 
of the team. Plus if consistency can be recognized by developers, then 
deviations are also easier to recognize for junior developers.

Robert