Ferenc Kovacs wrote on 28/01/2015 12:13:
ok, I was assuming that by turning it into E_RECOVERABLE_ERROR you would still keep the assuming string behavior if there is a custom error handler which returns true for this error.
I'm undecided on whether the string value or null would make more sense, and listed both possibilities in my original post:
> Proposed behaviour: an E_RECOVERABLE_ERROR is issued; if the error is caught, either the existing string behaviour could be retained, or the value could be treated as NULL. (I'm open to other alternatives.)
Returning null would probably allow the engine code to be simplified, but returning the string would allow people to write compatibility layers using a custom error handler.
Regards, -- Rowan Collins [IMSoP] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
