Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104635
To: PHP Internals <internals@lists.php.net>
References: <2c497732-96f8-3ef0-bc18-912220fbff4d@gmail.com>
 <CA+kxMuTA+NWgMRbG26hQWO+pXro5pANs4uVdG+aRg3yJY3ewJQ@mail.gmail.com>
Message-ID: <78aa28fb-28dc-0ecc-23bc-b0b8806d1e46@gmail.com>
Date: Sun, 10 Mar 2019 20:56:43 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.5.3
MIME-Version: 1.0
In-Reply-To: <CA+kxMuTA+NWgMRbG26hQWO+pXro5pANs4uVdG+aRg3yJY3ewJQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Subject: Re: [PHP-DEV] RFC: Locked Classes
From: rowan.collins@gmail.com (Rowan Collins)

On 10/03/2019 20:19, Dan Ackroyd wrote:
> trait LockedClass
> {
> public function __set($name, $value)
> {
> throw new \Exception("Property [$name] doesn't exist for class [" . 
> get_class($this) . "] so can't set it");
> }
> public function __get($name)
> {
> throw new \Exception("Property [$name] doesn't exist for class [" . 
> get_class($this) . "] so can't get it");
> }
> }


Incidentally, this isn't quite equivalent to the current RFC, because it 
will also intercept access to private or protected properties from out 
of scope. It doesn't make much difference other than making the error 
messages less helpful, but it's an example of how a nice userland 
implementation isn't quite as trivial as it first looks.

Regards,

-- 
Rowan Collins
[IMSoP]