On Thu, 17 Nov 2005, Andi Gutmans wrote:
I'm hoping that in future we can provide better tools for upgrading in between
versions. Both from an auto-conversion perspective and just scanning the code
statically and printing out warnings on what code to check. Coupled with
better upgrading docs I think we'd improve the current situation
significantly.
We already have the scanner:
# php -derror_reporting=4095 -l script_to_check.php
Strict Standards: Usage of {} to access string offsets is deprecated and
will be removed in PHP 6 in t.php on line 6
No syntax errors detected in t.php
With a simple shell script you can create a list of files having
any errors/warnings/notices/strict.. :)
At work we use a syntax checker script run whenever we commit files
to our CVS repository to catch any errors early..this reminded me to
fix that script to catch notices and such too. :)
--Jani
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
