Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:86245 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 12528 invoked from network); 16 May 2015 14:40:39 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 May 2015 14:40:39 -0000 Authentication-Results: pb1.pair.com header.from=morrison.levi@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=morrison.levi@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.179 as permitted sender) X-PHP-List-Original-Sender: morrison.levi@gmail.com X-Host-Fingerprint: 209.85.213.179 mail-ig0-f179.google.com Received: from [209.85.213.179] ([209.85.213.179:38138] helo=mail-ig0-f179.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 54/42-14891-6E657555 for ; Sat, 16 May 2015 10:40:38 -0400 Received: by igcau1 with SMTP id au1so19029393igc.1 for ; Sat, 16 May 2015 07:40:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=CgNl92b2CH74FA/D4nxBQ83PdUjev6EeNUEl82f5aQ8=; b=UoWkVk9Ku3JR7+u5YYx7df0bmX2eKpGIKdqTGz7CyWzg2e2Ushu+dHSdKZbj4LYp08 q8z4l5tj1eXSUtYf5mtDsG38hBpe/AfuGqhliAUntv82d6uR2xx/1pwsHXXObF/r24qS RHquEfxQZcWVUSfc4BCRVWBJ/qnMF/S7YP7zI+l61geOYe0pxYe1j+Ig5wa8PXsOsZuP auS00FzScKQhZ/JQjSpmaYxTKqWa5fZJ0s3XnOE1z7top0Poy4szvZoxYq8xA+u1XiH2 DyLNfUVcH/tVwKPViMXSGOcxGr72rF5+8sb+T//xlrRrWXZ3r9RRPDyPEFO+YQf9Oy9L rL5w== MIME-Version: 1.0 X-Received: by 10.50.43.227 with SMTP id z3mr4588243igl.12.1431787235202; Sat, 16 May 2015 07:40:35 -0700 (PDT) Sender: morrison.levi@gmail.com Received: by 10.79.98.67 with HTTP; Sat, 16 May 2015 07:40:35 -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> <554D8F4D.9020903@gmail.com> <554D90CC.3040607@php.net> <5552E3EB.5010800@gmail.com> <5552E494.5070401@php.net> <5552FF58.8070807@php.net> Date: Sat, 16 May 2015 08:40:35 -0600 X-Google-Sender-Auth: PKPaqFdVeVeawV6wLso7BJQJV8I Message-ID: To: =?UTF-8?Q?Pavel_Kou=C5=99il?= Cc: Sebastian Bergmann , PHP internals Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] [VOTE] Exceptions in the engine From: levim@php.net (Levi Morrison) I want to talk about the BC impact of what has been discussed. Currently the meaning of this code is to catch all possible exceptions, because all exceptions *must* extend `\Exception`: } catch (Exception $e) { By making some other root exception you just broke all the code that is *appropriately* using the catch-all variant. So either way it is a BC break. So let's consider other impact to help decide: If we introduce a new root exception then the people "punished" are the ones currently using Exception correctly. Whereas if engine exceptions just extend Exception then the people "punished" are the ones using it inappropriately. Please, revert all of these changes with Error and some new root exception and *do the right thing* based on logical arguments. It makes no sense to punish the people using code correctly to avoid punishing people misusing a feature, especially when it is a BC break either way.