On 3/14/06, Andi Gutmans <[EMAIL PROTECTED]> wrote: > Pierre and all, > > A while ago I suggested to add an UPGRADING file for the PHP 6 > upgrade, where we'd document every time we break BC and how to solve > that. For example, with nuking register_globals we could write what > we broke, and if really needed, what 1-2 liners they can write to get > the same behavior back (e.g. extract()).
Are you asking me to write the docs about how to emulate register_globals? :-D > Ilia and I owe the safe_mode docs. If anyone who broke something can > take care of this that'll be great. The earlier we start the easier > the PHP 6 upgrade will be and the less info we'll forget. I do not what is your way, but if we remove something for very good reasons, what's the point to explain howto emulate what we just removed? A doc to explain why it has been removed and links to the other doc pages (like _GET, _SESSION,...) is more appropriate in this case. In other breakages, you are right, some nice migration docs are welcome, should the developers always take care of that? I'm not sure, we are not all good doc writers (or I am not). --Pierre -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
