Re: Re: [PEPr] Comment on Web Services::Services_Digg

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Services_Digg can only get into PEAR if it is E_STRICT compatible, which is the point of the RFC. That means that not only the package needs to be E_STRICT compatible, but also all packages it depends on. While you depend on HTTP_Request (in the current available version), your package can't be accepted if we don't want to break the rules.

Fine, I'll rewrite it to use file_get_contents(). Problem solved. After I'm done with that I'll be proposing and RFC that states not only do we not accept packages that aren't E_STRICT in PHP 5+, but that we also no longer allow people to even release new versions of non-PHP5 packages. Instantly deprecating hundreds of PHP4 packages sounds like a great idea to me (since that's what this RFC has essentially done). Then, maybe, people will start porting their code to PHP5 rather than letting PEAR flounder in the abyss of PHP4 BC-compliancy. I mean, seriously, PHP5 has been out for *years* and PHP6 is on it's way. Why are we still having PHP4-related RFC flame wars? The problem I have with this RFC is exactly what Greg has said; it stops people from contributing valid code in favor of keeping things status quo. I have zero power to force a rewrite of HTTP_Request2 so my package is denied and PEAR is out one more valid package. - --Joe -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFGK7lOh0MUGpYY9OQRAlIpAJ9tAzdCBUfsY58hDJaDIsL/Ew5okACdHEn5 GaGWz2RFa2OAvhQuXhR/Hio= =U10/ -----END PGP SIGNATURE-----