Re: [PEPr] Comment on RFC::Requiring E_STRICT Compatibility for New PEAR Packages
| From: | Alexey Borzov | Date: | Mon, 10 Jul 2006 19:43:21 +0000 |
| Subject: | Re: [PEPr] Comment on RFC::Requiring E_STRICT Compatibility for New PEAR Packages | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-43342@lists.php.net to get a copy of this message | ||
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_StrictOne 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.