Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:55831 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 75254 invoked from network); 17 Oct 2011 06:55:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Oct 2011 06:55:03 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.183 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.183 smtp183.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.183] ([67.192.241.183:52501] helo=smtp183.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id EF/22-50906-641DB9E4 for ; Mon, 17 Oct 2011 02:55:03 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp8.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 3E8FB8120; Mon, 17 Oct 2011 02:54:59 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp8.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id EB3AA80E7; Mon, 17 Oct 2011 02:54:58 -0400 (EDT) Message-ID: <4E9BD142.8060806@sugarcrm.com> Date: Sun, 16 Oct 2011 23:54:58 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: Sebastian Bergmann CC: "internals@lists.php.net" References: <4E95AB4E.6040302@sugarcrm.com> <4E9B7CDF.4090106@php.net> In-Reply-To: <4E9B7CDF.4090106@php.net> 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: smalyshev@sugarcrm.com (Stas Malyshev) Hi! On 10/16/11 5:54 PM, Sebastian Bergmann wrote: > Such a performance regression sounds like an appropriate "punishment" to > me for deploying bad code ;-) By bad code you mean not obsessively checking for stuff that is of no importance to them as programmers and is only required because language implementers decided to go B&D on their users? ;) I personally hate to see all these isset($foo['bar'])?$foo['bar']:null. I think it's bad we make people do that. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227