Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:20190
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <014501c5edd2$140c1b60$50906751@foxbox>
Reply-To: "Steph Fox" <steph@zend.com>
To: "Eric Coleman" <eric@aplosmedia.com>
Cc: "Andi Gutmans" <andi@zend.com>, "Jani Taskinen" <sniper@iki.fi>,
	<truth@proposaltech.com>, <internals@lists.php.net>
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> <Pine.LNX.4.61.0511180959210.4255@arfg.argcubovn.sv> <6.2.3.4.2.20051118113030.03382ab0@localhost> <18191EE7-055A-4EF8-BFE6-B3399E7ADEC3@aplosmedia.com> <009c01c5ed82$841e0b20$50906751@foxbox> <65655689-EF3A-4631-8C1C-312477A4653E@aplosmedia.com>
Date: Sun, 20 Nov 2005 12:58:15 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Upgrading php
From: steph@zend.com ("Steph Fox")

The PHP_CompatInfo package simply evaluates a script to find which is the
minimum version of PHP able to run it.  Obviously it'll need updating for
PHP 5.1, and it may well be a helpful tool for users deciding whether an
upgrade is a good idea, but it's unlikely to be useful in the context under
discussion.

Andi was thinking of an auto-conversion tool for PHP 6 (something like
autoconf's autoupdate) - this isn't something that's likely to be achievable
in userspace code.

- Steph


----- Original Message ----- 
From: "Eric Coleman" <eric@aplosmedia.com>
To: "Steph Fox" <steph@zend.com>
Cc: "Andi Gutmans" <andi@zend.com>; "Jani Taskinen" <sniper@iki.fi>;
<truth@proposaltech.com>; <internals@lists.php.net>
Sent: Sunday, November 20, 2005 4:34 AM
Subject: Re: [PHP-DEV] Upgrading php


> 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" <eric@aplosmedia.com>
> > To: "Andi Gutmans" <andi@zend.com>
> > Cc: "Jani Taskinen" <sniper@iki.fi>; <truth@proposaltech.com>;
> > <internals@lists.php.net>
> > 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
> >>
> >
>
> -- 
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>