Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:83289 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 62620 invoked from network); 20 Feb 2015 11:27:12 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Feb 2015 11:27:12 -0000 Authentication-Results: pb1.pair.com header.from=pthreads@pthreads.org; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=pthreads@pthreads.org; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain pthreads.org from 209.85.220.44 cause and error) X-PHP-List-Original-Sender: pthreads@pthreads.org X-Host-Fingerprint: 209.85.220.44 mail-pa0-f44.google.com Received: from [209.85.220.44] ([209.85.220.44:35998] helo=mail-pa0-f44.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 86/21-54878-E0A17E45 for ; Fri, 20 Feb 2015 06:27:11 -0500 Received: by pabkq14 with SMTP id kq14so7428757pab.3 for ; Fri, 20 Feb 2015 03:27:08 -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=G8buwFHmQO+P/p9rqaAV2HLyck7J8Yg+5Phl2DtMDVs=; b=JgptPhxcAwAH5qRDxCSkNhQ5YGWkfYsqngnbVSivEL9m+tWMRtJYI4rusD03ed8lwN /TA+rlL9sRADZiKiTybHm01uUukHOU3xlf7lNQCz8O2s/uFI+5bQ/vUZF+Cvod1ZllGN V7WB40aWxXEKV75+3DLCcVy+M8G048fx7V1oSZok9NAuGAlSoEo74D/UzGSNsiTpFyz6 +kggx3jp1R/ULYXx5UnOVwMFreBgDhm8IS0s5t+UEk/NGcG6oaGZ1pzgln3C6jyb07fy 6OylQcVV1dYCo1+DGtM1E6TNDL3o0GazhWTQJRPcNAVJbuV8kIbL4kL6ckO0tE/Swv49 r3MA== X-Gm-Message-State: ALoCoQkz9YmZj7QJ3xmMY70Eb8+IFy/hTOb+t0I6UamTWwXgY04yzgNlpErRm7ke09/m6BLoSJaq MIME-Version: 1.0 X-Received: by 10.66.217.198 with SMTP id pa6mr16039569pac.49.1424431628369; Fri, 20 Feb 2015 03:27:08 -0800 (PST) Received: by 10.70.49.100 with HTTP; Fri, 20 Feb 2015 03:27:08 -0800 (PST) X-Originating-IP: [86.159.154.191] In-Reply-To: References: <54E5F77D.9090406@fischer.name> <54E6F48A.9040906@fischer.name> Date: Fri, 20 Feb 2015 11:27:08 +0000 Message-ID: To: Leigh Cc: Markus Fischer , PHP internals Content-Type: multipart/alternative; boundary=e89a8f646b0b37552e050f8355f6 Subject: Re: [PHP-DEV] [VOTE] Expectations From: pthreads@pthreads.org (Joe Watkins) --e89a8f646b0b37552e050f8355f6 Content-Type: text/plain; charset=UTF-8 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. Cheers Joe On Fri, Feb 20, 2015 at 11:06 AM, Leigh wrote: > On 20 February 2015 at 08:47, Markus Fischer wrote: > > This sounds two-folded to me: "very cool" (albeit I can't see a use-case > > right now) on one hand and "utter magic" on the other. > > Inclined to agree. > > @Joe what use-case prompted this feature? > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > --e89a8f646b0b37552e050f8355f6--