Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103243
To: internals@lists.php.net
References: <AM0PR0702MB3684F2B7EFF1826F515BA940E2040@AM0PR0702MB3684.eurprd07.prod.outlook.com>
 <D23FE5D3-4C11-424A-9837-F5F838D4CDBC@gmail.com>
 <CADqTB_h1oWExsgmxR6RHbX1Eew2YiQTGjR2PgJc=4uW4qAJHYw@mail.gmail.com>
 <1681263.Ri4PIu1jiQ@vulcan> <1476841B-EEBA-4513-8DD8-7ACE1F662372@gmail.com>
 <95a7902d-8451-06ee-debf-6f03c4fd7190@gmail.com>
 <0f589b64-5c3b-21b2-a396-b626054edb41@gmx.de>
Message-ID: <91ab65c4-1584-fe94-acea-734574543450@gmail.com>
Date: Sun, 23 Sep 2018 22:00:40 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.0
MIME-Version: 1.0
In-Reply-To: <0f589b64-5c3b-21b2-a396-b626054edb41@gmx.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Subject: Re: [PHP-DEV] [RFC] [VOTE] Typed properties v2
From: rowan.collins@gmail.com (Rowan Collins)

On 23/09/2018 21:50, Christoph M. Becker wrote:
> In my opinion, explicitly *declared* properties should not be
> unsettable.  We don't allow to undefine constants, functions, classes
> etc. either.  Adding and removing other properties could still be allowed.


While I agree, I think that's a somewhat separate discussion: right now, 
you can unset() a declared property, and that is handled differently 
from setting it to null. Weird though it is, there is widely-used code 
which actively relies on this fact, so it's not something we can just "fix".

The solution might be some way of marking a class as "completely 
specified" - no dynamic properties may be added, no declared properties 
may be unset; but like I say, that's a separate discussion.

Regards,

-- 
Rowan Collins
[IMSoP]