Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:86539 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 71682 invoked from network); 10 Jun 2015 07:37:05 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Jun 2015 07:37:05 -0000 Authentication-Results: pb1.pair.com header.from=dmitry@zend.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=dmitry@zend.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.216.44 as permitted sender) X-PHP-List-Original-Sender: dmitry@zend.com X-Host-Fingerprint: 209.85.216.44 mail-vn0-f44.google.com Received: from [209.85.216.44] ([209.85.216.44:42908] helo=mail-vn0-f44.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 5C/91-61871-F19E7755 for ; Wed, 10 Jun 2015 03:37:05 -0400 Received: by vnbg129 with SMTP id g129so6594699vnb.9 for ; Wed, 10 Jun 2015 00:37:00 -0700 (PDT) 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=arEWrTGz+dscMf54bg+Or7cOgtAtw0T7SXwTILvSUqs=; b=AX2lc9WrGaWtu0AyeMsyvWs2I9L50b/zGbWrkrF4saJNYW/6ZdoAJyxt7Odwakqksa VaKKny5O8BQbO4voavPjWBvUFseIcCkaWXWUkdrt+FtdXhwIPWhmnLX6pwOA0k7Z0szm Jw+fJcwrQLgLyupHAIa7ZOcWKKNwDX9LdO7B2Ptzh5o47tNNsQEEnTRhllnNxaeaH321 O0CpFmzTke3k2DjgRRhHrLYLJhSAXzUA7kNuYpLflJdAOrrf+R3xXuSomMJSm6YiAwNp PmajPFvFVaWAqQB+69fFBmVeME/cH1Ior0+Av3bdOfJiv5PS5cKwjI8AG6jZeIOEy4ij H+0g== X-Gm-Message-State: ALoCoQkcszYRex6rISfwZWnOCDq4vWpgr1WtQCHxurpd5wibCD4I2xzVbfDsOx8LPPeY03Hr/rtzj3LcV16FdEKoiAf5A3z9T+5BAc5TGIQLEgPx2zrdEi6famY9sfGv8jxw7K54Si6CHbINR0aR+5IdY06nSlG+X7z/k29JzcL0MNcHo38WlOs= MIME-Version: 1.0 X-Received: by 10.52.185.69 with SMTP id fa5mr3919452vdc.62.1433921820154; Wed, 10 Jun 2015 00:37:00 -0700 (PDT) Received: by 10.31.10.201 with HTTP; Wed, 10 Jun 2015 00:37:00 -0700 (PDT) In-Reply-To: References: <971AB39D-1E20-43E8-9CF1-A7F67E3C14C3@icicle.io> <556363D3.1040902@gmail.com> <12C3389A-AFF5-42CA-8190-E4227309DAED@icicle.io> Date: Wed, 10 Jun 2015 10:37:00 +0300 Message-ID: To: Levi Morrison , Aaron Piotrowski , Nikita Popov Cc: internals , Anatol Belski , Kalle Sommer Nielsen Content-Type: multipart/alternative; boundary=bcaec5486476b9fa0d051824f0a4 Subject: Re: [PHP-DEV] [RFC] Throwable Interface From: dmitry@zend.com (Dmitry Stogov) --bcaec5486476b9fa0d051824f0a4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Tue, Jun 9, 2015 at 9:13 PM, Levi Morrison wrote: > On Tue, Jun 9, 2015 at 11:40 AM, Aaron Piotrowski wrote= : > > Does anyone have any questions, comments, or concerns about the > Throwable Interface RFC? > > > > http://wiki.php.net/rfc/throwable-interface > > > > The proposed exception hierarchy: > > > > interface Throwable > > =E2=8A=A2 Exception implements Throwable > > =E2=88=9F Error implements Throwable (replaces EngineException) > > =E2=8A=A2 TypeError (replaces TypeException) > > =E2=88=9F ParseError (replaces ParseException) > > > > I=E2=80=99d like to complete a vote before too many alpha releases are = made. > > > > I=E2=80=99ll be happy to resolve the merge conflicts in the PR if the v= ote > passes. > > My only objections have already been raised, but I'll reiterate them > briefly: > > 1. Having both Error and Exception makes little sense, especially > since we have historically used error to refer to an error that wasn't > an exception (something that triggered the error handler). > 2. The name "Error" is going to have a fairly high collision rate > with user code. > I also like EngineException more than Error. > 3. I think they should all use Exception as the root instead having > a new root with multiple children (and yes, I am aware of the impact > of this, and it has already been discussed on this list). > This done on purpose. To prevent catching of new exceptions by old PHP code= . If we won't accept this now (before 7.0 release), it would make more troubles in the future. I didn't make deep code review, and don't know all possible consequences. Anyway, I would make a chance to accept this now or never. RM, your thoughts? In case we decide to vote for this RFC, I'll make code review and will help with possible problems. Thanks. Dmitry. > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > --bcaec5486476b9fa0d051824f0a4--