Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:83294 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 81094 invoked from network); 20 Feb 2015 13:00:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Feb 2015 13:00:30 -0000 Authentication-Results: pb1.pair.com header.from=cryptocompress@googlemail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=cryptocompress@googlemail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 74.125.82.53 as permitted sender) X-PHP-List-Original-Sender: cryptocompress@googlemail.com X-Host-Fingerprint: 74.125.82.53 mail-wg0-f53.google.com Received: from [74.125.82.53] ([74.125.82.53:40783] helo=mail-wg0-f53.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 00/04-54878-DEF27E45 for ; Fri, 20 Feb 2015 08:00:29 -0500 Received: by mail-wg0-f53.google.com with SMTP id a1so12930891wgh.12 for ; Fri, 20 Feb 2015 05:00:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=iORoK3jv6SeCe4IYcPnAlkH3Qelchm45ylUEgDev8yM=; b=PfwFmtuIuX/ECIHig8cjqt/TCJrf00J+Z2cxSH7nXSg2AIHcP52PTiPQFftAcocwvE Ksw5m72he69ksV6DaBbC1CIGOWYbZ+K/67ezsYJzwVs/wXEzOqsjwTKENeBhia1V/wpm zADHRou+X6qpgREMLq3Z/fXbfvh3uiOvcQ+2E+twjOr7e1SeYH+qdqg4Due3aRLKr7Tr PA8rZW/VgNX1j6AASImCpRxihKyCesS1yGM92j50nhK/EwcoBUub4F4pek4iMXFnq3YP FJs9xFpZWALkTumTvBBi1Liu0iePyjf4j9LtcM5E8w6n6Gg+49AUyarvlrzFzTy0dzkq 5UTg== X-Received: by 10.194.3.40 with SMTP id 8mr18343846wjz.98.1424437226351; Fri, 20 Feb 2015 05:00:26 -0800 (PST) Received: from [192.168.1.115] (mnch-5d858289.pool.mediaWays.net. [93.133.130.137]) by mx.google.com with ESMTPSA id et4sm41985525wjd.15.2015.02.20.05.00.24 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 20 Feb 2015 05:00:25 -0800 (PST) Message-ID: <54E72FE7.9030803@googlemail.com> Date: Fri, 20 Feb 2015 14:00:23 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: PHP Developers Mailing List References: <54E5F77D.9090406@fischer.name> <54E6F48A.9040906@fischer.name> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [VOTE] Expectations From: cryptocompress@googlemail.com (Crypto Compress) Am 20.02.2015 um 12:27 schrieb Joe Watkins: > I work on a massive codebase, 3m loc, the ability to document that we throw > SomeAssertionException in *insert circumstance* is extremely appealing. It > would allow us to structure the documentation and the code in a way that > really makes sense especially for new developers. The alternatives are not > nice, in my opinion. It's not about runtime, and the ability to catch > specific exceptions by name, at all, > there shouldn't be any catch blocks for AssertionExceptions in deployed code Hello Joe, can you please explain a bit more how you would achieve this in 3m loc? Thanks!