Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:20147 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 69759 invoked by uid 1010); 18 Nov 2005 13:37:59 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 69744 invoked from network); 18 Nov 2005 13:37:59 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Nov 2005 13:37:59 -0000 X-Host-Fingerprint: 192.38.9.232 gw2.emini.dk Linux 2.4/2.6 Received: from ([192.38.9.232:4311] helo=gw2.emini.dk) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id B4/50-07637-639DD734 for ; Fri, 18 Nov 2005 08:37:58 -0500 Received: from foxbox (client-1020-p-1-lns.glfd.dial.virgin.net [81.103.147.251]) by gw2.emini.dk (Postfix) with ESMTP id B46488F606; Fri, 18 Nov 2005 14:37:52 +0100 (CET) Message-ID: <0dc401c5ec45$41352e30$5f416551@foxbox> Reply-To: "Steph Fox" To: "Jani Taskinen" Cc: , References: <437B530A.5050105@prohost.org> <437CF6B4.5080207@web.de><437CF943.7090800@lerdorf.com> <437D0D08.8060805@web.de> <437D0E22.7080006@lerdorf.com><437D11B7.7090102@web.de> <437D1361.5080504@prohost.org><1132274666.8441.175.camel@notebook> <6.2.3.4.2.20051117165150.028458b0@localhost> Date: Fri, 18 Nov 2005 13:37:42 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1506 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 Subject: Re: [PHP-DEV] Upgrading php From: steph@zend.com ("Steph Fox") 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" To: "Andi Gutmans" Cc: ; 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 >