Hey Levi,
Upon further thought, I’m not super-enthusiastic about this. As has been pointed out, it’s a
pretty serious BC break, whether code can be automatically updated or not. PHP 4 constructors may be
obsolete, but an awful lot of code uses them.
A better solution, IMO, might be simply to add a deprecation notice. This would make it obvious
during development if you’ve accidentally defined a PHP4 constructor, and would encourage
migration away from them, but wouldn’t prevent existing code from working.
Thoughts?
--
Andrea Faulds
http://ajf.me/