Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78364
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 66.111.4.25 as permitted sender)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
In-Reply-To: <544DB15E.7090704@php.net>
Date: Sun, 26 Oct 2014 22:08:24 -0500
Cc: PHP Internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <4F8CEEE9-33CF-4138-9280-5488992C4AAB@php.net>
References: <544DA1CD.9070109@php.net> <A7DB3F27-0306-4401-919A-006000A5C164@fitch.so> <544DB15E.7090704@php.net>
To: Stas Malyshev <smalyshev@gmail.com>
Subject: Re: [PHP-DEV] [RFC] Using objects as keys
From: willfitch@php.net (Will Fitch)


> On Oct 26, 2014, at 9:43 PM, Stas Malyshev <smalyshev@gmail.com> =
wrote:
>=20
> Hi!
>=20
>> I=E2=80=99m trying to wrap my head around a real-world use-case with =
this.
>> We have spl_object_hash, which effectively provides a unique hash for
>=20
> This hash has nothing to do with object's contents. But imagine number
> GMP("42") and imagine you actually want two GMP objects expressing =
"42"
> actually represent the same hash key. Or imagine you want to generate
> the key somehow in a way related to object's content and not just a
> random number. As I said in the RFC, evidence that so many languages
> implement it shows that this use case is quite real. Of course, you =
can
> always default to spl_object_hash, but now you have control over it.

Thank you for your clarity. With this new approach, wouldn=E2=80=99t we =
best be served by renaming/deprecating/removing spl_object_hash? I=E2=80=99=
m concerned these different approaches will introduce quite a bit of =
confusion with object hashing. This RFC=E2=80=99s approach gives the =
user more power to determine what=E2=80=99s best in this case, so I=E2=80=99=
d lean more towards renaming spl_object_hash to something that reflects =
getting a unique ID per object (e.g. spl_unique_object_id, etc).

>=20
>> an object. If the intent is to provide an opportunity of individual
>> classes to decide what their hash is, couldn=E2=80=99t they provide =
that via
>> __toString? I know many frameworks use __toString to build out some
>> implementation of an object (Zend form for example), but the point of
>> __toString is to provide a string representation of an object.
>=20
> This is covered in the RFC, right in the introduction.
> --=20
> Stanislav Malyshev, Software Architect
> SugarCRM: http://www.sugarcrm.com/