Johannes Schlüter wrote on 20/11/2014 17:00:
We can deprecate it in 7 (and fix code in our distribution) and then take a next step in a later version, though. This gives folks like WP time to update their codebase and be ready when our larer version comes out.
+1 for officially deprecating this for a while before removing; currently, there's not even an E_STRICT when defining or using old-style constructors. The manual isn't particular clear either:
> For backwards compatibility, if PHP 5 cannot find a __construct() <http://php.net/manual/en/language.oop5.decon.php#object.construct> function for a given class, and the class did not inherit one from a parent class, it will search for the old-style constructor function, by the name of the class.
I notice the RFC does propose deprecation, but in 5.7; that's predicated on a 5.7 being released, which I know some people are not in favour of. Has there been a formal vote on whether 5.7 should exist as a lightweight "last 5.x" shortly before 7.x?
Even with that, there is the question of whether 5.7 would give users long enough to make sure everything was compatible with this change.
Regards, -- Rowan Collins [IMSoP]