Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:24362
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <44B58A36.2010900@php.net>
Date: Thu, 13 Jul 2006 01:48:06 +0200
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: Lukas Smith <lsmith@php.net>
Cc: internals@lists.php.net
References: <0F.C0.46743.0CB15B44@pb1.pair.com>
In-Reply-To: <0F.C0.46743.0CB15B44@pb1.pair.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: E_STRICT
From: lsmith@php.net (Lukas Smith)

Lukas Smith wrote:

Ok I see 2 options:

1)
> Obviously one solution would be to disallow making anything an E_STRICT 
> notice that is not available since the first release of the given major 
> version.

Pierre and Anthony seem to favor this solution.

2)
> Adding such a filter API into PHP internals however seems like a 
> considerably effort. Therefore my proposal would be to simply add a 
> defined "header" to all E_STRICT messages that contains the PHP version 
> in which this E_STRICT message was added. This way PEAR could provide 
> its developer with a simple filter method that would take an error 
> message inside a customer error handler and determine if it should be 
> filtered out or not.

 From IRC discussions and the PEAR ML I think Michael and Marcus favor 
this solution. I also prefer this solution.

regards,
Lukas