Re: Flexible function naming
| From: | Robert Cerny | Date: | Mon, 16 Dec 2013 21:12:01 +0000 |
| Subject: | Re: Flexible function naming | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-70676@lists.php.net to get a copy of this message | ||
Alexander wrote:
On Mon, Dec 16, 2013 at 8:00 PM, Robert Cerny <robert@cerny-online.com> wrote:RobertMy 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.