Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:9298 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 636 invoked by uid 1010); 16 Apr 2004 22:20:35 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 578 invoked from network); 16 Apr 2004 22:20:34 -0000 Received: from unknown (HELO mail.mbobo.org) (213.133.123.182) by pb1.pair.com with SMTP; 16 Apr 2004 22:20:34 -0000 Received: from localhost (localhost [127.0.0.1]) by mail.mbobo.org (Postfix) with ESMTP id 5DF68576C9D; Sat, 17 Apr 2004 00:20:34 +0200 (CEST) Received: from mail.mbobo.org ([127.0.0.1]) by localhost (debian [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 24557-06; Sat, 17 Apr 2004 00:20:33 +0200 (CEST) Received: from [10.200.1.52] (adsl-68-120-96-254.dsl.sntc01.pacbell.net [68.120.96.254]) by mail.mbobo.org (Postfix) with ESMTP id 3D25B576C16; Sat, 17 Apr 2004 00:20:32 +0200 (CEST) In-Reply-To: References: <00cc01c422e1$46a4adc0$0100a8c0@pc07653> <1082070778.17792.18.camel@coogle.localdomain> <1082130174.31819.51.camel@coogle.localdomain> <4080035B.1090404@cschneid.com> <1082132272.31824.56.camel@coogle.localdomain> <40800930.2070302@cschneid.com> Mime-Version: 1.0 (Apple Message framework v613) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-ID: <45808D19-8FF4-11D8-9B29-000A95E073A0@php.net> Content-Transfer-Encoding: 7bit Cc: john@coggeshall.org, Christian Schneider , PHP Internals Date: Fri, 16 Apr 2004 15:20:30 -0700 To: Derick Rethans X-Mailer: Apple Mail (2.613) X-Virus-Scanned: by amavisd-new-20030616-p5 (Debian) at mbobo.org Subject: Re: [PHP-DEV] Exceptions and a real example: Tidy From: sterling@php.net (Sterling Hughes) Tidy's current error handling scheme is totally messed up - every single thing in the extension should be an E_WARNING by PHP standards. Its RC2, and this stuff has worked for a long time, breaking it now is counterproductive and annoying. John, if you insist on messing up the error handling in the tidy extension, which is a serious thing, why not move it to pecl where you have full control over such things without bothering the rest of the release..? -Sterling On Apr 16, 2004, at 9:44 AM, Derick Rethans wrote: > On Fri, 16 Apr 2004, Christian Schneider wrote: > >> John Coggeshall wrote: >>> the best compromise I can reach without discarding exceptions >>> entirely, >>> which I believe is even more wrong for OO code. >> >> I disagree. I lost track over the last couple of days, what is >> everyone >> else's view on this? > > I disgree with this behavior too. E_WARNINGs were never supposed to > abort a script, that's what we have E_ERRORs for. (Making E_ERROR an > exception in an OO context is fine, as when it's unhandled it should > abort the script, just like in PHP 4 and all other non-oo extensions). > > Derick > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php >