Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.10.13

Request #4995 Perfomance: move PEAR_Error to separate file
Submitted: 2005-08-04 08:32 UTC
From: techtonik Assigned: pajoye
Status: Closed Package: PEAR
PHP Version: 4.4.0 OS:
Roadmaps: (Not assigned)    
Comments Add Comment Add patch

Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
Solve the problem : 27 - 13 = ?

 [2005-08-04 08:32 UTC] techtonik
Description: ------------ Since many of us use PEAR possibilities only for error reporting it would be a "slight" perfomance boost to have PEAR_Error in separate file for inclusion.


 [2005-08-04 15:06 UTC] cellog
actually, it would be a slight decrease in performance because PEAR_Error extends PEAR
 [2005-08-05 16:44 UTC] techtonik
You are wrong. =) I have 4.4.0 distribution and 4.3.11 sources. In addition:
 [2005-08-05 16:50 UTC] pierre at dotgeek dot org
Greg is not, you are refering to HEAD which is 1.4. Check again the 1.3 sources. I agree with Greg, besides the BC issues introduced by such a change (ok, we can include pear_error in pear ;).
 [2005-08-06 11:08 UTC] techtonik
Thanks. Checked them. Nothing changed. PEAR_Error doesn't extend PEAR. Well, I can understand why you don't want to fix that. It is a design "feature" that PEAR_Error doesn't have isError and setErrorHandling methods. I agree that PEAR_Error alone is not that usable. To tell the truth I thought PEAR class contains more complicated abilities I didn't know about and don't have time to explore, but I need to use only PEAR error handling ability alone to ease the application and include only error handling class in distribution. Seems that PEAR.php is almost 90% of that I need.