Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:86103 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 14455 invoked from network); 1 May 2015 05:08:56 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 May 2015 05:08:56 -0000 Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.172 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.212.172 mail-wi0-f172.google.com Received: from [209.85.212.172] ([209.85.212.172:36377] helo=mail-wi0-f172.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 7A/30-06510-46A03455 for ; Fri, 01 May 2015 01:08:53 -0400 Received: by wizk4 with SMTP id k4so42833305wiz.1 for ; Thu, 30 Apr 2015 22:08:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=uMqTSYTU3XTrkbk7349ZQKIPNInNeboWlHXmCoiLDqQ=; b=nvwhqleJT4DrsLIOgGBLMPxishF/D8padDzld8WTgZ63ZDUP+PppH9umoWMVioTQ40 zoYYVnBLi/s/TqJ+OWqZ5E5gIly6uLXTXi7bUl1W3fqHWSQG3eu0CgEeEguG+iXmBp79 FbRucOQVjCHD3ugrTLWcZmbZlRbImUKtqNTIPcqXhGva79ty+vxbmHBqfcckSWb93xD7 db0uiekXyjfZ5LIlrODJv1ETbSJ+mu9pYfQgrIizjWyLHhYLEMZ3mybKO+15sm6CMtJu wJo6m1tTxD3KckP8TIMzB8H1XcMrZkQEkLBAa/wHJwFEMvMy4UJc4c98Ftjws1rUWY/q g7TQ== MIME-Version: 1.0 X-Received: by 10.180.105.74 with SMTP id gk10mr11494761wib.29.1430456929728; Thu, 30 Apr 2015 22:08:49 -0700 (PDT) Received: by 10.194.5.129 with HTTP; Thu, 30 Apr 2015 22:08:49 -0700 (PDT) Received: by 10.194.5.129 with HTTP; Thu, 30 Apr 2015 22:08:49 -0700 (PDT) In-Reply-To: References: <54F07FC7.8050901@php.net> <54F0839C.3010700@seld.be> <55052FAD.6090608@php.net> <5505346D.7020700@php.net> <550DA4EE.2030903@php.net> <55410973.4010300@php.net> <55417C64.7000707@gmail.com> <5541B4D6.9060503@php.net> <55425D7E.6010803@gmail.com> Date: Fri, 1 May 2015 12:08:49 +0700 Message-ID: To: Marcio Almada Cc: PHP internals , Sebastian Bergmann , Julien Pauli , Stanislav Malyshev Content-Type: multipart/alternative; boundary=f46d04426ca629bd410514fe35a0 Subject: Re: [PHP-DEV] [VOTE] Exceptions in the engine From: pierre.php@gmail.com (Pierre Joye) --f46d04426ca629bd410514fe35a0 Content-Type: text/plain; charset=UTF-8 On May 1, 2015 1:24 AM, "Marcio Almada" wrote: > > Hi Stas, > > 2015-04-30 13:51 GMT-03:00 Stanislav Malyshev : > > > Hi! > > > > > We could make an exception (sic !) and add the Throwable interface to > > PHP7, > > > even after feature freeze, because it is an easy pick and having a clear > > > Exception model for 7.0 is to my opinion very important. > > > > I'm OK with it but I fear this is opening a can of worms, since people > > will start arguing "well, we've added Throwable so let's also add this > > other thing which is absolutely 100% necessary" and here goes our > > feature freeze. Maybe I'm just too cynical :) Anyway, I don't have any > > objection on substance to it. So if everybody is ok with it, I'm fine > > with it too. > > -- > > Stas Malyshev > > smalyshev@gmail.com > > > > -- > > PHP Internals - PHP Runtime Development Mailing List > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > I agree with you, but the process isn't perfect - and will never be. Taking > RFC guidelines without exceptions is damaging to quality in this case. If > someone else decide to open a new RFC after the deadline without the same > level of consensus we have here, the RFC will be put down, hopefully. Let do a rfc to accept to post pone features freeze with a list or a single RFC. I totally agree that this exact problem has to be fixed for 7.0, same for error cb. I don't see anything else being so critical that it has to be in 7.0. My point for error cb is that it requires quite some changes in extensions and if we like to avoid a 7.0 to 7.1 migration pain, it has to be in 7.0. > Thanks. --f46d04426ca629bd410514fe35a0--