Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:77593
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.208 as permitted sender)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
In-Reply-To: <542324D0.6050407@sugarcrm.com>
Date: Wed, 24 Sep 2014 21:12:55 +0100
Cc: =?windows-1252?Q?Johannes_Schl=FCter?= <johannes@schlueters.de>,
 Nicolai Scheer <nicolai.scheer@gmail.com>,
 PHP Internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <18FA619F-0476-4814-81E6-F004BDF2775E@ajf.me>
References: <CAOg_pRQFYY9rpujHBC8DzaTfJ_3RPnrzpbuBoSRNuS-+A4qPbg@mail.gmail.com> <1411561476.2303.4.camel@guybrush> <54232205.4020806@sugarcrm.com> <3E4C58C8-E816-4798-9D8F-2C7EFFA28438@ajf.me> <542324D0.6050407@sugarcrm.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Subject: Re: [PHP-DEV] Invokation on __toString() for object used as array key
From: ajf@ajf.me (Andrea Faulds)


On 24 Sep 2014, at 21:08, Stas Malyshev <smalyshev@sugarcrm.com> wrote:

> The hash doesn't have to be a nonsensical hex value, it can be =
something
> like "My Object Number 42" if you want to. The difference is that
> __toString is for human reading, and it's not always suitable for
> hashing purposes. Just read the docs on any of the languages that have
> separate hash method - they all have the same argument, there's a
> different between printing an object for output and using the object =
as
> a key.

Actually, yeah, I see your point. I suggest this, then:

    public function __toKey() : int | string {}

Psuedo-code, since you can=92t have multiple return types. I think it=92s =
a better name than __hash (fits well with __toString IMO), and this way =
we can support integer keys too, where that makes sense.
--
Andrea Faulds
http://ajf.me/