Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:20187 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 8599 invoked by uid 1010); 20 Nov 2005 04:34:19 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 8584 invoked from network); 20 Nov 2005 04:34:19 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Nov 2005 04:34:19 -0000 X-Host-Fingerprint: 70.85.198.202 unknown Linux 2.4/2.6 Received: from ([70.85.198.202:33696] helo=orange.aplosmedia.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 2F/4D-11378-BCCFF734 for ; Sat, 19 Nov 2005 23:34:19 -0500 Received: (qmail 8978 invoked from network); 19 Nov 2005 22:34:15 -0600 Received: from c-24-3-184-5.hsd1.pa.comcast.net (HELO ?192.168.2.2?) (24.3.184.5) by 206.70-85-198.reverse.theplanet.com with SMTP; 19 Nov 2005 22:34:15 -0600 In-Reply-To: <009c01c5ed82$841e0b20$50906751@foxbox> 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> <6.2.3.4.2.20051118113030.03382ab0@localhost> <18191EE7-055A-4EF8-BFE6-B3399E7ADEC3@aplosmedia.com> <009c01c5ed82$841e0b20$50906751@foxbox> Mime-Version: 1.0 (Apple Message framework v746.2) X-Priority: 3 Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-ID: <65655689-EF3A-4631-8C1C-312477A4653E@aplosmedia.com> Cc: "Andi Gutmans" , "Jani Taskinen" , , Content-Transfer-Encoding: 7bit Date: Sat, 19 Nov 2005 23:34:13 -0500 To: "Steph Fox" X-Mailer: Apple Mail (2.746.2) Subject: Re: [PHP-DEV] Upgrading php From: eric@aplosmedia.com (Eric Coleman) Im aware of that, but my thinking was to add the things in for that.... Maybe Davey will be willing, or I could give it a shot and see. -- Eric Coleman http://aplosmedia.com home: 412 399 1024 cell: 412 779 5176 On Nov 19, 2005, at 10:28 PM, Steph Fox wrote: > Current release: 1.0.0 (stable) was released on 2005-03-15 > > That means it's not up to date enough to help with 5.0 -> 5.1 > upgrades... > > > ----- Original Message ----- > From: "Eric Coleman" > To: "Andi Gutmans" > Cc: "Jani Taskinen" ; ; > > Sent: Sunday, November 20, 2005 3:24 AM > Subject: Re: [PHP-DEV] Upgrading php > > >> What about using http://pear.php.net/package/PHP_CompatInfo as a >> basis? It seemed to do a pretty good job last time I ran it... >> >> - Eric >> -- >> Eric Coleman >> >> http://aplosmedia.com >> home: 412 399 1024 >> cell: 412 779 5176 >> >> >> On Nov 18, 2005, at 2:33 PM, Andi Gutmans wrote: >> >>> Yep that's definitely a good start. The two things we might want to >>> improve on are: >>> a) Not require PHP 5 in order to detect these issues when PHP 6 >>> comes a long. >>> b) Have a script that automatically makes the changes that can be >>> done without human intervention. >>> >>> We had something similar to (a) and (b) when we moved people from >>> PHP/FI 2 to PHP 3 as there were some significant differences. That >>> said, it's not always simple because you might need to have to >>> reuse the scanner/parser and a simple PHP script might not be >>> enough. >>> >>> Hopefully, as we get closer to PHP 6 there will be people who have >>> time to invest in this. >>> Most important thing at this point, is to keep the upgrading docs >>> (which will be first released with 5.1) in sync with the changes, >>> so that when the time comes with PHP 6, it'll be easy to translate >>> the docs to such a script, without forgetting half the stuff that >>> was changed. >>> >>> Andi >>> >>> At 12:06 AM 11/18/2005, Jani Taskinen wrote: >>>> 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 >>> >> >> -- >> PHP Internals - PHP Runtime Development Mailing List >> To unsubscribe, visit: http://www.php.net/unsub.php >> >