Re: Re: E_STRICT
| From: | David Costa | Date: | Fri, 09 Jul 2004 12:13:41 +0000 |
| Subject: | Re: Re: E_STRICT | ||
| References: | 1 2 | Groups: | php.pear.dev php.pear.dev php.pear.dev |
| Request: | Send a blank email to pear-dev+get-31790@lists.php.net to get a copy of this message | ||
On Jul 9, 2004, at 2:08 PM, Hans Lellelid wrote:
Hi Lukas, Lukas Smith wrote: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 Costajust 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.)