Michael Moll

Needs to wait for a new PHPCS release with https://github.com/squizlabs/PHP_CodeSniffer/issues/3479 closed.

The advantage IMHO is pulling in widely used, known well maintained 3rd party code (providing also auto-fixes) and thus reducing the code in this repository that needs to get maintained....

> a seperate package which consists of a phpcs.xml with aggregated rules from different standards Something like https://github.com/mayflower/mo4-coding-standard? ;) On a more serious note, I'd say for an end-user the...

> another library that is, in essence a **specific company's** coding standard Since a few years, I personally do see that in the Slevomat case not as true anymore. Almost...

AFAICT, this is a problem in PHP CodeSniffer's `PEAR.FunctionCommentSniff`, which is only extended by `Symfony.FunctionCommentSniff`. Could anybody verify this and report it to the upstream project?

https://github.com/squizlabs/PHP_CodeSniffer/pull/3396 might fix this.

phpc 3.6.1 got released, @vpassapera could you test, if that fixes this issue?

This is ready now with the PHPCS 3.6.0 release :)

GH-183 would implicitly fix this.

Without a code snippet that reproduces the crash, it's going to be impossible to investigate further.