@MarkMaldaba I agree there is a change (which may or may not be detected in PHPCompatibility, I need to check), but the change has nothing to do with __call() or __callStatic() as far as I can see: https://3v4l.org/gcUhi

Hi @jrfnl. No, your fiddle is not doing the same thing and I would expect things to work the same across PHP versions if you are not returning by reference.

The point is that PHP < 7 does not allow you to return values by reference from __call() and __callStatic() therefore attempting to assign their value to a variable, by reference, will trigger the strict standards warning (or simply fail without an error) on earlier versions. This is because you are returning an unbound value from the function and therefore there is no reference to assign.

However, once the ability to return by reference was added, the assign by reference is acceptable and (a) no longer throws a notice; and (b) correctly holds a reference to the static class property, meaning changes made to the variable in the outer scope affect the class variable in the inner scope. It is the second of these that is the more significant backwards-compatibility issue, and the reason I am flagging this.

Here is another fiddle which demonstrates the difference between function __call() and function &__call() within the same PHP version: https://3v4l.org/3UWMV

@MarkMaldaba It would be helpful to find the exact change in PHP, either the commit which made this change or any RFC/UPGRADING reference related to it.

I want to properly understand what was exactly has changed to be able to evaluate whether this is sniffable or not and what exactly should be sniffed for.

I'm not completely sure, but this looks like the commit where it was changed: php/php-src@5e8133f

This is a change to how __call() and __callstatic() were implemented that was made in PHP 7.0. I'm wondering if this was a byproduct of the change, rather than an intended outcome.