Juliette

You are missing the point. In PHPCS 3.2.0, new ignore/disable/enable annotations were introduced via which you can modularly ignore just one particular sniff or error code, so the CS checks...

@ryanshoover :+1: Timing-wise for the community-outreach / documentation update, I would **strongly recommend** to wait until PHPCompatibility 9.0.0 has been released and this plugin has been updated to use the...

Those type of tags are _dangerous_ to use in plugin code as - as a developer - you don't know whether the server on which the plugin will be deployed...

As PHP no longer supports ASP tags since PHP 7, this particular issue (i.e. having those tags in the code, even though they are not used as ASP tags) will...

Could you show some example code ? If you mean that `resource` is used as part of a namespace, see: http://php.net/manual/en/reserved.other-reserved-words.php

It might be worth opening a separate issue to address the execution time - the plugin could possibly work round issues with that by resetting it during the run or...

This is actually not a false positive as the variable is found in the code, even though used correctly. All the same, there is an issue open about the principle...

@moorscode Not sure, but would be worth checking if the `phpcompat` plugin will respect `// phpcs:ignore PHPCompatibility.Cat.Sniff` annotations and if so, it might be worth it to see if such...

> I assume this is related to arguments passed by reference, which is not an issue in the enclosing functions where the above lines trigger these errors. It is not,...

I suspect this will be fixed if/when this plugin update the included version of PHPCompatibility to 8.2.0 (to be released within the next week or so).