> use a slightly modified version of the open tag, for example <?php6 or > <*php, etc. This satisfies several desires: we don't want an extra > line of boilerplate code like 'use PHP 6' to be required in every > source file, we want a PHP 5 file to run without modification, and we > want a PHP 6 file to be able to include a PHP 5 file without > modification, but we don't want PHP 6 to have to be a superset of PHP
I don't like this idea, and in fact if it's ever implemented I think it should go the other way around. (i.e. use a <?php5 for a 5.x compatibility mode) Mostly because people who want to properly maintain a project will go through the source thoroughly to properly update legacy code, however old legacy code that isn't going to be maintained usually warrants the find and replace method where something like this could make sense... But my point is I'd rather have this option: > 3. Build a high-quality tool to convert code automatically to the > greatest extent possible Telling the what's incompatible/broken and how to fix it, or do it automagically if possible. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
