Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:83297 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 88109 invoked from network); 20 Feb 2015 13:32:08 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Feb 2015 13:32:08 -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.220.47 cause and error) X-PHP-List-Original-Sender: pthreads@pthreads.org X-Host-Fingerprint: 209.85.220.47 mail-pa0-f47.google.com Received: from [209.85.220.47] ([209.85.220.47:40534] helo=mail-pa0-f47.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 01/25-54878-25737E45 for ; Fri, 20 Feb 2015 08:32:06 -0500 Received: by paceu11 with SMTP id eu11so8069684pac.7 for ; Fri, 20 Feb 2015 05:31:59 -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=Zt8SqyUVwAGE9rfVfAyAmJNOLs7ejahgFx+c6ow0qUI=; b=aCFzkXFgNYSOozTpKVgnfXP6JGk/OPL5NSd1Tcya1/LOPx+OT8V4k4+N2RIkdKamFC Ute/Sw2fboeU5tLRmgCu6BFMbuVyKaDrfGlOurkxl+QckcIWLi9Rq7Wduay0GWieZWlO yG57+pSy0LCc6z9j0Az0He0vhiMmbVVjSL5pwJLjTxdrAW5VciL9TUS7uPg3PLJE0A76 eUKq0fVrWbWuvJmiHLjiY9vT9LXrj1OtSVgp5hQ3bEn65dHYgOF9nVF5eO1s6aVAwwDh 5IQ5VPdRnT3Lb5CXyM9DZewNTiRwUmvl+zBbKDG6oGTlsv29sw4TBaqrX+Pe69ZPry8i rq/Q== X-Gm-Message-State: ALoCoQk1aWNJUZtpgUJvxrbFlTTcFjhsOr0GdxmkXGosbJvgnXndLGmOXS1TNrtKUyJbcp18pUe4 MIME-Version: 1.0 X-Received: by 10.70.46.65 with SMTP id t1mr16682918pdm.128.1424439119433; Fri, 20 Feb 2015 05:31:59 -0800 (PST) Received: by 10.70.49.100 with HTTP; Fri, 20 Feb 2015 05:31:59 -0800 (PST) X-Originating-IP: [86.159.154.191] In-Reply-To: <54E7312D.9090404@googlemail.com> References: <54E5F77D.9090406@fischer.name> <54E6F48A.9040906@fischer.name> <54E72FE7.9030803@googlemail.com> <54E7312D.9090404@googlemail.com> Date: Fri, 20 Feb 2015 13:31:59 +0000 Message-ID: To: Crypto Compress Cc: PHP Developers Mailing List Content-Type: multipart/alternative; boundary=047d7bd8ffa8b7e8d0050f85137e Subject: Re: [PHP-DEV] [VOTE] Expectations From: pthreads@pthreads.org (Joe Watkins) --047d7bd8ffa8b7e8d0050f85137e Content-Type: text/plain; charset=UTF-8 > can you please explain a bit more how you would achieve this in 3m loc? AssertionExceptions are not intended to be caught, they are intended to be seen, in a specific environment. It doesn't really make sense to commit/deploy code that catches AssertionExceptions knowing that the code is actually dead in production. So you just don't deploy catch blocks for AssertionException, you might write one while debugging locally, but deploying them doesn't make sense. Cheers Joe On Fri, Feb 20, 2015 at 1:05 PM, Crypto Compress < cryptocompress@googlemail.com> wrote: > > The alternatives are not nice, in my opinion. >> > > What are this alternatives? What are the drawbacks of "warning" in > production code? > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > --047d7bd8ffa8b7e8d0050f85137e--