Hi,
I still don't get get what problem this RFC is actually going to solve?
I don't see a problem. Yes, PHP4 constructors are are old and should no
longer be used. But there is no problem still supporting them. Raise an
E_DEPRECATED for those, and be done with it.
+1
I can accept BC-breaks if there's a good reason, but this one seems a
little weak. For reference 1/3 of the 4500+ php files in the project I
work on every day still uses PHP4 constructors. And one third of them is
within the bundled PEAR libraries.
I'm not saying it is quality code, but it's a dinosaur open source
project... I believe that many other historical open source projects are
in the same boat. All the (unpaid) time that the team(s) would need to
waste on this could be better spent elsewhere.
Cheers
--
Matteo Beccati
Development & Consulting - http://www.beccati.com/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
