Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104631
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
In-Reply-To: <2c497732-96f8-3ef0-bc18-912220fbff4d@gmail.com>
Date: Sun, 10 Mar 2019 15:16:08 -0500
Cc: PHP Internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <EA2E4E33-18D2-4357-8AB9-460B78B756F2@gmail.com>
References: <2c497732-96f8-3ef0-bc18-912220fbff4d@gmail.com>
To: Rowan Collins <rowan.collins@gmail.com>
Subject: Re: [PHP-DEV] RFC: Locked Classes
From: pmjones88@gmail.com (Paul Jones)



> On Mar 10, 2019, at 13:35, Rowan Collins <rowan.collins@gmail.com> =
wrote:
>=20
> Hi all,
>=20
> I'd like to present a new RFC for "locked classes": classes which =
restrict dynamically adding or removing properties from their instances.

Nice. This would help enforce at least one element of immutability in =
userland; namely, not having to define `final public function __set()` =
and `final public function __unset()` to prevent adding and mutating =
undefined properties.



--=20
Paul M. Jones
pmjones@pmjones.io
http://paul-m-jones.com

Modernizing Legacy Applications in PHP
https://leanpub.com/mlaphp

Solving the N+1 Problem in PHP
https://leanpub.com/sn1php