Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:55830 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 52990 invoked from network); 17 Oct 2011 00:55:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Oct 2011 00:55:03 -0000 Authentication-Results: pb1.pair.com smtp.mail=sebastian@php.net; spf=unknown; sender-id=unknown Authentication-Results: pb1.pair.com header.from=sebastian@php.net; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 93.190.64.36 as permitted sender) X-PHP-List-Original-Sender: sebastian@php.net X-Host-Fingerprint: 93.190.64.36 mail-6.de-punkt.de Received: from [93.190.64.36] ([93.190.64.36:36749] helo=mail-6.de-punkt.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 69/10-50906-5EC7B9E4 for ; Sun, 16 Oct 2011 20:55:03 -0400 Received: (qmail 6406 invoked by uid 511); 17 Oct 2011 00:55:09 -0000 Received: by simscan 1.3.1 ppid: 6398, pid: 6402, t: 0.3879s scanners: attach: 1.4.0 Received: from unknown (HELO ?0.0.0.0?) (sb%sebastian-bergmann.de@217.114.76.105) by 0 with ESMTPA; 17 Oct 2011 00:55:09 -0000 Message-ID: <4E9B7CDF.4090106@php.net> Date: Sun, 16 Oct 2011 17:54:55 -0700 Organization: PHP Development Team User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0) Gecko/20110927 Thunderbird/7.0 MIME-Version: 1.0 To: internals@lists.php.net References: <4E95AB4E.6040302@sugarcrm.com> In-Reply-To: <4E95AB4E.6040302@sugarcrm.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] #60038 SIGALRM cause segfault in php_error_cb From: sebastian@php.net (Sebastian Bergmann) On 10/12/2011 07:59 AM, Stas Malyshev wrote: > Note that on 99% of real PHP code, dozens of "errors" may happen due to > multitude of notices and E_STRICTs that we have now and we have no means > to disable until the very last moment before printing them. Such a performance regression sounds like an appropriate "punishment" to me for deploying bad code ;-) -- Sebastian Bergmann Co-Founder and Principal Consultant http://sebastian-bergmann.de/ http://thePHP.cc/