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

From:	Joshua Eichorn	Date:	Mon, 10 Jul 2006 19:36:38 +0000
Subject:	Re: [PEPr] Comment on RFC::Requiring E_STRICT Compatibility for New PEAR Packages
References:	1 2 3	Groups:	php.pear.dev
Request:	Send a blank email to pear-dev+get-43339@lists.php.net to get a copy of this message

Pierre wrote:

On 10 Jul 2006 19:24:15 -0000, Joshua Eichorn <jeichorn@joshuaeichorn.com> wrote:
Joshua Eichorn (http://pear.php.net/user/jeichorn) has commented on the proposal for RFC::Requiring E_STRICT Compatibility for New PEAR Packages. Comment: 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
It was more about requiring the last (by all means) 5.1.0 version and not 5.0. --Pierre Im just wondering if E_STRICT is really an issue at all any more. Isn't it just making sure your not throwing any reference bugs, or do method definitions without public/private still throw errors.

And if thats the case then its stupid to require a new version to do s/function/public function/g -josh