Quoting Ilia Alshanetsky <[EMAIL PROTECTED]>:
In this case the "facility" was implementing, poorly might I add a
handler for a clearly incorrect behavior. Removing it was not only
appropriate but necessary to encourage proper code being written.
I know that other people have other points of view, but I am not
arguing this. I'm just asking that 4.4 be marked as having a non-BC
change, because - whether I could have updated my new code or not -
there's a ton of existing code out there that will never magically
change to run silently under 4.4.
I've already had people running old major versions of applications
upgrade to PHP 4.4 because it has "security fixes", and then come
complaining because suddenly they get a ton of warnings.
Yes, they could turn off warnings. But since the code has always run
cleanly beforehand, they don't think to do that.
Yes, they could very well ignore a note on php.net about the code
they're downloading.
But if there *was* a note with the 4.4 release, it would somewhat
lighten the load on PHP application developers dealing with the change.
-chuck
--
"But she goes not abroad in search of monsters to destroy." - John
Quincy Adams
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
