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

Alexey Borzov wrote:

Hi, Joshua Eichorn wrote:

That would be a solution that breaks our BC standards (though maybe still sensible). But its also more related to another RFC that passed long ago on what error handling mechanism should be used for PHP5 (even if PEAR.php provides some non error handling related features).

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.

We've gained couple hundred packages that are forward-compatible, i.e. will not break spectacularly when E_STRICT is promoted to E_ERROR. Well except for i'm sure the PHP devs will break lots of other things before even php6 is out and if we release new versions of every package as soon as possible will quickly be up too MDB7 etc.

So lets say I try to support E_STRICT and because of whatever reason (but this reason would be at most 2 or 3 lines of code) its impossible while still supporting PHP4. Why would I want to release HTML_AJAX2.

Please note that the RFC in question deals only with new package proposals and new major versions. It does not *force* you to release HTML_AJAX2. It will only have serious impact on a couple dozen existing packages that are heavily depended upon. Of course HTML_AJAX2 will be needed if a developer wants to use it in his E_STRICT-compatible package, but then you can strike an agreement with that developer that he'll help you with maintaining the package. ;] That doesn't help me much.

The requests im getting right now are for HTML_Quickform and DB_DataObject_FormBuilder integration The standard way to add new features to Quickform is too make a new package. Once this passes i'll be doubly un-allowed too add a new one since neither Quickform or HTML_AJAX are E_STRICT compatible. -josh