I wasn't thinking of writing something in PHP... there'd be no way for
userland code to 'see' half the stuff that needed changing.
Anyway, just a thought.
Steph Fox wrote:
Is it a really stupid idea to suggest a script upgrading program a la
'autoupdate' (for 4/5 -> 6)?
It's something I hoped to tackle myself, but am unlikely to find the time
for.
Well if it works it could solve some issues. Like handling stupid BC
breaks (array_merge, class_exists), exploit new features (parsing phpdoc
to set PPP) and generally make the code a happy E_STRICT camper.
The potential for breakage is huge though (take the PPP example ..) and
also for code library it would mean that users will report all sorts of
suprising bugs (unless you test the code in all its variations).
So maybe as a one time migration tool it could make a nice addition to
PHP_Compat (implements new functions/constants etc in userland) and
PHP_CompatInfo (determines the minimal php version).
regards,
Lukas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
__________ NOD32 1.1380 (20060125) Information __________
This message was checked by NOD32 antivirus system.
http://www.eset.com
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
