Re: updated docs for Error_Raise
| From: | Martin Jansen | Date: | Thu, 21 Aug 2003 17:27:05 +0000 |
| Subject: | Re: updated docs for Error_Raise | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-20315@lists.php.net to get a copy of this message | ||
On Thu Aug 21, 2003 at 12:4304PM -0400, Greg Beaver wrote:
> >Maybe I'm just dumb at the moment, but why don't we move PEAR_Error to
> >it's own file and require_once() it in PEAR.php? Or ar PEAR_Error and
> >PEAR connected in a way that I have missed yet?
> >
> No, you're not dumb, this is the best solution. The biggest problem,
> actually, is not just the file size, but the fact that PEAR_Error
> extends PEAR. The destructor registration slows down things. I realier
> proposed the possibility of switching this so that PEAR extends
> PEAR_Error. If the error-raising methods are moved to PEAR_Error, there
> would be no BC implications.
Moving the stuff to PEAR_Error and deriving PEAR from it sounds like a
good plan. If you see a change to integrate that with your new error
handling stuff, seeing some diff's would be cool.
What do the maintainers of the PEAR core (Stig, Tomas, Sterling) think
about that, btw?
--
- Martin Martin Jansen
http://martinjansen.com/