Re: Re: Making old PEAR packages (more) E_STRICT compatible

This would be usefull - especially a static infront of getStaticProperties() But I guess you will need to either a) create a temporary PEAR_PHP5 package - that overwrites PEAR.php b) release a PHP5 only version of the PEAR package, - which could be fraught with problems (installing with PHP5 on a server running both PHP4/PHP5 - breaking all code... etc. Regards Alan Gregory Beaver wrote:

Christian Schmidt wrote:

Gregory Beaver wrote:

    
I think that the solution is not likely to be hacking on php4 packages

to make them less E_STRICT-able. Pyrus is nearly ready for a first devel release, and the playing field for PEAR2 will be wide open for those who wish to E_STRICTify existing packages in a more exciting environment.

I agree that PEAR2 is the way ahead, and I will definately transition from old PEAR packages to PEAR2 equivalents as they become available. However, I assume it will take months or even years before the majority of existing packages has been converted to PEAR2 or PHP5-compatible PEAR packages. By making some mostly uncomplicated adjustments to the existing packages, people can turn on E_STRICT warnings (with a custom error handler) already in a few weeks. I believe this may be attractive to many users.

Hi, If you feel these changes can be done with minimal work, no BC issues, and no maintenance issues, I would not oppose them. However, I did not get the impression that it would be minimal. Please feel free to open bugs for specific packages with patches to do this, I'm sure devs would appreciate the time and energy you would put into it.

I appreciate your work on PEAR2, and I am glad to see that PHP5 usage is finally gaining som momentum. On the other hand, I think it is worth spending a little effort on improving the current situation until all important packages have been made PHP5-compatible. It appears as if many package owners are not yet ready to abandon PHP4, and as long as that is the case, I don't see any reason not to make their PHP4-compatible packages slightly more "PHP5-friendly". But that of course is the individual package owner's call. I do hope, though, that you are willing to accept a patch that removes E_STRICT warnings from PEAR.php (something along the lines of what I mentioned in my original message) as this file is used by all other PEAR packages. Then at least package owners can decide for themselves whether they want to make their PHP4-compatible package PHP5-friendly.

All efforts are useful :) Greg