Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81539
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.169 as permitted sender)
Message-ID: <54CE7589.7060407@gmail.com>
Date: Sun, 01 Feb 2015 18:50:49 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <CAEbg-4YrBumSmCmvTbgVQTS=U2dm3gLzO6im69qQp6brxm=RMg@mail.gmail.com> <54CBC804.7050706@gmail.com> <54CD7668.30301@garfieldtech.com> <54CD7975.8040908@gmail.com> <C524B7E9-86D2-42D1-AFA7-2A508A9A046D@ajf.me>
In-Reply-To: <C524B7E9-86D2-42D1-AFA7-2A508A9A046D@ajf.me>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [RFC] Immutable variables and objects
From: rowan.collins@gmail.com (Rowan Collins)

On 01/02/2015 01:06, Andrea Faulds wrote:
>> the intermediate objects are useless and nobody needs 5 new objects when
>> >you do it. Am I missing something here?
> I assume the reason for doing this is so you can’t ever modify the object from a distance, you must always create a new one to avoid messing up anything with an existing handle on it.

An alternative, which I'm guessing FIG considered and rejected, is 
having a mutable "builder" object, and require the user to specifically 
request an immutable object when they're ready to use it:

$builder = new RequestBulider;
$a = $builder->withHeaders(...)->withBody(...)->getRequest();
$a_prime = $builder->withEncoding(...)->withETag(...)->getRequest();


-- 
Rowan Collins
[IMSoP]