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

Philippe Jausions (http://pear.php.net/user/jausions) has commented on the proposal for RFC::Requiring E_STRICT Compatibility for New PEAR Packages. Comment: I don't really see the point of this RFC. Packages make their way into PEAR because people wrote them and wanted to share them with the rest of the world. Sometimes these packages *had* to be written in PHP4. And some other users may need such a version as well. I understand the need to move forward to PHP5, but if people can't use a PHP5 version of a package and a PHP4 is available, the RFC shouldn't forbid the PH4 package to make it into PEAR. The RFC should state that new packages must provide a PHP5 E_STRICT version, but not restrict to that version only. The dependency on E_STRICT packages will slow development if nothing is done first to up some major existing packages. In the (recent) past when a PHP5 package was submitted, a PHP4 version was asked if the said package was not really using PHP5-only features. I guess these kind of backward compatibility requests should be discouraged. Proposal information: http://pear.php.net/pepr/pepr-proposal-show.php?id=419 -- Sent by PEPr, the automatic proposal system at http://pear.php.net