Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104622
MIME-Version: 1.0
References: <2c497732-96f8-3ef0-bc18-912220fbff4d@gmail.com>
In-Reply-To: <2c497732-96f8-3ef0-bc18-912220fbff4d@gmail.com>
Date: Sun, 10 Mar 2019 19:51:57 +0100
Message-ID: <CADyq6sJwMaX6vYi9p4V1XVXSa-86nCH6QxmtS0KJ2PX_Cb+4JA@mail.gmail.com>
To: Rowan Collins <rowan.collins@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000001424fe0583c1f469"
Subject: Re: [PHP-DEV] RFC: Locked Classes
From: ocramius@gmail.com (Marco Pivetta)

--0000000000001424fe0583c1f469
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Rowan,

Overall good idea, except that I disagree with the `unset()` being
disabled: that bit is strictly required for lazy-loading purposes, and
mostly harmless for userland ("normal" people don't do it, libraries do it)=
.

Besides that (blocker for me), if this RFC would be enforced in my coding
standards of choice =F0=9F=91=8D

Does anybody know if this has potential for engine optimizations?


On Sun, 10 Mar 2019, 19:35 Rowan Collins, <rowan.collins@gmail.com> wrote:

> Hi all,
>
> I'd like to present a new RFC for "locked classes": classes which
> restrict dynamically adding or removing properties from their instances.
>
> While it can be useful, the ability to set an object property which is
> not part of the class definition can also lead to subtle bugs. Banning
> this for all objects would be a significant and painful breaking change,
> so I propose instead the option to mark a particular class with a new
> keyword, "locked".
>
> An instance of a locked class behaves like any other object, except that:
>
> - Attempting to set a property on the instance which was not declared in
> the class (or inherited from one of its parent classes) will throw an
> error, and the instance will not be modified.
> - Attempting to read a property on the instance which was not declared
> (or inherited) will throw an error, rather than raising a Notice and
> evaluating to null.
> - Attempting to call unset() on any property of the instance will throw
> an error, and the instance will not be modified.
>
> Note that ECMAScript  / JavaScript includes a similar feature, called
> "sealed objects". However, the proposed modifier applies to classes, and
> "sealed class" has a different meaning elsewhere (e.g. C#, Kotlin), so
> I've chosen "locked class" to avoid confusion.
>
> For further details and examples, please check the RFC at
> https://wiki.php.net/rfc/locked-classes and the tests in the draft
> implementation at https://github.com/php/php-src/pull/3931
>
> Regards,
>
> --
> Rowan Collins
> [IMSoP]
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--0000000000001424fe0583c1f469--