On Tue, 30 May 2017, Tony Marston wrote: > "Rowan Collins" wrote in message > news:dc66f890-a033-4efa-8f2b-cb365c8a4...@gmail.com... > > > > On 30 May 2017 09:21:38 BST, Tony Marston <tonymars...@hotmail.com> wrote: > > > > > Different projects/teams/organisations are free to use whatever > > > naming convention they like, be it snake_case, CamelCase, > > > studlyCaps or whatever > > > > I think the discussion here is which convention we, as the PHP > > Internals project/team/organisation, want to use. It's nothing to do > > with forcing anyone else to do anything at all. > > It does not matter. If there was no agreed "standard" to begin with, > why should the core developers be forced to make unnecessary changes > just because someone that there should now be a standard. Who gives > this "someone" the right to demand a change in the name of consistency > when the definition of "consistency" has not even been agreed? If it > does not cause a problem then no time should be wasted in working on a > solution.
It is also really irrelevant, as function and class names are case-insensitve. cheers, Derick -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
