Re: [Discussion] is_string(), string type and objects implementing __toString()

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 >