Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:83375 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 68692 invoked from network); 21 Feb 2015 03:10:49 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Feb 2015 03:10:49 -0000 Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.182 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.216.182 mail-qc0-f182.google.com Received: from [209.85.216.182] ([209.85.216.182:43403] helo=mail-qc0-f182.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 11/04-45394-837F7E45 for ; Fri, 20 Feb 2015 22:10:49 -0500 Received: by qcxr5 with SMTP id r5so3882815qcx.10 for ; Fri, 20 Feb 2015 19:10:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=4t4D68tKPfKvorZaY/4q8Nw7V2ltzbzjFda8JKIK7DI=; b=p4GVa5YO09rYDRbMdIPTxpjUePwICN2+r+/5psCpEhr6lfp/f+4X1s3g9huv+KHaTV tlZm17C8nG3mPLFjph8XYAlCxANweN8cvaHh/ibGFlFEtMBEUuREwUEgd9pzuvGqSd9w f/YNMoLApJPBSHLTROLNNHTZN+Kmd5+O7SjRsCpzbPtrylg2Q9k5Af5aab4ezYdnILFL Rt/bvNRLJAyt2JzgKYRhgDDVKlyQs/bj/v8Kd5OKiPdsPJA0vUoIR//hUzzEJj+GTo4G up+V9F9J0sdSmOsMyV7usa43dMbabbSlSRuP/qn9RJyWrPSfS3+ihrxV4VBZNbv0Kcuy tFQQ== X-Received: by 10.229.204.135 with SMTP id fm7mr2026369qcb.2.1424488245838; Fri, 20 Feb 2015 19:10:45 -0800 (PST) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.229.198.8 with HTTP; Fri, 20 Feb 2015 19:10:05 -0800 (PST) In-Reply-To: <54E73E70.5020403@googlemail.com> References: <54E5F77D.9090406@fischer.name> <54E6F48A.9040906@fischer.name> <54E72FE7.9030803@googlemail.com> <54E7312D.9090404@googlemail.com> <54E73E70.5020403@googlemail.com> Date: Sat, 21 Feb 2015 12:10:05 +0900 X-Google-Sender-Auth: Qj0rBK-rl7hKFsLt4sCk30-BqZI Message-ID: To: Crypto Compress Cc: PHP Developers Mailing List Content-Type: multipart/alternative; boundary=001a11c1fd4ce14c4f050f9083c3 Subject: Re: [PHP-DEV] [VOTE] Expectations From: yohgaki@ohgaki.net (Yasuo Ohgaki) --001a11c1fd4ce14c4f050f9083c3 Content-Type: text/plain; charset=UTF-8 Hi Crypto, On Fri, Feb 20, 2015 at 11:02 PM, Crypto Compress < cryptocompress@googlemail.com> wrote: > AssertionExceptions are not intended to be caught, they are intended to be >> seen, in a specific environment. >> > > Joe, your argumentation is around how (not) to use exceptions. I can see > your point and it's valid. > My point is about not to implement exceptions at all. > > If exceptions are not intended to be caught, they don't need to be thrown > (even if the context is different). > If exceptions are not thrown and not caught, we can use "error" in dev and > some easing severity (warning, zero cost nothing) in prod. > > Freely adapted from Murphy: If assertion exception can be catched, it will > be even in production. Assertion is only for development and testing. We need errors or exceptions during development and testing, but not in production. Therefore, errors/exception should not be catched by code in general. Isn't assertion nature? I don't insist not to enable assertion in production environment. There might be software that needs extreme reliability and stability. For these softwares, it makes sense to enable assertions and catch errors/exceptions to do some cleanups. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --001a11c1fd4ce14c4f050f9083c3--