Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95874
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain fredemmott.co.uk from 209.85.220.51 cause and error)
Content-Type: multipart/alternative; boundary="Apple-Mail=_DFA862C3-2D31-4238-A478-AFB18ADEDA5D"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
In-Reply-To: <CAA69SC5w-0KAGcX_akmhtFJL=mte+3ZrShKPtnWgcML+z-HhKw@mail.gmail.com>
Date: Fri, 9 Sep 2016 12:46:28 -0700
Cc: internals@lists.php.net
Message-ID: <F1628C35-24A8-417C-BE40-EBC8F8CE8A14@fredemmott.co.uk>
References: <CAA69SC5w-0KAGcX_akmhtFJL=mte+3ZrShKPtnWgcML+z-HhKw@mail.gmail.com>
To: =?utf-8?Q?Silvio_Mariji=C4=87?= <marijic.silvio@gmail.com>
Subject: Re: [PHP-DEV] RFC - Immutable classes
From: fred@fredemmott.co.uk (Fred Emmott)

--Apple-Mail=_DFA862C3-2D31-4238-A478-AFB18ADEDA5D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I see Reflection is still todo;  should there be a similar escape hatch =
to ReflectionMethod::setAccessible()?

This would allow things like: =
https://gist.github.com/fredemmott/01ad55c0c03c8d7ba62bbd6e9fb23686 =
<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 approach in the RFC seems like it =
would rapidly become unwieldy for classes with a large number of =
properties.

Regards,
 - Fred
    =20

On Aug 8, 2016, at 3:31 AM, Silvio Mariji=C4=87 =
<marijic.silvio@gmail.com> wrote:
>=20
> Hi,
>=20
> I would need your help with one idea. I'm working on one RFC that I'm =
would
> 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:
>=20
> <?php
>=20
> immutable class Email {
>>     public $email;
>>     public function __construct($email){
>>         $this->email =3D $email;
>>     }
>> }
>> $email =3D new Email("example@email.com");
>=20
>=20
>=20
> After instance of class is created, object is "frozen" so call like =
this
>=20
> $email->email =3D "new@email.com";
>=20
>=20
> Would result in error.
>=20
> 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?
>=20
> Some constraints are needed:
>=20
>   1. Child class that extends immutable class must be defined as =
immutable
>   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.
>=20
> Thank you all in advance.
>=20
> --=20
> Silvio Mariji=C4=87
> Software Engineer
> 2e Systems


--Apple-Mail=_DFA862C3-2D31-4238-A478-AFB18ADEDA5D--