Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:92977
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain telia.com from 81.236.60.155 cause and error)
To: Rowan Collins <rowan.collins@gmail.com>
References: <CADFyporyFgnMgetcEj8FZUFs1Lbc_VidBsxg5jBE7J4_OFzKTQ@mail.gmail.com>
 <CA+kxMuTFfqHZa4sXNv=Cfcm8w6eHdkKSGYiPdUiTJ1DGd6_VQQ@mail.gmail.com>
 <CADyq6sJP_BYEmmTWzJ4OvhcM9uto2EY+vefZTKovAaKBA8hs7w@mail.gmail.com>
 <alpine.DEB.2.20.1604181614100.3391@whisky.home.derickrethans.nl>
 <BY2PR02MB298461D66EA1A39720B93CBAC6C0@BY2PR02MB298.namprd02.prod.outlook.com>
 <CACwt+Jfoat-3C1QBPEgc-mR5-jQnLBQxcs-6=LJmOMfuGyy3iA@mail.gmail.com>
 <CA+kxMuTVUKjqbBTLj=4sxWSGzoQwrPwZgJdz+cu5=c9nPBtgsA@mail.gmail.com>
 <CACwt+JcxauE8fgwPSeh6r4jK9-yqwowbvObx2JUvveY_0SZGew@mail.gmail.com>
 <571DE825.6050807@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Message-ID: <5724864F.1000301@telia.com>
Date: Sat, 30 Apr 2016 12:17:52 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <571DE825.6050807@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [VOTE] Catching Multiple Exception Types
From: bjorn.x.larsson@telia.com (=?UTF-8?Q?Bj=c3=b6rn_Larsson?=)

Den 2016-04-25 kl. 11:49, skrev Rowan Collins:
> Patrick ALLAERT wrote on 24/04/2016 14:18:
>> There is just nothing more repeatable or common cases than "resource not
>> found", "method not allowed", "access denied",... They are all non
>> exceptional cases better handled without exceptions and with clean APIs
>> reflecting the business logic of the application.
>
> I think part of the problem may be that non-trivial examples require 
> rather a lot of context. An example that comes to my mind is if an 
> application is combining a bunch of different libraries, and calling 
> them all in sequence:
>
> try
> {
> $fooService->doStuff($data);
> $barService->doMoreStuff($data);
> $bazService->doDifferentStuff($data);
> }
> catch ( FooException | BarException | BazException $e )
> {
> // We don't care which library threw the exception, the action is 
> always the same
> throw new AppException($e); // Hide which libraries we're using to 
> implement the function
> }
>
> Regards,

Good example, thats how I would use multi-catch.

Regards //Björn Larsson