Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:38347
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain chsc.dk designates 80.160.77.98 as permitted sender)
Message-ID: <4858F99D.60700@chsc.dk>
Date: Wed, 18 Jun 2008 14:03:41 +0200
User-Agent: Thunderbird 3.0a2pre (Windows/2008061503)
MIME-Version: 1.0
To: php-dev List <internals@lists.php.net>
References: <4858B5EC.90109@lsces.co.uk>
In-Reply-To: <4858B5EC.90109@lsces.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Selectable error messages
From: lists@chsc.dk (Christian Schmidt)

Lester Caine wrote:
> Short of switching display_errors on and off all the time, how do other
> people handle this irritation?

I don't have experiences with E_DEPRECATED, but for E_STRICT we use a 
custom error handler to surpress strict errors in external libraries. 
Not all E_STRICT errors can be caught in this way, especially not if you 
are using an opcode cache.

Our error handler looks like this, perhaps you can do something similar 
for E_DEPRECATED.:


if (!($errorNumber & error_reporting()) ||
     $errorNumber == E_STRICT &&
     (strpos($fileName, '/pear/') !== false ||
      strpos($fileName, '/smarty/') !== false ||
      preg_match('/^Non-static method (DB|HTTP|Mail_RFC822|PEAR)::/',
                 $message))) {

     if ($errorNumber & (E_ERROR | E_RECOVERABLE_ERROR | E_USER_ERROR)) {
         exit;
     }
     return;
}
// Show error message etc.


Christian