While this may be annoying in this instance, this behaviour happens everywhere, so variable evaluation is now predictable across the board. Uniform variable syntax means that now, the order is evaluated left to right across the board, so PHP 7 first tries to evaluate `$link->$properties` and gives an error, because we cannot use a variable with an array type to lookup a class property. PHP 7.1 errors, because the order in which this variable chain is processed has changed. “`PHP Notice: Array to string conversion in Link.php on line 12“` When you run this code with PHP 7.1, you’ll see something different: This is because PHP 5 resolves the `$properties` part first and then applies that to the property call of the `$link` object effectively you are calling `$link->meleeWeapon` as the array lookup is done first. Running this code in PHP 5.6 would give you what you might expect: For example, let’s take the following code in PHP 5: 'rune', 'weapon' => 'meleeWeapon'] Įcho 'Link is wielding a '. In the past, PHP has resolved variables differently depending on the context, but PHP 7 fixed this causing some PHP 5 code to break.

PHP 7’s uniform variable syntax is a difficult way of saying that PHP now treats the order in which you chain variables the same, no matter the place you do it. PhpStorm 2017.1 brings full support for the uniform variable syntax changes, plus improved support for anonymous classes. PHP 7’s uniform variable syntax improvements were welcomed but opened up a whole new raft of problems for PHP developers to understand.

Phpstorm 207.1.1 license server