Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81528
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain beccati.com designates 176.9.114.167 as permitted sender)
Message-ID: <54CE0A5E.8060901@beccati.com>
Date: Sun, 01 Feb 2015 12:13:34 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Larry Garfield <larry@garfieldtech.com>, internals@lists.php.net
References: <CAEbg-4YrBumSmCmvTbgVQTS=U2dm3gLzO6im69qQp6brxm=RMg@mail.gmail.com> <54CBC804.7050706@gmail.com> <54CD7668.30301@garfieldtech.com> <54CD7975.8040908@gmail.com> <54CDE9FF.40700@googlemail.com> <54CDF420.1030801@garfieldtech.com>
In-Reply-To: <54CDF420.1030801@garfieldtech.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Immutable variables and objects
From: php@beccati.com (Matteo Beccati)

Hi Larry,

Il 01/02/15 10:38, Larry Garfield ha scritto:
> On 02/01/2015 02:55 AM, Crypto Compress wrote:
>> - If the old object is not thrown away, then memory consumption is
>> doubled and the "fast" argument is wrong.
>> (Performance, of cloning an object without copying values and of some
>> method calls, is negligible.)
>
> I'm not sure that anyone has benchmarked the memory impact of the
> immutable approach yet.  I will pass that along and see what data comes
> out.

I think I did while checking its speed. Maybe I didn't publish the 
result, but going from memory there was no significant footprint 
increase. Just the expected speed decrease.


Cheers
-- 
Matteo