Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78382
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error)
Message-ID: <544E0AE1.9090406@lsces.co.uk>
Date: Mon, 27 Oct 2014 09:05:37 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <544DA1CD.9070109@php.net>
In-Reply-To: <544DA1CD.9070109@php.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Using objects as keys
From: lester@lsces.co.uk (Lester Caine)

On 27/10/14 01:37, Stas Malyshev wrote:
> The name __hash is not final, I am open to using __toKey instead or any
> reasonable alternative, we may also include a couple of options in the
> vote if that will be a point of disagreement.

I don't think it's clear from the RFC ...
Is the resulting value intended always to return the same object
independent of what has been done to the object in the mean time? A
fixed 'address' for the physical data when used as an array key?
If that is the case, then __toKey seems more comfortable. To me a hash
is used to establish if the item I am looking at has changed since it
was last accessed. There are two use cases compare the contents are the
same, and access the same object later even if it has been updated.

That said, the EKey value IS intended to identify objects which have
changed since last being accessed ... so you can't win either way?

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk