Re: Seeking direction

From: Date: Fri, 15 Sep 2006 17:04:10 +0000
Subject: Re: Seeking direction
References: 1 2  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-43944@lists.php.net to get a copy of this message
On 2006 09 15 12:41, Justin Patrin wrote:
On 9/15/06, Alan Langford <jal@ambitonline.com> wrote:
Hello all: I've been making extensive use of PEAR for several years now and I recently decided to tackle a transition to PHP5. One of my coding requirements is that an application run error-free with everything except E_NOTICE turned on. So I tried PHP5 with a large e-commerce application. Lets just say that I retreated back to PHP4 very quickly! I'm starting work on a major new application. It's loaded with XML work, so I really want to use PHP5 for it. I've read and agree with the proposal to make packages run clean with E_STRICT. I also have a number of my own libraries that are built upon the PEAR foundation. Obviously there's a lot that needs to be done to get PHP5 versions of a lot of packages ready, and since this is keeping me from my objectives, I'd like to help. I don't want to go duplicating effort, so the question is: is there someone coordinating this work? Where is a good place to start? Here's my current list of installed packages. Obviously working on some of these is my preference: Archive_Tar Auth_SASL Console_Getopt DB HTML_Common HTML_QuickForm HTML_Template_IT HTML_Template_PHPLIB HTML_Template_Sigma HTTP HTTP_Request Log MDB2 Mail Mail_Mime Net_SMTP Net_Socket Net_URL PEAR PHP_Beautifier XML_Beautifier XML_Parser XML_RPC XML_Util
I really suggest that you just turn off E_STRICT for now. All of those packages should work fine in PHP5 and you're going to be waiting a long time for them all to be released as PHP5-only versions.... Okay, maybe I'm missing something here. In my configuration,
if (PEAR::isError($foo)) {} generates a warning because isError isn't declared static. This is way above E_STRICT. Sure, I know I want to grab these things and throw an exception instead, but I want to be able to do that without suppressing warnings all over the place. The recent proposal "RFC::Requiring E_STRICT Compatibility for New PEAR Packages." got overwhelming support. What I'm doing here is offering my services to make that "waiting a long time" as short as possible.

« previous php.pear.dev (#43944) next »