Thanks for the clarrification.
I'll echo Stefano's thoughts and say that referring to a previous section
is generally helpful when the standard is being heavily modified (you don't
want to update 10 places each time), but duplicating those rules once the
standard moves to review seems like the
TBH making readers to jump to another section that contains different
informations is kinda lazy.
Can we just copy paste the relevant indications and do without the
reference to the closures?
Il giorno mer 16 mag 2018 alle ore 17:44 'Alexander Makarov' via PHP
Framework Interoperability Group ha
1. The opening brace MUST go on the same line, and the closing brace MUST
go on the next line following the body.
On Tuesday, April 24, 2018 at 1:53:06 AM UTC+3, Greg Sherwood wrote:
>
> Hi,
>
> I'm working on the PSR-12 standard for PHP_CodeSniffer. I have a question
> about this section:
>
>
Hi,
I'm working on the PSR-12 standard for PHP_CodeSniffer. I have a question
about this section:
8. Anonymous Classes
> Anonymous Classes MUST follow the same guidelines and principles as
> closures in the above section.
Almost the entire closure section of PSR-12 is dedicated to argument li
