Selectable error messages View as Markdown

hi Lester,

Short of switching display_errors on and off all the time, how do other
people handle this irritation? I could repair phpDocumentor in this case and
ignore BC as I will not be running THAT on older version of PHP, and since a
run is taking 30 minutes it would be interesting to see if there is any
improvement to time.

Use error_reporting in your php.ini or within your applicaion:
error_reporting(E_ALL ^ E_DEPRECATED);

Cheers,

Pierre

http://blog.thepimp.net | http://www.libgd.org

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

Hello Lester,

Wednesday, June 18, 2008, 9:14:52 AM, you wrote:

OK - I've got PHP5.3.0-dev up at the moment in order to test the Firebird
stuff, so display_errors is on. I need it on anyway while testing code.

The 'problem' I am having is that of cause none of the other PHP stuff I'm
using is currently not compatible with PHP5.3 so generates a lot of deprecated
warnings in particular.

Current one is phpDocumentor which uses is_a() extensively, and has a function
to replicate it for backwards compatibility.

Hey guys, I thought we undeprecated is_a()?

there is no need whatsoever to deprecate it.

Best regards,
Marcus