> > This wholesale statement doesn't get us anywhere.
>
> It does, we underestimate the situation and this fix/improvement/consistency
> change breaks apps and codes out there.
> And I do not consider it as acceptable at this stage in 5.3.x. Let do it only
> in
> 5.4.
How is it different from any of the other non-crash-fixing bugs we fixed, that
could break apps that relied on the old behavior? Gave you two examples from
the last release (well, 5.3.7), and another imaginary one. They all fall in
the category of potentially breaking code out there, and yet - they should all
be fixed.
> > Every bug fix can result in breaking existing code.
>
> Not every, and here it is easily fixable.
I'll refrain from word fighting you on the first part, but on the second - how
is it easily fixable?
This:
is_a("bar", "foo"); // false
$obj = new bar;
is_a($obj, "foo"); // true, since now that bar's been loaded we know it
extends foo
Is a language bug, and a pretty bad one too.
Zeev
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
