Juliette

@chartjes Thank you for looking into this. As clearly some conferences apparently feel the need to add these kind of character limits (the wrong way), it might be an idea...

@Potherca I honestly wouldn't know. I also found that using `127.0.0.1` (or in practice: `127.0.0.1:3306`) worked better than using `localhost`. But to be honest, I tried so much that it...

@gep13 They did indeed and yes, I meant to still get back with a response, but never ending to-do lists etc etc. Having said that, that doesn't take away from...

@msykes Hi Marcus, this is a known issue and being working on - see https://github.com/wimg/PHPCompatibility/issues/292

It's not a false positive and that code is a bit silly. The "PHP 7+" version of the code will work in both PHP 5, as well as PHP 7,...

@AlexGStapleton I've ran some tests with the underlying tooling ([PHPCompatibility](https://github.com/phpcompatibility/phpcompatibility)) and for the life of me, I can not reproduce these results *at all*. I've tested with the current version...

@AlexGStapleton Thanks for that information. I've now able to reproduce the issue with: * Any PHP version * And the locked dependencies of the plugin at v1.5.0: * PHPCS 2.9.2...

@AlexGStapleton Nothing for me to keep track of. Maybe for one of the plugin maintainers though, For your perspective: I'm not directly involved with this project. I am the maintainer...

Related #204. The PHPCompatibilityWP (and underlying PHPCompatibility) dependency will also need to be updated. The plugin currently is locked at PHPCompatibility 7.1.5 (released July 2017) which contains hardly any checks...

Why not just use the PHPCS native ignore/disable/enable comments ? That way, those comments will work independently of in what manner PHPCS is run, like using PHPCS itself, using this...