Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:7830
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
To: internals@lists.php.net
In-Reply-To: <20040213175429.GC702@bumblebury.com>
References: <5.1.0.14.2.20040213194729.02b6f718@127.0.0.1>
	 <20040213175429.GC702@bumblebury.com>
Content-Type: text/plain
Message-ID: <1076839483.266.10.camel@localhost>
Mime-Version: 1.0
Date: Sun, 15 Feb 2004 11:04:43 +0100
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: [ZEND-ENGINE-CVS] cvs: ZendEngine2 /
	zend_default_classes.c zend_default_classes.h zend_execute.h
	zend_execute_API.c
From: thekid@thekid.de (Timm Friebe)

On Fri, 2004-02-13 at 18:54, Sterling Hughes wrote:
[...]
> I get the concept, that's the reason Exception was added.  But its meant
> to be a voluntary thing (I believe this has been discussed before btw),
> a standard class that gives users something to build upon, should they
> want to.  I think an all-your-base-is-belonging-to-Exception is the
> wrong way to go.

I agree with Sterling. What if I have some really methods in my base
class that I rely on being existant in each and every subclass of it,
including Exception (or any other name I thought of to work around
"Exception" being built-in)?

- Timm