Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95925
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.46 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <2c115733-8fe4-5230-a9ec-9d5f2cc2b810@garfieldtech.com>
References: <CAA69SC5w-0KAGcX_akmhtFJL=mte+3ZrShKPtnWgcML+z-HhKw@mail.gmail.com>
 <CABdc3WqGZ9GML-jb31FPudkML9eojpJ-Ap3kPsyd_5d8_fnwAQ@mail.gmail.com>
 <642a6e78-90ea-cbf0-ec1c-376c24e568c5@fleshgrinder.com> <CABdc3WqGFyM23CNA0eaMAyCn8L0=TaUf3xSoBOsFY_Gz4Z5uGA@mail.gmail.com>
 <CABdc3WqdTOid2BTGfpyVmNAca_9roxxx6AaQhKUPSYownO8MsA@mail.gmail.com>
 <0800a5ca-3d14-c541-1a1a-2574ec802b8c@fleshgrinder.com> <83fa661e-2d3d-6548-a506-fb969be31c0e@garfieldtech.com>
 <CAA69SC4=BXomSjmwm_6AEQGWqQqDC9scCVfv0aDH_rXMdZwt2A@mail.gmail.com>
 <c179bdb7-8665-9998-6f4f-99bbbfd19131@fleshgrinder.com> <CABdc3Wq_zfifnU=Y7TY8AXakBNO_KyDxaMhk0+Kubao_wGXaTg@mail.gmail.com>
 <56acc1d9-f424-a460-59be-3a9a1a74b198@fleshgrinder.com> <e06a39a8-305a-2de1-a8a7-e249d8179b09@gmx.de>
 <CAA69SC7wzKc2djTX267gaVpKd5-28H_GwAq2UBpzpRrqUfjpKQ@mail.gmail.com>
 <CAA69SC4QHSPpTo69X8siUv9gNmWdkgiBoiFE9Dsv_7n+Hnkpmw@mail.gmail.com>
 <b5f4cdb7-ab12-e508-5e1d-03d55db4eca0@gmx.de> <95832b08-ee80-18c1-a3da-202eed51903e@fleshgrinder.com>
 <2c115733-8fe4-5230-a9ec-9d5f2cc2b810@garfieldtech.com>
Date: Mon, 12 Sep 2016 09:15:39 +0200
Message-ID: <CAA69SC5tQ3erY7oxjf=GQs2Z3mcSRw_OjpfO=FKTJejw-k_YhA@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a113d0f5a75193c053c4a4373
Subject: Re: [PHP-DEV] RFC - Immutable classes
From: marijic.silvio@gmail.com (=?UTF-8?Q?Silvio_Mariji=C4=87?=)

--001a113d0f5a75193c053c4a4373
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

@Larry

RFC is not updated with the solution for cloning yet. So far I did add
changes on which we have agreed on. Currently we have to candidates:

First one is to have copy on write (As Christoph pointed out, we had that
in PHP 4).
Second proposal is to introduce "transformer" keyword as a method modifier.
In "transformer" method $this would basically represent cloned instance
instead of the original object.


Cheers.

2016-09-11 22:04 GMT+02:00 Larry Garfield <larry@garfieldtech.com>:

> On 09/10/2016 05:55 AM, Fleshgrinder wrote:
>
>> So? Where are we now? CoW is definitely doable and I personally think
>> that it's the best approach because the engine has full control that
>> nothing goes south. I also do not think that it's magic in any way since
>> developers have to add the _immutable_ keyword explicitly to the class.
>> That this modifier modifies the behavior should be obvious, _abstract_
>> and _interface_ also do that.
>>
>> Since I mention _interface_. I've been thinking about it and I would
>> prefer it if the _immutable_ modifier also works for interfaces.
>> Interfaces are pure abstract classes after all and they are meant to
>> define a contract for implementors. I cannot see any good reason why it
>> should not be allowed to force implementors of an interface to be
>> immutable; same as with abstract classes.
>>
>> Another aspect that we should discuss is how immutable properties should
>> behave in case we decide for CoW.
>>
>> @Larry what do you think about the CoW proposal?
>>
>
> I'm afraid I got lost in the thread somewhere with the back and forth
> about implementation details. Can you repost the current proposal, or has
> the RFC page been updated with the latest CoW-based recommendation?
>
>
> --Larry Garfield
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>


--=20
Silvio Mariji=C4=87
Software Engineer
2e Systems

--001a113d0f5a75193c053c4a4373--