Zeev Suraski wrote:
If we are to continue with that idea, we need to strike that one out completely. Instead, we need to come up with clear instructions on how to upgrade without forcing people to audit their applications. Your letter is a good first step. It's very much contradictory to the original letter (it is in fact adding more hacks to work around the removed features), but if we are to remove these features, that's the way to go.
The point here is to move the hacks into the user space. This makes the language cleaner, but more importantly it means that less unnecessary stuff is handled via ini settings which makes portable apps considerably more doable. That is something which is very important.
As for changes in functions. An alias cleanup really does need to happen at some point, especially if we are to add even more alias to deal with function naming cleanups :-)
Parameter order fixes are another beast entirely. Maybe in the end alot of the functions that have inconsistent parameter orders also have inconsistent function names. So in those cases we might be able to "kill two flies at once" without having to resort to runkit and friends. Obviously in that case we cannot just add a standard alias for BC.
regards, Lukas -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
