Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:73670 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 38344 invoked from network); 11 Apr 2014 17:52:38 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Apr 2014 17:52:38 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.67 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.67 smtp67.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.67] ([108.166.43.67:56548] helo=smtp67.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 74/30-37056-5EB28435 for ; Fri, 11 Apr 2014 13:52:37 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp1.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id BFF731497EE; Fri, 11 Apr 2014 13:52:34 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp1.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 5B2D01499DD; Fri, 11 Apr 2014 13:52:33 -0400 (EDT) Message-ID: <53482BE0.4060005@sugarcrm.com> Date: Fri, 11 Apr 2014 10:52:32 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Kris Craig , Julien Pauli CC: Rowan Collins , Marco Schuster , PHP Internals References: <53446FC5.7000001@gmail.com> <53459231.2080402@gmail.com> <5345AE83.1070506@sugarcrm.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [PHP.next] Error-handling using "Error Events" From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > behavior using try/catch blocks as Stas mentioned. However, people who > actually want this sort of behavior so they can route everything through > their own custom handlers (might be particularly useful for framework > developers) could switch it on. Something like ini_set( Why just not set error handler which would throw an exception? -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227