Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:77521
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.178 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <54213ECC.5080204@php.net>
References: <CAOg_pRQFYY9rpujHBC8DzaTfJ_3RPnrzpbuBoSRNuS-+A4qPbg@mail.gmail.com>
	<54213481.8080700@php.net>
	<CAPwsocGDyT13Se-0AcUon=Q59JEkLX-YPiyXAM+Q9GupYMk0-A@mail.gmail.com>
	<54213ECC.5080204@php.net>
Date: Tue, 23 Sep 2014 10:45:26 +0100
Message-ID: <CAPwsocHKP6i0QiQFe86yjwjC6m=wAPRe1+zvCOBYgzsm-hX5mw@mail.gmail.com>
To: Michael Wallner <mike@php.net>
Cc: Nicolai Scheer <nicolai.scheer@gmail.com>, PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Invokation on __toString() for object used as array key
From: leight@gmail.com (Leigh)

On 23 September 2014 10:35, Michael Wallner <mike@php.net> wrote:
> On 2014-09-23 11:15, Leigh wrote:
>> He doesn't want to add the object as a key, he wants to invoke __toString().
>
> Did I write that?

No, you didn't, sorry.

I just didn't see how an object with an explicit method to convert it
to a string compared to using a resource straight up as a key. If you
were implying the resource would be cast to int, then I get the
comparison.

Does it really make bugs that hard to find? You'd expect the user to
know when they're using this behaviour when they write the code...
well, I would.

I suppose explicit casting removes any ambiguity, we use
$a[(int)$resource] all the time for arrays of sockets and that's
served us fine over the years. Hmm, thinking about it
$a[(string)$object] is a lot clearer than having some magic sort it
out. You're right, I'll retreat now :)