Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:94921
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAA69SC7KYFf2wWpPt4L79wmWL-8YvfNhGmMrdRfvYpiJYEzBvA@mail.gmail.com>
References: <CAA69SC5w-0KAGcX_akmhtFJL=mte+3ZrShKPtnWgcML+z-HhKw@mail.gmail.com>
 <CABdc3Wo-uh3b8QNeKGADza4qSOr1cmPaSwqc=jZk9zk=1A8L9w@mail.gmail.com> <CAA69SC7KYFf2wWpPt4L79wmWL-8YvfNhGmMrdRfvYpiJYEzBvA@mail.gmail.com>
Date: Mon, 8 Aug 2016 14:46:01 +0200
Message-ID: <CAA69SC7vJK7GpH3qf=tQSx19wp4OV2pJ5woO-nWeRm_pcxgCZw@mail.gmail.com>
To: =?UTF-8?Q?Micha=C5=82_Brzuchalski?= <michal@brzuchalski.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a114ab9c27a812e05398ecc9a
Subject: Re: [PHP-DEV] RFC - Immutable classes
From: marijic.silvio@gmail.com (=?UTF-8?Q?Silvio_Mariji=C4=87?=)

--001a114ab9c27a812e05398ecc9a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Btw, I was not aware that there was already conversation on immutable
classes.

2016-08-08 14:31 GMT+02:00 Silvio Mariji=C4=87 <marijic.silvio@gmail.com>:

> I see your standpoint, but I think it could cause confusion because of
> final classes. I think "immutable" is more suited here.
> What I try to achieve is something similar like case classes in Scala.
>
> Best regards,
>
> 2016-08-08 13:16 GMT+02:00 Micha=C5=82 Brzuchalski <michal@brzuchalski.co=
m>:
>
>> Hi Silvio,
>>
>> Look into my talk about final properties https://marc.info/?
>> t=3D145979255800003&r=3D1&w=3D2 maybe there would be something usefull.
>> There is also talk about mutable and immutable properties and other clas=
s
>> modifiers also about var and val.
>> I'm not sure that it should be class midifier rather than proprty
>> modifier keyword.
>>
>> regards,
>> --
>> Micha=C5=82 Brzuchalski
>>
>> 2016-08-08 12:31 GMT+02:00 Silvio Mariji=C4=87 <marijic.silvio@gmail.com=
>:
>>
>>> Hi,
>>>
>>> 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 t=
o
>>> 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 thi=
s
>>>
>>> $email->email =3D "new@email.com";
>>>
>>>
>>> Would result in error.
>>>
>>> I have already implementation up to certain degree, but I need one advi=
ce
>>> 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
>>> immutable
>>>    also.
>>>    2. If property on immutable class contains object, it must be instan=
ce
>>>    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
>>>
>>
>>
>>
>> --
>> pozdrawiam
>> --
>> Micha=C5=82 Brzuchalski
>>
>
>
>
> --
> Silvio Mariji=C4=87
> Software Engineer
> 2e Systems
>



--=20
Silvio Mariji=C4=87
Software Engineer
2e Systems

--001a114ab9c27a812e05398ecc9a--