Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91584
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain webstart.fr from 209.85.161.169 cause and error)
MIME-Version: 1.0
Sender: pierrick@webstart.fr
In-Reply-To: <alpine.DEB.2.20.1603091149080.3594@whisky.home.derickrethans.nl>
References: <CAOfKkdQ_9jQw5p6hcCx=YL-RoZWf4st8Q=C9hknHUzR97P0fhA@mail.gmail.com>
	<alpine.DEB.2.20.1603091149080.3594@whisky.home.derickrethans.nl>
Date: Wed, 9 Mar 2016 08:03:48 -0500
Message-ID: <CAOfKkdRWv8Z4z1bWHFHnX_EK=wQ-vxryy24731qnFhu7MHxRkw@mail.gmail.com>
To: Derick Rethans <derick@php.net>
Cc: PHP internals <internals@lists.php.net>, =?UTF-8?B?QnJvbmlzxYJhdyBCaWHFgmVr?= <after89@gmail.com>
Content-Type: multipart/alternative; boundary=001a1146c95a27e516052d9d5477
Subject: Re: [PHP-DEV] [RFC Discussion] Catching multiple exception types
From: pierrick@adoy.net (Pierrick Charron)

--001a1146c95a27e516052d9d5477
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Derick

I agree that most of the time the best solution is to implement a clean
exception hierarchy but as stated in the RFC :

"A solution to fix this problem on the user level would be to implement a
common interface for ExceptionType1 and ExceptionType2 and catch it.
However, this is only possible when you control the exception hierarchy in
your own code, but not possible when you don't control the code."

On 9 March 2016 at 06:52, Derick Rethans <derick@php.net> wrote:

> Hi!
>
> On Tue, 8 Mar 2016, Pierrick Charron wrote:
>
> > Bronis=C5=82aw Bia=C5=82ek and I would like to start a discussion about=
 allowing
> > multiple exception types to be caught in a single catch statement.
> >
> > https://wiki.php.net/rfc/multiple-catch
>
> Would it not be better, to have your Exceptions extend a common base
> class in this case? Or perhaps, which I think is even better, to have
> your Exception classes implement a common interface that you can catch
> against. That I believe should already work.
>
> What you are asking PHP users to do with a multiple catch like this, is
> to test in each catch's statement block to test for each class again.
> Neither the inheritence or implements options from the previous
> paragraph have that issue.
>
> cheers,
> Derick

--001a1146c95a27e516052d9d5477--