Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:73680 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 52041 invoked from network); 13 Apr 2014 12:01:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Apr 2014 12:01:25 -0000 Authentication-Results: pb1.pair.com header.from=kris.craig@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=kris.craig@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.175 as permitted sender) X-PHP-List-Original-Sender: kris.craig@gmail.com X-Host-Fingerprint: 209.85.214.175 mail-ob0-f175.google.com Received: from [209.85.214.175] ([209.85.214.175:56091] helo=mail-ob0-f175.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 9C/10-49914-49C7A435 for ; Sun, 13 Apr 2014 08:01:25 -0400 Received: by mail-ob0-f175.google.com with SMTP id vb8so1529594obc.6 for ; Sun, 13 Apr 2014 05:01:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=fMKOU6DktCxoB4tHBjgJ7PUmp1E9JEc6mbfTx3lw02o=; b=nRnz1oFyvGuHA8L3xa6FHm3/tRR60LVCjAM2aXhKoTadCCqlPrlQbsc1K+l5n/MPJF mdAgDux+/63K+ZaFwl4SgX431yQ4bu34SjpqzEZNIrNGClNUqqqz/DLjlpeR9hQ+8EtV VoQQhYkRBtc0CgurIju7rKQoLxbcp4HjaJFk3O8LJHIMyHWFN/OsPEMTHGj/dAdqawKE gfaNpiN7nJpgxM4WrtamRhkp+pJBxmbsDuf3VCUpO2ctcKNiqRoMFvEk8RkLd5dhifpE peNKqrbLaDmrY72mUwoMwhAlyECtn3oQ4TUJ1GZwqWm2vpWjbP9i7rqz5wBz/In/QXXL QG+A== MIME-Version: 1.0 X-Received: by 10.182.28.98 with SMTP id a2mr292931obh.63.1397390481959; Sun, 13 Apr 2014 05:01:21 -0700 (PDT) Received: by 10.182.231.230 with HTTP; Sun, 13 Apr 2014 05:01:21 -0700 (PDT) In-Reply-To: <534A38DB.10100@sugarcrm.com> References: <53446FC5.7000001@gmail.com> <53459231.2080402@gmail.com> <5345AE83.1070506@sugarcrm.com> <53482BE0.4060005@sugarcrm.com> <534A38DB.10100@sugarcrm.com> Date: Sun, 13 Apr 2014 05:01:21 -0700 Message-ID: To: Stas Malyshev Cc: Marco Schuster , Julien Pauli , Rowan Collins , PHP Internals Content-Type: multipart/alternative; boundary=089e0158adfe4a333b04f6eb5304 Subject: Re: [PHP-DEV] [PHP.next] Error-handling using "Error Events" From: kris.craig@gmail.com (Kris Craig) --089e0158adfe4a333b04f6eb5304 Content-Type: text/plain; charset=ISO-8859-1 > > unless you change every piece of code to use > individual exception class - which is a huge chunk of work and goes way > beyond ini setting That's just it. I know a lot of PHP developers who believe that's the ideal way to go about it; that everything should be funneled through a massive custom exception class(es). Those people would build their code around that from the ground-up, anyway. As I mentioned earlier, a likely example of this would be someone developing a new framework and they want to control all error handling through there. I'm not sure if I would take that approach on a given project, myself, but I know a lot of people who would and I can see something like this being very useful to them for their purposes. --Kris --089e0158adfe4a333b04f6eb5304--