Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:55838 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 15388 invoked from network); 17 Oct 2011 12:50:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Oct 2011 12:50:03 -0000 Authentication-Results: pb1.pair.com smtp.mail=ilia@prohost.org; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=ilia@prohost.org; sender-id=pass Received-SPF: pass (pb1.pair.com: domain prohost.org designates 209.85.215.170 as permitted sender) X-PHP-List-Original-Sender: ilia@prohost.org X-Host-Fingerprint: 209.85.215.170 mail-ey0-f170.google.com Received: from [209.85.215.170] ([209.85.215.170:46645] helo=mail-ey0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id DD/33-27630-7742C9E4 for ; Mon, 17 Oct 2011 08:50:00 -0400 Received: by eyg7 with SMTP id 7so2831805eyg.29 for ; Mon, 17 Oct 2011 05:49:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.14.17.27 with SMTP id i27mr254936eei.133.1318855796273; Mon, 17 Oct 2011 05:49:56 -0700 (PDT) Received: by 10.14.127.136 with HTTP; Mon, 17 Oct 2011 05:49:56 -0700 (PDT) In-Reply-To: References: <4E95AB4E.6040302@sugarcrm.com> <4E9B7CDF.4090106@php.net> <4E9BD142.8060806@sugarcrm.com> Date: Mon, 17 Oct 2011 08:49:56 -0400 Message-ID: To: Ferenc Kovacs Cc: Stas Malyshev , Sebastian Bergmann , "internals@lists.php.net" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] #60038 SIGALRM cause segfault in php_error_cb From: ilia@prohost.org (Ilia Alshanetsky) Unless you are deleting thousands of files in a tight loop, the overhead involved won't make any difference for your application. In general your application is throwing many errors, even "benign" E_STRICT or E_NOTICE you are already incurring a performance hit. On Mon, Oct 17, 2011 at 3:49 AM, Ferenc Kovacs wrote: > On Mon, Oct 17, 2011 at 8:54 AM, Stas Malyshev wr= ote: > >> Hi! >> >> >> On 10/16/11 5:54 PM, Sebastian Bergmann wrote: >> >>> =A0 Such a performance regression sounds like an appropriate "punishmen= t" to >>> =A0 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. >> >> > and there are cases when you can't avoid triggering errors (like trying t= o > delete delete a while =A0which can be deleted concurrently) so your only > option is to suppress them and handle the result based on the return valu= e > of the statement. > > -- > Ferenc Kov=E1cs > @Tyr43l - http://tyrael.hu >