Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:9249 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 15509 invoked by uid 1010); 16 Apr 2004 07:33:38 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 15483 invoked from network); 16 Apr 2004 07:33:37 -0000 Received: from unknown (HELO jdi.jdimedia.nl) (212.204.192.51) by pb1.pair.com with SMTP; 16 Apr 2004 07:33:37 -0000 Received: from localhost (localhost [127.0.0.1]) by jdi.jdimedia.nl (8.12.10/8.12.10) with ESMTP id i3G7XHst026782; Fri, 16 Apr 2004 09:33:18 +0200 Date: Fri, 16 Apr 2004 09:32:48 +0200 (CEST) X-X-Sender: derick@localhost To: John Coggeshall cc: Nuno Lopes , PHP Internals In-Reply-To: <1082070778.17792.18.camel@coogle.localdomain> Message-ID: References: <00cc01c422e1$46a4adc0$0100a8c0@pc07653> <1082070778.17792.18.camel@coogle.localdomain> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [PHP-DEV] Exceptions and a real example: Tidy From: derick@php.net (Derick Rethans) On Thu, 15 Apr 2004, John Coggeshall wrote: > - All errors were re-evaluated, and those (such as a bogus config > option) were demoted to E_NOTICE or promoted to E_ERROR as > necessary > - Those errors which are truly E_WARNING will behave as such when > called from a procedural context. If called from an object oriented > context, they will be represented as exceptions. Do you mean E_ERRORS become exceptions or also E_WARNINGS? E_WARNINGS should never become exceptions as it's a non-fatal error. Derick