Re: why don't most classes extend PEAR?
| From: | Chuck Hagenbuch | Date: | Thu, 06 Sep 2001 15:18:31 +0000 |
| Subject: | Re: why don't most classes extend PEAR? | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-1825@lists.php.net to get a copy of this message | ||
Quoting greg keraunen <gk@proliberty.com>:
> It would be nice if there were some way in which the cvs hierarchy
> reflected which classes extend PEAR.php and which do not.
I don't think that's a good way to go. For instance, how would you have the
hierarchy reflect the fact that a package had it's own, added-functionality
error class, which naturally extends PEAR_Error? I.e.:
Pear.php
PEAR/
Error.php
Package.php
Package/
Error.php
That class is very definitely part of Package - it shouldn't go under
PEAR/Error/foo.
-chuck
--
Charles Hagenbuch, <chuck@horde.org>
Some fallen angels have their good reasons.