Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:6552
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
To: internals@lists.php.net
Date: Thu, 18 Dec 2003 18:52:35 +0100
User-Agent: KMail/1.5.94
References: <20031218124303.18e22274.paj@pearfr.org> <20031218171530.GA17635@panix.com> <3FE1E318.3060004@cschneid.com>
In-Reply-To: <3FE1E318.3060004@cschneid.com>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-ID: <200312181852.38575.magnus@php.net>
Subject: Re: [PHP-DEV] B3, pear segfault, and msgs about deprecated
From: magnus@php.net (Magnus =?iso-8859-1?q?M=E4=E4tt=E4?=)

On Thursday 18 December 2003 18.25, Christian Schneider wrote:
> Daniel Convissor wrote:
> > It's the custom error handler in pearcmd.php.  PHP doesn't pay attention
> > to any error_reporting() settings when a custom error handler is
> > established.  Then, error_handler() doesn't account for the new warning
> > level.
>
> Is it just me or is this undesired behaviour? I noticed this back when I
> was playing around with error_handlers.
>
> I think this should be treated as a bug and be changed for two reasons:
> 1) It seems illogical that an error_handler is called for an error level
> which is disabled in php.ini
> 2) It's a performance issue since the custom error handler is called for
> e.g. every access to an undefined array index even though I disabled
> that warning.

I find this very useful and don't think it should be changed, maybe
it's just me.


/Magnus

-- 
Marriage is a lot like the army, everyone complains, but you'd be
surprised at the large number that re-enlist.
		-- James Garner