Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:114277
To: internals@lists.php.net
References: <CAF+90c-Aeaf9SfkCZWC-NZ4dy+8HxE2V=7oa94TO2zkAf2kaQQ@mail.gmail.com>
 <CADyq6sLx9239Wp0MfofAjCQYatPiY58Xw0F9-c7qnyhAZ63H9w@mail.gmail.com>
Message-ID: <3e7bc1e2-9ab0-f8c7-9d4a-f7bf3e7cf2a7@gmail.com>
Date: Tue, 4 May 2021 22:34:08 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <CADyq6sLx9239Wp0MfofAjCQYatPiY58Xw0F9-c7qnyhAZ63H9w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Property accessors
From: dik.takken@gmail.com (Dik Takken)

On 04-05-2021 12:57, Marco Pivetta wrote:
>  * instead of allowing by-ref `get` declaration, can we just kill it here,
> before it breeds again? I don't think I need to explain the woes of by-ref
> to internals, but removing the ability to declare new accessors by-ref
> would be a huge win for the engine and the language long-term.

Would killing it imply that the following example from the RFC:

    $test->prop[] = 42;

behaves differently depending on 'prop' being either a regular class
property or a property with associated get accessor?

Regards,
Dik Takken