rfc:uniform_variable_syntax

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
rfc:uniform_variable_syntax [2014/06/09 13:09]
nikic
rfc:uniform_variable_syntax [2017/09/22 13:28] (current)
Line 2: Line 2:
   * Date: 2014-05-31   * Date: 2014-05-31
   * Author: Nikita Popov <nikic@php.net>   * Author: Nikita Popov <nikic@php.net>
-  * Status: Draft +  * Status: Implemented (in PHP 7) 
-  * Proposed forPHP 6+  * Discussionhttp://markmail.org/message/mr4ihbubfbdxygci
  
 ===== Introduction ===== ===== Introduction =====
Line 52: Line 52:
                         // old meaning            // new meaning                         // old meaning            // new meaning
 $$foo['bar']['baz'    ${$foo['bar']['baz']}     ($$foo)['bar']['baz'] $$foo['bar']['baz'    ${$foo['bar']['baz']}     ($$foo)['bar']['baz']
-Foo::$bar['baz']()      Foo::{$bar['baz']}()      (Foo::$bar)['baz']()+$foo->$bar['baz'      $foo->{$bar['baz']}       ($foo->$bar)['baz']
 $foo->$bar['baz']()     $foo->{$bar['baz']}()     ($foo->$bar)['baz']() $foo->$bar['baz']()     $foo->{$bar['baz']}()     ($foo->$bar)['baz']()
 +Foo::$bar['baz']()      Foo::{$bar['baz']}()      (Foo::$bar)['baz']()
 </code> </code>
  
Line 157: Line 158:
  
 Because of the implementational hurdles described in the previous section, we do not support all combinations of Because of the implementational hurdles described in the previous section, we do not support all combinations of
-dereferencing operations to an arbitrary death. While PHP 5.4 fixed the most glaring issue (support for+dereferencing operations to an arbitrary depth. While PHP 5.4 fixed the most glaring issue (support for
 ''%%$foo->bar()['baz']%%''), other problems still exist. ''%%$foo->bar()['baz']%%''), other problems still exist.
  
Line 195: Line 196:
 ''%%$bar%%'', even though it is not necessary and never used. This is once again related to the way static member access ''%%$bar%%'', even though it is not necessary and never used. This is once again related to the way static member access
 needs to be implemented to support our weird indirect reference semantics. needs to be implemented to support our weird indirect reference semantics.
- 
-=== TODO === 
  
 ===== Proposal ===== ===== Proposal =====
Line 272: Line 271:
 <code> <code>
 $$foo['bar']['baz'  interpreted as   ($$foo)['bar']['baz'] $$foo['bar']['baz'  interpreted as   ($$foo)['bar']['baz']
-Foo::$bar['baz']()    interpreted as   (Foo::$bar)['baz']()+$foo->$bar['baz'    interpreted as   ($foo->$bar)['baz']
 $foo->$bar['baz']()   interpreted as   ($foo->$bar)['baz']() $foo->$bar['baz']()   interpreted as   ($foo->$bar)['baz']()
 +Foo::$bar['baz']()    interpreted as   (Foo::$bar)['baz']()
 </code> </code>
  
-This change is **backwards incompatible** (with low practical impact), which is the reason why this RFC targets PHP 6.+This change is **backwards incompatible** (with low practical impact), which is the reason why this RFC targets PHP 7.
 However it is always possible to recreate the old behavior by explicitly using braces: However it is always possible to recreate the old behavior by explicitly using braces:
  
Line 285: Line 285:
 </code> </code>
  
-This syntax will have guaranteed same behavior in both PHP 5 and PHP 6.+This syntax will have guaranteed same behavior in both PHP 5 and PHP 7.
  
 ==== Newly added and generalized syntax ==== ==== Newly added and generalized syntax ====
Line 349: Line 349:
                         // old meaning            // new meaning                         // old meaning            // new meaning
 $$foo['bar']['baz'    ${$foo['bar']['baz']}     ($$foo)['bar']['baz'] $$foo['bar']['baz'    ${$foo['bar']['baz']}     ($$foo)['bar']['baz']
-Foo::$bar['baz']()      Foo::{$bar['baz']}()      (Foo::$bar)['baz']()+$foo->$bar['baz'      $foo->{$bar['baz']}       ($foo->$bar)['baz']
 $foo->$bar['baz']()     $foo->{$bar['baz']}()     ($foo->$bar)['baz']() $foo->$bar['baz']()     $foo->{$bar['baz']}()     ($foo->$bar)['baz']()
 +Foo::$bar['baz']()      Foo::{$bar['baz']}()      (Foo::$bar)['baz']()
 </code> </code>
  
Line 356: Line 357:
 occurrence of ''%%$loader[0]::$loader[1]($className)%%'' in the Doctrine class loader will be affected by this change. occurrence of ''%%$loader[0]::$loader[1]($className)%%'' in the Doctrine class loader will be affected by this change.
 This occurrence must be replaced with ''%%$loader[0]::{$loader[1]}($className)%%'' to achieve compatibility with both This occurrence must be replaced with ''%%$loader[0]::{$loader[1]}($className)%%'' to achieve compatibility with both
-PHP 5 and PHP 6.+PHP 5 and PHP 7.
  
 The latter change turns currently valid syntax into a parse error. Expressions like ''%%global $$foo->bar%%'' are no The latter change turns currently valid syntax into a parse error. Expressions like ''%%global $$foo->bar%%'' are no
 longer valid and ''%%global ${$foo->bar}%%'' must be used instead. longer valid and ''%%global ${$foo->bar}%%'' must be used instead.
  
-As these changes only apply to some very rarely used syntax, the breakage seems acceptable for PHP 6.+As these changes only apply to some very rarely used syntax, the breakage seems acceptable for PHP 7.
  
 ===== Open issues ===== ===== Open issues =====
Line 383: Line 384:
 The main changes are limited to the language parser and compiler. Furthermore some opcode handlers had to be modified The main changes are limited to the language parser and compiler. Furthermore some opcode handlers had to be modified
 to support ''CONST'' and ''TMP'' operands. to support ''CONST'' and ''TMP'' operands.
 +
 +===== Vote =====
 +
 +As this is a language change, a 2/3 majority is required for acceptance. The vote started on 2014-07-07 and ended on 2014-07-14.
 +
 +<doodle title="Implement Uniform Variable Syntax in PHP 6?" auth="nikic" voteType="single" closed="true">
 +   * Yes
 +   * No
 +</doodle>
 +
rfc/uniform_variable_syntax.1402319377.txt.gz · Last modified: 2017/09/22 13:28 (external edit)