Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113379
MIME-Version: 1.0
References: <CAF+90c-HY-0fx+pTmntRJZKcQcZFfk3uJwrZ6FAMAx5_Wj+JHw@mail.gmail.com>
In-Reply-To: <CAF+90c-HY-0fx+pTmntRJZKcQcZFfk3uJwrZ6FAMAx5_Wj+JHw@mail.gmail.com>
Date: Thu, 4 Mar 2021 16:26:08 +0100
Message-ID: <CAO11TfEr-_-tZR_yAFF0n1U-Bfa=EtbwX54Cn908xJHomXPsJw@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000dc4f0e05bcb7968b"
Subject: Re: [PHP-DEV] [RFC] New in initializers
From: gabriel.ostrolucky@gmail.com (Gabriel O)

--000000000000dc4f0e05bcb7968b
Content-Type: text/plain; charset="UTF-8"

On Wed, 3 Mar 2021 at 16:04, Nikita Popov <nikita.ppv@gmail.com> wrote:

> Hi internals,
>
> I would like to propose allowing the use of "new" inside various
> initializer expressions: https://wiki.php.net/rfc/new_in_initializers
>
> In particular, this allows specifying object default values for properties
> and parameters, and allows the use of objects as attribute arguments.
>
> The RFC is narrow in scope in that it only adds support for "new". An
> extension to other call kinds should be straightforward though.
>
> Regards,
> Nikita
>

 Does this support anonymous classes? RFC should probably mention that.

--000000000000dc4f0e05bcb7968b--