The shell script we use here at work can be found here:
http://www.php.net/~jani/patches/syntax_check.sh.txt
We have this line in our CVSROOT/commitinfo file:
ALL $CVSROOT/CVSROOT/syntax_check.sh %r/%p %s
--Jani
On Fri, 18 Nov 2005, Steph Fox wrote:
Jani, I'm going to slip that into the upgrade notes - I wasn't aware you
could do this 'til now either!
----- Original Message -----
From: "Jani Taskinen" <sniper@iki.fi>
To: "Andi Gutmans" <andi@zend.com>
Cc: <truth@proposaltech.com>; <internals@lists.php.net>
Sent: Friday, November 18, 2005 8:06 AM
Subject: Re: [PHP-DEV] Upgrading php
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
--
Give me your money at @ <http://pecl.php.net/wishlist.php/sniper>
Donating money may make me happier and friendlier for a limited period!
Death to all 4 letter abbreviations starting with P!