Re: Re: E_STRICT

For whatever it is worth, I just wanted to add that I always code with E_ALL using php4 and plan to code with E_STRICT on php5. If a PEAR package didn't conform to E_STRICT I would be prevented from using the package, or prevented from using E_STRICT; neither option is good. Thanks, Matt Friedman Symcor Inc. David Costa <gurugeek@php.net To: Hans Lellelid <hans@velum.net> > cc: Lukas Smith <lsmith@php.net>, > "'pear-dev@lists.php.net'" <pear-dev@lists.php.net> 09/07/2004 08:13 Subject: Re: [PEAR-DEV] Re: E_STRICT AM On Jul 9, 2004, at 2:08 PM, Hans Lellelid wrote: > Hi Lukas, > > Lukas Smith wrote: >> just wanted to clarify that there was also never a decision that >> E_STRICT is a requirement for PHP5 only packages. Its just what I >> said on IRC to David a while back. > > I remember seeing it in a list email (not that that makes it any more > of a decision). I agreed with your reasoning, though, at the time. > If PHP4 packages must run w/ E_NOTICE then PHP5 packages should run in > E_STRICT. It makes sense, especially if E_STRICT errors will > eventualy become regular warnings or notices in PHP. (It seems like > that could happen given that E_STRICT is a way to "ease" people into > the new object model.) I agree and I am thankful to Lukas for the suggestion early on. Clearly it is not a rule written in stone but common sense and good coding practices suggest that if you want to do a PHP 5 only package you should provide with some benefits and reasoning to do that vs running on PHP 5 a PHP 4 package. It is certainly nothing binding yet, but as far as I have seen all the PHP 5 only packages & proposal do fit within the E_STRICT compliance rules. Regards David Costa -- PEAR Development Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php