Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:45375 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 79908 invoked from network); 24 Aug 2009 23:30:31 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Aug 2009 23:30:31 -0000 Authentication-Results: pb1.pair.com smtp.mail=ilia@prohost.org; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=ilia@prohost.org; sender-id=unknown Received-SPF: error (pb1.pair.com: domain prohost.org from 209.85.221.193 cause and error) X-PHP-List-Original-Sender: ilia@prohost.org X-Host-Fingerprint: 209.85.221.193 mail-qy0-f193.google.com Received: from [209.85.221.193] ([209.85.221.193:42401] helo=mail-qy0-f193.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 6F/2F-03363-792239A4 for ; Mon, 24 Aug 2009 19:30:31 -0400 Received: by qyk31 with SMTP id 31so378148qyk.27 for ; Mon, 24 Aug 2009 16:30:28 -0700 (PDT) Received: by 10.224.123.231 with SMTP id q39mr3414943qar.80.1251156628742; Mon, 24 Aug 2009 16:30:28 -0700 (PDT) Received: from ?192.168.0.199? (76-10-171-174.dsl.teksavvy.com [76.10.171.174]) by mx.google.com with ESMTPS id 4sm2593493qwe.5.2009.08.24.16.30.27 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 24 Aug 2009 16:30:27 -0700 (PDT) Cc: Stanislav Malyshev , 'PHP Internals' Message-ID: <39F20BFC-DAA0-4403-A52E-62CE5F4CF0FE@prohost.org> To: Greg Beaver In-Reply-To: <4A931A1C.804@chiaraquartet.net> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Mon, 24 Aug 2009 19:30:25 -0400 References: <4A92D936.2010107@zend.com> <4A931A1C.804@chiaraquartet.net> X-Mailer: Apple Mail (2.936) Subject: Re: [PHP-DEV] Re: [patch] error masks From: ilia@prohost.org (Ilia Alshanetsky) On 24-Aug-09, at 6:54 PM, Greg Beaver wrote: > > 2) as long as the patch does not break any backwards compatibility > (error logging still works as it always did independent of error_mask, > user error handlers still get the same stuff), why would we care? > There > is a time and place for being academic about fixing things and it is > called development, not production. You must not have any bugs in production environment, I am very envious. :-)