What are you talking about? The change is exactly about that, change the behavior when a string is passed.
We are back to the discussion about undeprecating is_a, from scratch... It hurts codes and apps with 5.3, let do it in 5.4 only. ----- Reply message ----- From: "Stas Malyshev" <smalys...@sugarcrm.com> Date: Wed, Aug 24, 2011 19:00 Subject: [PHP-DEV] PHP 5.3.8 Released! To: "a...@akbkhome.com" <a...@akbkhome.com> Cc: "internals@lists.php.net" <internals@lists.php.net> Hi! On 8/24/11 5:38 AM, a...@akbkhome.com wrote: > " If it's a clear bug, which IMHO this is_a() issue was - then unless > we're looking at code breakage at massive scale, it should be fixed. " > > mmh.. how much breakage did you want. > > PEAR::isError is basically is_a($input, 'PEAR_Error'); it's been like > that for> 8 years.... So, PEAR has a bug, if it passes non-object argument to is_a, as previously is_a was only documented (and actually still is) as accepting objects. The fact that this bug remained for 8 years is very sad, but it doesn't cease to be a bug. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
