Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:20121 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 2357 invoked by uid 1010); 18 Nov 2005 00:54:19 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 2342 invoked from network); 18 Nov 2005 00:54:19 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Nov 2005 00:54:19 -0000 X-Host-Fingerprint: 80.74.107.235 mail.zend.com Linux 2.5 (sometimes 2.4) (4) Received: from ([80.74.107.235:15591] helo=mail.zend.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id CF/FF-07637-A362D734 for ; Thu, 17 Nov 2005 19:54:18 -0500 Received: (qmail 24129 invoked from network); 18 Nov 2005 00:54:13 -0000 Received: from localhost (HELO ANDI-NOTEBOOK.zend.com) (127.0.0.1) by localhost with SMTP; 18 Nov 2005 00:54:13 -0000 Message-ID: <6.2.3.4.2.20051117165150.028458b0@localhost> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Thu, 17 Nov 2005 16:54:05 -0800 To: truth@proposaltech.com,internals@lists.php.net In-Reply-To: <1132274666.8441.175.camel@notebook> 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> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: Re: [PHP-DEV] Upgrading php From: andi@zend.com (Andi Gutmans) Hi Todd, 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. Main problem is that currently there haven't been the people to get it done. We did write some upgrading docs for 5.1 (not sure if they made it into the RC but they can always make it to the site), but this whole area needs a lot more work and help. Andi At 04:44 PM 11/17/2005, Todd Ruth wrote: >I'd been ignoring the "curly braces" thread, but then I grepped my >code and ... sure enough, I have curly braces that are used to index >into strings. I don't care about this philosophically, but it makes >me wonder about upgrade tools. I know I shouldn't ask this without >volunteering to do it myself, but when a version of php comes out >that makes such a change, is there any chance of having a tool that >updates the code available at the same time? > >It seems to me that nothing understands php user code better than the >core php code, so perhaps a tool could be written that uses the guts >of php as a base. I suppose there are some IDEs that could do the >job as well. Sadly, I still use vi, but I bet if something were written >for emacs or eclipse, most people (even me) could learn to use it. >I'm dreading going to php5. I hear that to avoid warnings/notices >I'll need to convert a bunch of "var"s to "public"s. I'll need to >wrap my "get_class"s with "strtolower"s. etc. > >It would be so wonderful to throw all my code at a tool that would >change everything that can be easily changed and give me a list of >spots I need to look at manually. A lot of the changes don't take >an overwhelming amount of time to do myself, but when you think >about the thousands of users all doing the same conversions, it just >makes sense for there to be a tool. It might also have the side >benefit of reducing long threads about breaking old code. > >Perhaps this already exists and I've missed it. Perhaps it will >never exist because it isn't enough fun to write. Just an idea... > >- Todd > >-- >PHP Internals - PHP Runtime Development Mailing List >To unsubscribe, visit: http://www.php.net/unsub.php