Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:77523
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain margaine.com from 209.85.223.174 cause and error)
MIME-Version: 1.0
In-Reply-To: <54214E57.3080200@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>
	<CAPwsocHKP6i0QiQFe86yjwjC6m=wAPRe1+zvCOBYgzsm-hX5mw@mail.gmail.com>
	<54214E57.3080200@php.net>
Date: Tue, 23 Sep 2014 12:53:31 +0200
Message-ID: <CABRjmp-UF0GXmvyc_+wFOp=Ld9+7Betzu0ch8N+mvsqUZmTnXA@mail.gmail.com>
To: Michael Wallner <mike@php.net>
Cc: PHP Internals <internals@lists.php.net>, Nicolai Scheer <nicolai.scheer@gmail.com>, 
	Leigh <leight@gmail.com>
Content-Type: multipart/alternative; boundary=bcaec50fe063d3e0fd0503b9600d
Subject: Re: [PHP-DEV] Invokation on __toString() for object used as array key
From: florian@margaine.com (Florian Margaine)

--bcaec50fe063d3e0fd0503b9600d
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,

I do believe that the UString class would benefit from such a change.

Why would it be confusing to implement this?

Regards,

*Florian Margaine*
Le 23 sept. 2014 12:42, "Michael Wallner" <mike@php.net> a =C3=A9crit :

> On 2014-09-23 11:45, Leigh wrote:
> > 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 :)
> >
>
> I'm a "victim" of $array[(int) $resource] myself. I just tried to
> explain that the behavior is intentional and not an oversight. That
> doesn't mean that is set in stone for all times.
>
> --
> Regards,
> Mike
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--bcaec50fe063d3e0fd0503b9600d--