Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:98433
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <996dc359-cbc1-1c76-dacc-f748d0941aa6@fleshgrinder.com>
References: <CAPhkiZzs=kLF-JKBjX4bVgADz+nonERWuZYiYo8cXA=GrXKU=g@mail.gmail.com>
 <CAObuZdteOTR-FEk5anLRSSeibtq8q+CjBQ+=sKUL0paTOVZYUg@mail.gmail.com>
 <CAObuZdv2Wat-ukzq6pSMr7=yzryPz7XohnWvwHa2MJXM5kynHQ@mail.gmail.com>
 <CAPhkiZxrH9V0-2mQVM645Ra5TaG+1D86Lbteqb-impUirYf=pw@mail.gmail.com> <996dc359-cbc1-1c76-dacc-f748d0941aa6@fleshgrinder.com>
Date: Wed, 8 Mar 2017 09:50:08 -0700
Message-ID: <CAObuZdvWtAwWMTs7f_Aodh9wrg34ijcgNh3WGkH6PsHdrTDLBg@mail.gmail.com>
To: "internals@lists.php.net" <internals@lists.php.net>
Cc: Andrey Andreev <narf@devilix.net>
Content-Type: multipart/alternative; boundary=001a113db09ad3cbc2054a3aeb07
Subject: Re: [PHP-DEV] [Discussion] is_string(), string type and objects
 implementing __toString()
From: derokorian@gmail.com (Ryan Pallas)

--001a113db09ad3cbc2054a3aeb07
Content-Type: text/plain; charset=UTF-8

On Wed, Mar 8, 2017 at 8:51 AM, Fleshgrinder <php@fleshgrinder.com> wrote:

> Hey! :)
>
> The reference is actually not a problem for a Stringable because you
> would get the "Only variables can be passed by reference" error with an
> object if `strict_types` is enabled.
>
> Simply because the object **MUST** be converted into a string. The
> object itself does not satisfy the constraint, but the object clearly
> states that it can be converted into a string at any point.
>

This is the part I disagree with. The object clearly states that it can be
turned into a string when you are done using it as a object. If it gets
turned into a string, you can no longer use it as a object.

There is a difference between changing an int to string and an object to
string, in that afterwards the int->string can continue to be treated as an
int afterwards, thanks to loose typing (otherwise it wouldn't have become a
string in the first place). However with an object->string afterwards it
can ONLY be treated as a string, it can no longer be treated as an object.
Meaning

$int = 3;
foo(3);
var_dump(++$int); // 4, success, no errors

$obj = new Foo('a');
foo($obj);
var_dump($obj->method()); // Fatal error: call to member function method on
string.

To me, this doesn't make sense.

>
> Not doing so would violate what `strict_types` actually promise us. ;)
>
> --
> Richard "Fleshgrinder" Fussenegger
>

--001a113db09ad3cbc2054a3aeb07--