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

From:	Alan Knowles	Date:	Tue, 11 Jul 2006 00:01:36 +0000
Subject:	Re: Re: [PEPr] Comment on RFC::Requiring E_STRICT Compatibility for New PEAR Packages
References:	1 2	Groups:	php.pear.dev
Request:	Send a blank email to pear-dev+get-43359@lists.php.net to get a copy of this message

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

Cant remember if that one's staying? - that breaks BC/FC code!

Using the '=& new' construct Using deprecated is_a()

That got removed from what I remember.. -> instance of could not handle negative testing.. Regards Alan

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.