Re: updated docs for Error_Raise
| From: | Martin Jansen | Date: | Thu, 21 Aug 2003 09:06:51 +0000 |
| Subject: | Re: updated docs for Error_Raise | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-20225@lists.php.net to get a copy of this message | ||
On Wed Aug 20, 2003 at 06:1024PM -0400, Greg Beaver wrote:
> There is one other concern that I hadn't realized was an assumption on
> my part - performance suffers slightly if we continue to use existing
> raiseError. My solution circumvents this problem through new methods
> that break BC, using existing raiseError would add a slight performance
> penalty.
Do you have any concrete numbers for that? Perhaps we can find a way to
get back that performance decrease elsewhere in the code.
> One of the most common complaints about PEAR's error handling is that
> the PEAR.php file adds a ton of overhead.
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?
--
- Martin Martin Jansen
http://martinjansen.com/