Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:45356 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 27549 invoked from network); 24 Aug 2009 20:45:10 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Aug 2009 20:45:10 -0000 Authentication-Results: pb1.pair.com smtp.mail=php-php-dev@m.gmane.org; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=news@ger.gmane.org; sender-id=pass Received-SPF: pass (pb1.pair.com: domain m.gmane.org designates 80.91.229.12 as permitted sender) X-PHP-List-Original-Sender: php-php-dev@m.gmane.org X-Host-Fingerprint: 80.91.229.12 lo.gmane.org Linux 2.6 Received: from [80.91.229.12] ([80.91.229.12:35867] helo=lo.gmane.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3A/B3-03363-4DBF29A4 for ; Mon, 24 Aug 2009 16:45:09 -0400 Received: from list by lo.gmane.org with local (Exim 4.50) id 1MfgPX-0003f5-9R for internals@lists.php.net; Mon, 24 Aug 2009 22:45:03 +0200 Received: from lv426.tranquillo.net ([64.62.158.120]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 24 Aug 2009 22:45:03 +0200 Received: from rabbitt by lv426.tranquillo.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 24 Aug 2009 22:45:03 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: internals@lists.php.net Date: Mon, 24 Aug 2009 16:33:23 -0400 Lines: 32 Message-ID: References: <4A92D936.2010107@zend.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Gmane-NNTP-Posting-Host: lv426.tranquillo.net User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) In-Reply-To: <4A92D936.2010107@zend.com> Sender: news Subject: Re: [PHP-DEV] [patch] error masks From: rabbitt@gmail.com ("Carl P. Corliss") Stanislav Malyshev wrote: > Hi! > > I've implemented a patch that allows to "mask" certain types of errors - > i.e. make PHP engine completely ignore them. Now even if the error is > not reported, it passes full cycle through message string creation, all > allocations on the way, etc. even though ultimately the result of it > will be thrown out. So I offer a way to make unwanted errors just > disappear. I know I'm a nobody here but, I think this is a really important change. I have worked in a couple of different companies where we have specifically turned turned down the error log noise in our production environment but kept them turned on fully (E_ALL | E_DEPRECATED) in our dev/staging environments. While our production environments were technically a bit quieter log-wise, there was definitely no apparent performance benefit aside from saving having to write to the logs. In fact, during our transition from 4.x -> 5.x, we noticed a marked slowdown related to generation of E_STRICT messages even when E_STRICT was disabled - which I only realized through stepping through the source via gdb was because it was still going through the motions of creating the messages even though they were discarded later. Again, I know I'm nobody here but, I really hope you find this patch worth committing - I know I would. Thanks for listening, -- Carl P. Corliss