Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95875
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <F1628C35-24A8-417C-BE40-EBC8F8CE8A14@fredemmott.co.uk>
References: <CAA69SC5w-0KAGcX_akmhtFJL=mte+3ZrShKPtnWgcML+z-HhKw@mail.gmail.com>
 <F1628C35-24A8-417C-BE40-EBC8F8CE8A14@fredemmott.co.uk>
Date: Fri, 9 Sep 2016 22:01:18 +0200
Message-ID: <CAA69SC7MuQa06+ubJBx_bfJO_iT1_cTh7PgYD8nVhrXqG71bXA@mail.gmail.com>
To: Fred Emmott <fred@fredemmott.co.uk>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a113b093a1f6298053c189c7f
Subject: Re: [PHP-DEV] RFC - Immutable classes
From: marijic.silvio@gmail.com (=?UTF-8?Q?Silvio_Mariji=C4=87?=)

--001a113b093a1f6298053c189c7f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

@Fred

Thanks for taking interest. I still need to fully patch reflection
extension for this. We had more important discussions in the past two weeks=
.

Cheers,
Silvio

2016-09-09 21:46 GMT+02:00 Fred Emmott <fred@fredemmott.co.uk>:

> I see Reflection is still todo;  should there be a similar escape hatch t=
o
> ReflectionMethod::setAccessible()?
>
> This would allow things like: https://gist.github.com/fredemmott/
> 01ad55c0c03c8d7ba62bbd6e9fb23686 (apologies for the hack-like syntax) -
> the =E2=80=98every property must be a constructor parameter=E2=80=99 appr=
oach in the RFC
> seems like it would rapidly become unwieldy for classes with a large numb=
er
> of properties.
>
> Regards,
>  - Fred
>
>
> On Aug 8, 2016, at 3:31 AM, Silvio Mariji=C4=87 <marijic.silvio@gmail.com=
>
> wrote:
>
>
> Hi,
>
> I would need your help with one idea. I'm working on one RFC that I'm wou=
ld
> like to submit. Idea is that after you initialize object eg. after
> constructor returns, object would be locked, and you wouldn't be able to
> change properties on that object anymore. It would like this:
>
> <?php
>
> immutable class Email {
>
>     public $email;
>     public function __construct($email){
>         $this->email =3D $email;
>     }
> }
> $email =3D new Email("example@email.com");
>
>
>
>
> After instance of class is created, object is "frozen" so call like this
>
> $email->email =3D "new@email.com";
>
>
> Would result in error.
>
> I have already implementation up to certain degree, but I need one advice
> from more experienced developers. Where is the place where I could put
> logic to lock object after the constructor has finished? Maybe in zend vm
> on ZEND_NEW token?
>
> Some constraints are needed:
>
>   1. Child class that extends immutable class must be defined as immutabl=
e
>   also.
>   2. If property on immutable class contains object, it must be instance
>   of immutable class.
>   3. You can not have immutability per property, it either whole class or
>   none.
>
> Thank you all in advance.
>
> --
> Silvio Mariji=C4=87
> Software Engineer
> 2e Systems
>
>
>


--=20
Silvio Mariji=C4=87
Software Engineer
2e Systems

--001a113b093a1f6298053c189c7f--