Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100786
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain belsimpel.nl designates 89.188.25.245 as permitted sender)
To: "PHP internals (internals@lists.php.net)" <internals@lists.php.net>
Thread-Topic: E_RECOVERABLE_ERROR for object to string conversion
Thread-Index: AdM3iryMCfkqQD5DT+uehnuf5CyTkw==
Date: Wed, 27 Sep 2017 12:45:15 +0000
Message-ID: <871ffa2fa9174506b227dbd6c6b816b4@belsimpel.nl>
Accept-Language: en-US, nl-NL
Content-Language: nl-NL
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: E_RECOVERABLE_ERROR for object to string conversion
From: marlies.heijkoop@belsimpel.nl (Marlies Heijkoop)

Hi Internals,

I stumbled upon a difference in behavior between PHP >=3D7.0 and HHVM when =
it comes to object-to-string conversion for objects not implementing a `__t=
oString` which caught me by surprise.

It's probably a pretty common scenario, especially for inexperienced PHP de=
velopers, as all it takes is to accidentally name your method `_toString()`=
 or `toString()` rather than `__toString()`.

When trying to use an object which does not implement a __toString(), PHP w=
ill emit an E_RECOVERABLE_ERROR where HHVM throws an Error.
See https://3v4l.org/WtJff  for a minimal example. HHVM's behavior makes mo=
re sense to me here.

To me, PHP's behavior is especially unexpected if you consider the behavior=
 in https://3v4l.org/lF7gR where PHP *does* throw a (Type)Error because of =
the typehint. Note this example works if you change `$a` for an instance of=
 something with a proper `__toString()`-method.

I searched through the discussions on the original 'Exceptions in the engin=
e' RFC and couldn't find any mention of this specific case so I was wonderi=
ng if anyone remembers if this was deliberately kept this way? I'm not sure=
 if I have the skill to write a patch, I'm willing to try, but it'd be a wa=
ste of time if there is some good reason for having kept this an E_RECOVERA=
BLE_ERROR I'm unaware of.

Met vriendelijke groet,
=A0
Marlies Heijkoop
-----
MobielWerkt BV / Belsimpel.nl
=A0
T. +31 (0)50 210 34 04
E. marlies.heijkoop@belsimpel.nl
I.=A0https://www.belsimpel.nl
=A0
Bezoekadres:
Waagstraat 1
9712 JX, Groningen
=A0
Postadres:
Postbus 3023
9701 DA, Groningen
=A0
Op deze e-mail is een disclaimer van toepassing, ga naar=A0www.belsimpel.nl=
/disclaimer_email A disclaimer is applicable to this e-mail, please refer t=
o=A0www.belsimpel.nl/disclaimer_email