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

Joshua Eichorn wrote:

It just seems silly to me to rewrite a couple hundred packages making a 1% or less change. Now we have twice the # of packages to support and we've gained nothing except for making a couple people who really like running with E_STRICT on happy.

The point is to focus on the future for new packages. I do not envision a flurry of package rewriting. Just as we have not had that in the past. Certainly making a package E_STRICT only is a very bad reason to write a new major version. However making a package PHP5 only gives you the opportunity to properly use private/protected without having to rely on documentation. There are plenty of other things that will get simplified. And the main reason to do a rewrite should be a need for some API clean ups. All this RFC says is that if you do a rewrite after that date, it should be in PHP5. We intend to support packages during their entire lifetime and therefore we commit to code for more than a year or two. So if we allow PHP4 packages into PEAR until the day that PHP4 is obsolete we carry alot of baggage. Also its a signal that will be heard among hosters. I am quite sure it will. It will be a signal for their users for sure. So I think its an opportunity to shape our future just as much. regards, Lukas