Re: PHP5 only sure .. E_STRICT?
| From: | Stefan Neufeind, PEAR | Date: | Thu, 13 Jul 2006 16:12:48 +0000 |
| Subject: | Re: PHP5 only sure .. E_STRICT? | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-43468@lists.php.net to get a copy of this message | ||
Michael Wallner wrote:
> Lukas Smith wrote:
>> Markus Tacker wrote:
>>> So, they say what's E_STRICT will not work in PHP6. What's not may
>>> become E_STRICT in future releases of PHP.
>>
>> No the question was as follows, in the word of Michael:
>> "The key is we would like to know if we can rely that there are no
>> things that throw E_STRICT in a minor version that don't work in a
>> lower minor version"
>>
>> The answer to this question is no, we cannot rely on this.
>> After the obviously heated debate with Marcus we talked in a query in
>> the language of love (also known as german) and we got to a solution
>> that I think is workable for us.
>
> After thinking more about the issue yesterday, I must admit, that
> limiting E_STRICT changes to major versions is really not reasonable
> for PHP development and it could cause a development deadlock.
>
>> All E_STRICT notices would start with an easily parseable string that
>> defines the version in which the given E_STRICT notice was added. This
>> would make it possible for us to provide a filter function that people
>> could use in customer error handlers that would enable them to filter
>> out any E_STRICT error messages they wish to ignore based on the
>> lowest PHP version they want to care about.
>
> Marcus just introduced me to this idea and I think it's actually a quite
> good compromise.
Same here ... sounds fine.
Regards,
Stefan