On Thu, 2014-11-20 at 13:54 -0700, Levi Morrison wrote: > > It is a non-trivial change. Fixing this is not always as some people > > might suggest. > > 1) Identify PHP 4 constructors using one of several tools (including > upgrading to PHP 5.7 and getting E_DEPRECATEDs). > 2) Use one of the several tools that support method rename refactoring > (Netbeans, PhpStorm, and others) to rename the methods to __construct. > > You could probably automate it with a very high degree of success; I > just don't want to automatically change code for liability reasons. I > think you are exaggerating the required work given the tools we have > at our disposal…
No you can't. (ok *you* can but not 90% of our users, those depend on external libraries/tools and those can't simply change their API without hurting their adoption rate, which in turn hurts our adoption rate) > I am proposing E_DEPRECATED in PHP 5.7, just as the RFC for using > multiple default statements in switches (which was accepted, by the > way). > > Updating to PHP 5.7 first gives you more time to prepare for this and > other BC breaks for PHP 7. There are already a few, and I suspect > we'll have a few more before it's shipped. Yay! Instead of helping users to keep up to date and respecting their needs we give them reasons to stay on old versions for making things "cleaner". How wonderful. All things said for this thread. johannes -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
