Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:55832 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 80625 invoked from network); 17 Oct 2011 07:49:48 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Oct 2011 07:49:48 -0000 Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.42 as permitted sender) X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.213.42 mail-yw0-f42.google.com Received: from [209.85.213.42] ([209.85.213.42:56689] helo=mail-yw0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 2E/E2-50906-A1EDB9E4 for ; Mon, 17 Oct 2011 03:49:47 -0400 Received: by ywt32 with SMTP id 32so667628ywt.29 for ; Mon, 17 Oct 2011 00:49:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=MS9mtBm6nlHsF9QrluKlbMoIou3uDNBxEU7Cf/iJC7g=; b=c1s1alEi0GubGA/9l2L+zv3SufdKLtqs6hGeV4TVeI30TY90vOdMxeijKPPr69wcYn HGCbh2Ivrc53R8dz0SUQ/DZZvgapHoRKEbuTCDDszUL9MUKdPLSvQslluomHM5ToOhRG dSav0bfzPWU8YeAf2w9plrCY/NyKD379++0ko= MIME-Version: 1.0 Received: by 10.236.138.161 with SMTP id a21mr24230024yhj.87.1318837784285; Mon, 17 Oct 2011 00:49:44 -0700 (PDT) Received: by 10.147.125.13 with HTTP; Mon, 17 Oct 2011 00:49:44 -0700 (PDT) In-Reply-To: <4E9BD142.8060806@sugarcrm.com> References: <4E95AB4E.6040302@sugarcrm.com> <4E9B7CDF.4090106@php.net> <4E9BD142.8060806@sugarcrm.com> Date: Mon, 17 Oct 2011 09:49:44 +0200 Message-ID: To: Stas Malyshev Cc: Sebastian Bergmann , "internals@lists.php.net" Content-Type: multipart/alternative; boundary=20cf303b40cfa6135004af79d998 Subject: Re: [PHP-DEV] #60038 SIGALRM cause segfault in php_error_cb From: tyra3l@gmail.com (Ferenc Kovacs) --20cf303b40cfa6135004af79d998 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Mon, Oct 17, 2011 at 8:54 AM, Stas Malyshev wrot= e: > 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. > > and there are cases when you can't avoid triggering errors (like trying to delete delete a while which can be deleted concurrently) so your only option is to suppress them and handle the result based on the return value of the statement. --=20 Ferenc Kov=C3=A1cs @Tyr43l - http://tyrael.hu --20cf303b40cfa6135004af79d998--