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" <[EMAIL PROTECTED]>
To: "Andi Gutmans" <[EMAIL PROTECTED]>
Cc: "Jani Taskinen" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
<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
