Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:9299
Return-Path: <derick@php.net>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 8980 invoked by uid 1010); 16 Apr 2004 22:23:49 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 8888 invoked from network); 16 Apr 2004 22:23:49 -0000
Received: from unknown (HELO jdi.jdimedia.nl) (212.204.192.51)
  by pb1.pair.com with SMTP; 16 Apr 2004 22:23:49 -0000
Received: from localhost (localhost [127.0.0.1])
	by jdi.jdimedia.nl (8.12.10/8.12.10) with ESMTP id i3GMNkst005804;
	Sat, 17 Apr 2004 00:23:46 +0200
Date: Sat, 17 Apr 2004 00:23:14 +0200 (CEST)
X-X-Sender: derick@localhost
To: Sterling Hughes <sterling@php.net>
cc: john@coggeshall.org, Christian Schneider <cschneid@cschneid.com>,
        PHP Internals <internals@lists.php.net>
In-Reply-To: <45808D19-8FF4-11D8-9B29-000A95E073A0@php.net>
Message-ID: <Pine.LNX.4.58.0404170022130.2091@localhost>
References: <00cc01c422e1$46a4adc0$0100a8c0@pc07653> 
 <1082070778.17792.18.camel@coogle.localdomain>  <Pine.LNX.4.58.0404160932040.2091@localhost>
 <1082130174.31819.51.camel@coogle.localdomain>  <4080035B.1090404@cschneid.com>
 <1082132272.31824.56.camel@coogle.localdomain> <40800930.2070302@cschneid.com>
 <Pine.LNX.4.58.0404161838131.2091@localhost> <45808D19-8FF4-11D8-9B29-000A95E073A0@php.net>
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 Fri, 16 Apr 2004, Sterling Hughes wrote:

> 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..?

I have to agree with this. Although it might be useful (to some people),
messing with it all the time warrants a nice place in pecl.

Derick