@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 coding style in every file in your project where you are the only person working on. However, we are a team if changing members, and having a consistent code style helps newcomers to get into the code base. It, hopefully, helps future maintainers to cope better with the legacy code we are producing every day.
Feel free to disagree with this, but this is reality here, and these kind of policies are established as part of any professional code base in the world. On 5/30/2017 3:58 PM, Derick Rethans wrote: > It is also really irrelevant, as function and class names are > case-insensitve. > > cheers, > Derick > It matters to a lot of people, and that is why it should matter for us. We are leaders of an unbelievably huge community and we must address their concerns. Sometimes those concerns are complete bullshit, in that case we can and should ignore them, but in this case we actually already have a policy, it is just incomplete and I am asking to complete it. ;) -- Richard "Fleshgrinder" Fussenegger
signature.asc
Description: OpenPGP digital signature
