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

Joshua Eichorn wrote:

Alexey Borzov wrote:

Hi, Joshua Eichorn wrote:

What does E_Strict entail as of 5.1.4 I've looked in the PHP manual but I can't seem to find a definition of what it actually means. With var being allowed it doesn't seem like it takes much to get too E_Strict

One has to grep the source, I suppose... I did, and here are the findings: Calling functions not defined as 'static' statically Using the '=& new' construct Using deprecated is_a() Using the old-style constructor Incompatible declarations of inherited methods There are also some E_STRICT errors dealing with references and deprecated methods, but I'm not sure about the context. In a nutshell: all code that does require_once 'PEAR.php'; is not E_STRICT-compatible.

So wouldn't the simple solution be creating a php5 PEAR.php and a new include that gives you the 5 version on 5 and the current version on 4.

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). regards, Lukas