> From: Robert Korulczyk [mailto:rob...@korulczyk.pl] > > Personally, I'm surprised by the controversy around this change. So far it > was an > obvious anti-pattern for me, and never seen anybody who was aware of the > consequences of using <? and still use <? instead <?php on purpose.
It's not really a problem for programmers/coders writing new code rather for server providers/administrators (maybe also a reason why such issues are not (or rarely) voiced in a language development internal list) hosting legacy applications where no one wants or there is nobody to fix anything (even more with an automatic third party tool) and then there won't even be a switch (ini option) anymore for backwards compability. So you are (will be) forced to stay on EOL php version or implement a patch for reverting particular thing in your distro/custom package. p.s. somewhat similar is the situation with 'mysql' extension which by default prints a lot of deprecated warnings even being in pecl and basically the same wrapper around mysqlnd as mysqli/pdo, but at least there is still an option if your code really requires mysql_* (and many thanks to the people like Dmitry, Matteo who still make it compatible with the actual php versions). rr -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
