Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93533
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.54 as permitted sender)
To: internals@lists.php.net, Andrea Faulds <ajf@ajf.me>
References: <CAL=_i_mcJoFnPgeU5FQCJN=SDYnNK7Jz8zoVMv9EMuWaGRYSMg@mail.gmail.com>
 <BY2PR0201MB17845690B6386D75AF4C3D79BF4F0@BY2PR0201MB1784.namprd02.prod.outlook.com>
 <CAL=_i_=EqNoHvXmY+RdQW-reC4YF8AkuWFtGGJGOOSqX4a010g@mail.gmail.com>
 <cfe8404a-54f6-24b7-0ba8-8f807c820821@zend.com>
 <CAL=_i_kze8MNSmpg4WT+EJCRPmvty=8DA6DkuHSx+WCBzJjytg@mail.gmail.com>
 <CAF+90c9cBqKfy_q5rME1u56Rq366niYUBDTY+3_2iFJSZD9fDA@mail.gmail.com>
 <80.72.63510.DAFA5475@pb1.pair.com>
 <68fd73e7-ad19-3758-7b7a-6013cc26385f@gmail.com>
 <F7.23.14311.2DCC5475@pb1.pair.com>
 <c2113a1d-99ee-fe0c-731c-d509019a9dea@gmail.com>
 <11.87.14311.EC5E5475@pb1.pair.com>
 <46620281-18af-094f-d484-8fc69bd7dc11@gmail.com>
 <cbf397df-036b-2c1e-0fd8-3184022223c0@fleshgrinder.com>
Message-ID: <e7b91e92-85b4-56dc-cb95-2857e6ef2eb6@gmail.com>
Date: Wed, 25 May 2016 14:29:32 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:45.0)
 Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <cbf397df-036b-2c1e-0fd8-3184022223c0@fleshgrinder.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC][Vote] Typed Properties
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

>> True. But I don't see how would it work for typed properties - what
>> exactly would happen after unset? Would it be - as it is now - that it
>> is as if the property was never defined, or would it be something else?
>>
> 
> In my opinion it should simply vanish along with its definition. I mean,
> isn't that the definition of unset in general.

Right, that would be the easiest way. But then you lose guarantee that
variable you marked as "int" is indeed always int - you could unset it
and then set it to whatever you want because it no longer has a definition!

OTOH, we do have precedent for properties that can not be unset -
namely, static properties can not be unset. They can be nulled-out, of
course, and they default to null. I have no idea how "static int $x;"
would work though. The current RFC doesn't implement it, which
definitely would be weird since people would expect if you can have
typed object property, you can have typed static property, but that's
not what the RFC says.

-- 
Stas Malyshev
smalyshev@gmail.com