wrote in message
news:b1ab1858-8ed9-802b-85a6-fe1b458a4...@fleshgrinder.com...
@Tony: exactly what Rowan said. We will not change a single line of
code, and nobody will be forced to do anything. **UNLESS** the code is
meant to become part of the core of PHP. In that case it must follow the
rules
@Tony: exactly what Rowan said. We will not change a single line of
code, and nobody will be forced to do anything. **UNLESS** the code is
meant to become part of the core of PHP. In that case it must follow the
rules, the rules that are part of the coding standard. It is fine if you
change your co
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 wrote:
> >
> > > Different projects/teams/organisations are free to use whatever
> > > naming convention they l
"Rowan Collins" wrote in message
news:dc66f890-a033-4efa-8f2b-cb365c8a4...@gmail.com...
On 30 May 2017 09:21:38 BST, Tony Marston wrote:
Different
projects/teams/organisations are free to use whatever naming convention
they
like, be it snake_case, CamelCase, studlyCaps or whatever
I think t
On 30 May 2017 09:21:38 BST, Tony Marston 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/organisat
