Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:82808 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 61654 invoked from network); 16 Feb 2015 10:32:33 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Feb 2015 10:32:33 -0000 Authentication-Results: pb1.pair.com smtp.mail=pthreads@pthreads.org; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=pthreads@pthreads.org; sender-id=unknown Received-SPF: error (pb1.pair.com: domain pthreads.org from 209.85.192.171 cause and error) X-PHP-List-Original-Sender: pthreads@pthreads.org X-Host-Fingerprint: 209.85.192.171 mail-pd0-f171.google.com Received: from [209.85.192.171] ([209.85.192.171:36977] helo=mail-pd0-f171.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 36/4D-05176-047C1E45 for ; Mon, 16 Feb 2015 05:32:33 -0500 Received: by pdbfl12 with SMTP id fl12so34403528pdb.4 for ; Mon, 16 Feb 2015 02:32:30 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Rar8yWSwdjcw6g5u+l2OUGTMr1gl/xD45vMzGvIrxpw=; b=BPbjrYuOzLXMC9dvCxKiXC7yBklDDbN3wVhYn1f7cFbjOqf2q2n+7G8E/mn+HFawdO zeFjgolvmNOHb0gSKm0PjMi7aNPGnTE/oRjFX2SNqZEShuSugJNxtdUFsr9y+dwe96ci 110+rLS+6tVQD/U0oMGUo1SkKAVPMsNWvC66zIvsL0L6b+SH2fgCn2LfhKJDMhDNtUef ce5Ig9yTisryA8Bx1SCHaCMFjCrHdHm+cGloI9WOct01FIzfoE44+yA6/qkCLOqlLJqT X3GDMTjaBbk+jeFI+tno1L3dwakRwcWL/j4y21SVx1C9o5w+okzVEZZIwezUK56wW7aF T5CQ== X-Gm-Message-State: ALoCoQlLBGBMV4vF6QlDkKUz1hXVvCT++0TAdGslnIgzfd5CEb7AfiGYOlo8ly+QzuGfks+nP2Q4 MIME-Version: 1.0 X-Received: by 10.66.185.230 with SMTP id ff6mr39023796pac.102.1424082750154; Mon, 16 Feb 2015 02:32:30 -0800 (PST) Received: by 10.70.49.100 with HTTP; Mon, 16 Feb 2015 02:32:30 -0800 (PST) X-Originating-IP: [86.190.233.59] In-Reply-To: <54E1C24B.6010806@googlemail.com> References: <54E1C24B.6010806@googlemail.com> Date: Mon, 16 Feb 2015 10:32:30 +0000 Message-ID: To: Crypto Compress Cc: PHP Developers Mailing List Content-Type: multipart/alternative; boundary=001a1134259a743c8a050f321a7a Subject: Re: [PHP-DEV] RFC: Expectations From: pthreads@pthreads.org (Joe Watkins) --001a1134259a743c8a050f321a7a Content-Type: text/plain; charset=UTF-8 > is there any penalty of catch-AssertionException-blocks? Are those eliminated in production code? Assertions should never be enabled in production code, the ability to catch (and enable by configuration) the exception serves the developer of the code during development only. The example code is bad, I'll clear this up. Cheers Joe On Mon, Feb 16, 2015 at 10:11 AM, Crypto Compress < cryptocompress@googlemail.com> wrote: > Hi Joe, > > is there any penalty of catch-AssertionException-blocks? Are those > eliminated in production code? > > Thanks > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > --001a1134259a743c8a050f321a7a--