> On Apr 22, 2019, at 04:48, alexey.bor...@gmail.com wrote: > > I don't agree that generally allowing whitespace to separate unrelated code > and then explicitly forbidding this in some language constructs is > consistent. Please prove me wrong.
By consistency, I did not mean that the style is consistent in all constructs. I meant that the developers are consistent in how they apply the style. That’s what’s important. Coding standards ensure that all the developers working on a project write code in exactly the same style, regardless of how that style is defined. When working on teams, we might feel very strongly about where to put braces or whether we use tabs vs. spaces, but these things ultimately don’t matter, as long as the team agrees to write the code in the same style. I can continue to disagree with the style, but I can compromise because I agree that being consistent (writing the code in the same style as the rest of the team) is the most important reason to use a coding standard. -Ben -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+unsubscr...@googlegroups.com. To post to this group, send email to php-fig@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/084A26D5-22ED-4FE7-B745-FA9B4962E533%40benramsey.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Message signed with OpenPGP
