From: "Zeev Suraski" <[EMAIL PROTECTED]>
> At 08:14 14/1/2001, Chris Newbill wrote:
> >What would be the cons of having these type of errors simply causing
> >E_USER_ERROR instead of E_ERROR? That way they would be trapable and I
> >don't think it would cause a problem if the user does not have a
At 08:14 14/1/2001, Chris Newbill wrote:
>Skimming the Zend code...
>
>Calls to undefined functions, class methods, and the like.
>
>What would be the cons of having these type of errors simply causing
>E_USER_ERROR instead of E_ERROR? That way they would be trapable and I
>don't think it would c
gt; Thanks,
> Chris Newbill
>
> - Original Message -
> From: "Rasmus Lerdorf" <[EMAIL PROTECTED]>
> To: "Chris Newbill" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Saturday, January 13, 2001 10:51 PM
> Subject: Re: [PHP-DEV]
rday, January 13, 2001 10:51 PM
Subject: Re: [PHP-DEV] set_error_handler() not handling E_ERROR
> This was covered recently. See
> http://marc.theaimsgroup.com/?l=php-dev&m=97673386418430&w=2
>
> On Sat, 13 Jan 2001, Chris Newbill wrote:
>
> > PHP Version 4.0.3pl1 and
This was covered recently. See
http://marc.theaimsgroup.com/?l=php-dev&m=97673386418430&w=2
On Sat, 13 Jan 2001, Chris Newbill wrote:
> PHP Version 4.0.3pl1 and 4.0.4
>
> It was my understanding that when using set_error_handler() ALL errors were
> sent to the users function? This does not see
PHP Version 4.0.3pl1 and 4.0.4
It was my understanding that when using set_error_handler() ALL errors were
sent to the users function? This does not seem to be happening.
error.lib
$oeh = set_error_handler("dosojin_ERROR");
error_reporting(E_ERROR | E_WARNING | E_PARSE | E_CORE_ERROR |
E_C
