Re: [PEPr] Comment on RFC::Requiring E_STRICT Compatibility for New PEAR Packages

Hi, Lukas Smith wrote:

Lukas Smith (http://pear.php.net/user/lsmith) has commented on the proposal for RFC::Requiring E_STRICT Compatibility for New PEAR Packages. Comment: I also think it is time we nudge people a bit more strongly towards PHP5. Even if PHP5 is not the standard at this point, we need to realize that its also in our hands to change the tides. I would however leave some option open for PHP4 packages. Maybe simply increase the required +1 total to be higher than for PHP5 packages (say : 10 or 15).

No, the whole purpose of this RFC is to discourage development of new packages for PHP4 and to encourage moving the existing packages to PHP5 versions. Adding this option defeats the purpose. There are two possibilities of a PHP4 package proposal: 1) A PEARified version of an existing library is proposed. Fortunately we have channels now and the author can distribute this library from his own site. 2) This is indeed a new package. There is no sense starting development in PHP4 if the package may stabilize only when PHP4 is completely obsolete. We won't accept PHP3 package, even if it gains a whopping +50 on PEPr, will we?

Also I think we should simply mandate that packages always adhere to the highest error reporting level for the lowest supported PHP major version. That should become a CS guideline.

+1