Req #70549 [Opn]: Allow `new Foo()->bar()` without parens around `(new Foo)`

From: Date: Fri, 25 Sep 2015 08:13:07 +0000
Subject: Req #70549 [Opn]: Allow `new Foo()->bar()` without parens around `(new Foo)`
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-196228@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=70549&edit=1 ID: 70549 Updated by: nikic@php.net Reported by: vovan-ve at yandex dot ru Summary: Allow new Foo()->bar() without parens around `(new Foo)` Status: Open Type: Feature/Change Request Package: Scripting Engine problem PHP Version: 7.0.0RC3 Block user comment: N Private report: N New Comment: Ah, I think I get what you mean now. You only want to allow omission of parentheses if new is used with an argument list, correct? I.e. new Foo->bar() will be forbidden, but new Foo()->bar() will be allowed and interpreted as (new Foo())->bar()? Previous Comments: ------------------------------------------------------------------------ [2015-09-25 07:24:27] vovan-ve at yandex dot ru > You are proposing to interpret this as $obj = (new > $foo)->bar() instead No, it's not. new $foo->bar()->method() is exactly new ($foo->bar)()->method() like new foo.bar().method() is ECMAScript. ------------------------------------------------------------------------ [2015-09-25 07:17:42] nikic@php.net We currently allow code like this: $obj = new $foo->bar(); // Meaning: $class = $foo->bar; $obj = new $class(); You are proposing to interpret this as $obj = (new $foo)->bar() instead, which would break backwards compatibility. This could have been changed as part of the UVS RFC, but I felt like this change would be too intrusive and the consequences rather weird. I expect something like new $foo['bar'] to behave as new {$foo['bar']} not (new $foo)['bar']. ------------------------------------------------------------------------ [2015-09-25 07:07:25] kalle@php.net (assigning to Nikita for his PoV on this) ------------------------------------------------------------------------ [2015-09-25 03:59:09] yohgaki@php.net Related RFC https://wiki.php.net/rfc/uniform_variable_syntax PHP 7 evaluates expression left to right, but individually in this case. i.e. "new" is non-associative. http://php.net/manual/en/language.operators.precedence.php Other language's operator precedence. JavaScript: http://www.scriptingmaster.com/javascript/operator-precedence.asp C++: http://en.cppreference.com/w/cpp/language/operator_precedence C: http://en.cppreference.com/w/c/language/operator_precedence Java: http://introcs.cs.princeton.edu/java/11precedence/ Python3: https://docs.python.org/3/reference/expressions.html Ruby: http://www.techotopia.com/index.php/Ruby_Operator_Precedence ------------------------------------------------------------------------ [2015-09-22 15:38:35] enoquejoseneas at gmail dot com Good idea. PHP need this feature, already available on Java and Javascript ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=70549 -- Edit this bug report at https://bugs.php.net/bug.php?id=70549&edit=1

« previous php.bugs (#196228) next »