Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107503
Return-Path: <sebastian@php.net>
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 86843 invoked from network); 11 Oct 2019 15:05:03 -0000
Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12)
  by pb1.pair.com with SMTP; 11 Oct 2019 15:05:03 -0000
Received: from php-smtp3.php.net (localhost [127.0.0.1])
	by php-smtp3.php.net (Postfix) with ESMTP id 4CBD52D203B
	for <internals@lists.php.net>; Fri, 11 Oct 2019 05:48:02 -0700 (PDT)
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp3.php.net
X-Spam-Level: 
X-Spam-Status: No, score=-0.5 required=5.0 tests=BAYES_05,SPF_HELO_NONE
	autolearn=no autolearn_force=no version=3.4.2
X-Spam-ASN: AS20694 188.94.24.0/21
X-Spam-Virus: No
Received: from scarlet.netpirates.net (scarlet.netpirates.net [188.94.27.5])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by php-smtp3.php.net (Postfix) with ESMTPS
	for <internals@lists.php.net>; Fri, 11 Oct 2019 05:48:01 -0700 (PDT)
Received: from p5de2c1dc.dip0.t-ipconnect.de ([93.226.193.220] helo=[192.168.178.42])
	by scarlet.netpirates.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256)
	(Exim 4.92.3)
	(envelope-from <sebastian@php.net>)
	id 1iIuKv-0006Wh-6V
	for internals@lists.php.net; Fri, 11 Oct 2019 14:48:01 +0200
To: internals@lists.php.net
References: <CAF+90c9EQ+UGe-y+V_n1QrYkXtPh1uWKXXWEJQUe0xP-MjV7_w@mail.gmail.com>
Reply-To: internals@lists.php.net
Message-ID: <62b8c362-47bc-de8f-a756-1ab341dc884b@php.net>
Date: Fri, 11 Oct 2019 14:47:58 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.1.1
MIME-Version: 1.0
In-Reply-To: <CAF+90c9EQ+UGe-y+V_n1QrYkXtPh1uWKXXWEJQUe0xP-MjV7_w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Envelope-From: <sebastian@php.net>
Subject: Re: [PHP-DEV] exit() via exception
From: sebastian@php.net (Sebastian Bergmann)

Am 11.10.2019 um 13:05 schrieb Nikita Popov:
> Depending on the implementation, we could also allow code to actually catch
> this exception, which may be useful for testing scenarios, as well as
> long-running daemons.

This sounds interesting :)

> Anyone have thoughts on this matter?

I think \Throwable should always include all objects that can be used with 
throw and catch.