Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107660
MIME-Version: 1.0
References: <CAJkq-zzRaVYVvQ_pJbKu1vGNTQSTZ_pFF6yzhVrDF4N-M8NbiA@mail.gmail.com>
 <CALKiJKombs9+L9Sp0p4zDwbGb9+uYU7Rju2eAWXxktcagsz0iA@mail.gmail.com>
 <5f8115ce-0f89-c401-c8b8-9f865e76edd3@xs4all.nl> <11C11DE1-9D3B-4CB1-8226-AD48A0CE7A33@newclarity.net>
In-Reply-To: <11C11DE1-9D3B-4CB1-8226-AD48A0CE7A33@newclarity.net>
Date: Thu, 24 Oct 2019 17:31:45 +0100
Message-ID: <CALKiJKpjyyeph1aGys6tT_VfkvW1tOnYuP5ZJtKio5XqsaP8tA@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000062c9a10595aa9297"
Subject: Re: [PHP-DEV] Reclassifying some PHP functions warning as exceptions
From: rowan.collins@gmail.com (Rowan Tommins)

--00000000000062c9a10595aa9297
Content-Type: text/plain; charset="UTF-8"

On Thu, 24 Oct 2019 at 16:38, Mike Schinkel <mike@newclarity.net> wrote:

> > Here, try() would swallow only FileException, other exceptions are still
> > thrown. I'm not sure if this construct is worth introducing though, the
> > difference compared to a proper try / catch is much smaller.
>
> I would want it to capture every exception. Why not?



Because you might want to convert "FileLockedByAnotherProcessException" to
a locally-handled error, but allow "ServerIsOnFireException" to bubble up
to a higher-level exception handler.  That's why catch blocks basically
force you to specify class/interface names: you should catch only the
exceptions you actually know how to handle in that particular piece of code.

Regards,
-- 
Rowan Tommins
[IMSoP]

--00000000000062c9a10595aa9297--