Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113955
To: =?UTF-8?B?QW5kcsOpIEjDpG5zZWw=?= <andre@webkr.de>, internals@lists.php.net
References: <0b8301d72a3a$71045ca0$530d15e0$@webkr.de>
Message-ID: <0463c632-8260-bc8b-920e-4a9214421311@gmx.de>
Date: Mon, 5 Apr 2021 19:12:46 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.9.0
MIME-Version: 1.0
In-Reply-To: <0b8301d72a3a$71045ca0$530d15e0$@webkr.de>
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: quoted-printable
Subject: Re: Raising the precedence of the new operator
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 05.04.2021 at 18:40, Andr=C3=A9 H=C3=A4nsel wrote:

> I was wondering... PHP is the only language I know of where you have to
> write `(new Foo())->bar()` instead of
> `new Foo()->bar()`. This is particularly apparent with the builder patte=
rn:
>
> $developer->drink((new Coffee())->withCream()->withSugar());
> $logger->log((new LogMessage())->withMessage('Coffee was drunk'));
>
> Since `new Foo()->bar()` cannot (and probably should not) be used to
> "dynamically instantiate a new thing of the class
> name returned by function Foo()", it seems like it would be no problem t=
o
> change the precedence rules so that
> `new Foo()->bar()` means "instantiate a new Foo and call bar() on it".
>
> It's currently a syntax error, so allowing it would be automatically
> compatible.
>
> Has this ever been discussed before?

See <https://bugs.php.net/bug.php?id=3D70549>.

=2D-
Christoph M. Becker