Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:6550 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 95104 invoked by uid 1010); 18 Dec 2003 17:47:07 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 95079 invoked from network); 18 Dec 2003 17:47:07 -0000 Received: from unknown (HELO jdi.jdimedia.nl) (212.204.192.51) by pb1.pair.com with SMTP; 18 Dec 2003 17:47:07 -0000 Received: from localhost (localhost [127.0.0.1]) by jdi.jdimedia.nl (8.12.10/8.12.10) with ESMTP id hBIHl36g031487; Thu, 18 Dec 2003 18:47:03 +0100 Date: Thu, 18 Dec 2003 18:47:03 +0100 (CET) X-X-Sender: derick@localhost To: Christian Schneider cc: PHP Internals List In-Reply-To: <3FE1E318.3060004@cschneid.com> Message-ID: References: <20031218124303.18e22274.paj@pearfr.org> <20031218140527.GA26390@panix.com> <3FE1D96B.3090308@chiaraquartet.net> <20031218170305.GA16670@panix.com> <3FE1DEF9.4060705@chiaraquartet.net> <20031218171530.GA17635@panix.com> <3FE1E318.3060004@cschneid.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [PHP-DEV] B3, pear segfault, and msgs about deprecated From: derick@php.net (Derick Rethans) On Thu, 18 Dec 2003, 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. No, it's desired behavior. > 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. Performance and error handling don't go together. It's not a valid argument and the current behavior IS the way it should be. (Please search the archives for reasons, we discussed this before here). Derick