Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:86204
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.169 as permitted sender)
MIME-Version: 1.0
References: <CAGSCP-nS+f5p-n-KbVZ6mFEax8Mh50px2vBVjq96iPbgHva8WA@mail.gmail.com>
 <5553E139.8090805@gmx.de>
In-Reply-To: <5553E139.8090805@gmx.de>
Date: Wed, 13 May 2015 23:45:54 +0000
Message-ID: <CAGSCP-nMm9MAqHkD=4NjwehCY7jVze4K0vne3w2a4B31xjE9dA@mail.gmail.com>
To: Christoph Becker <cmbecker69@gmx.de>, internals@lists.php.net
Content-Type: multipart/alternative; boundary=001a11c30f9e470d700515ff3619
Subject: Re: Proposal: interfaces for object to scalar type casting
From: guiwoda@gmail.com (Guido Contreras Woda)

--001a11c30f9e470d700515ff3619
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I do agree that, if I'm the owner and responsible for the object in
question, adding an explicit method would be better than casting it. The
problem is that many times we are dealing with third party libraries, and
modifying them is more complicated. But it is true, and it is true that the
number types would collide if both could be used. That could issue an
E_NOTICE if not force casted, and default to one of the types (as unquoted
strings do).

El mi=C3=A9., 13 de may. de 2015 a la(s) 8:41 p. m., Christoph Becker <
cmbecker69@gmx.de> escribi=C3=B3:

> Guido Contreras Woda wrote:
>
> > So, what do you think of a set of interfaces that allow userland object=
s
> to
> > be used as scalar types?
> >
> > Some simple examples in PHP here:
> > https://gist.github.com/guiwoda/5d16c8fb97d29e476d20
>
> One of the biggest problems is that it's not always clear which
> conversion should be used; consider, for instance,
>
>   $obj1 + $obj2
>
> where __toInt() as well as __toFloat() might make sense.
>
> A possible solution would be to force the conversion with type casts,
> but I don't see a real advantage in using
>
>   (int) $obj1
>
> over
>
>   $obj1->toInt()
>
> where the latter is a normal user defined method.
>
> Another problem is that such automatic casting from objects to scalars
> might obscure the code.
>
> --
> Christoph M. Becker
>
>
>

--001a11c30f9e470d700515ff3619--