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.

actually, it would be a slight decrease in performance because PEAR_Error extends PEAR

You are wrong. =) I have 4.4.0 distribution and 4.3.11 sources. In addition: http://cvs.php.net/annotate.php/pear-core/PEAR.php?rev=1.94#803

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 ;).

Thanks. Checked them. Nothing changed. PEAR_Error doesn't extend PEAR. http://cvs.php.net/annotate.php/pear-core/PEAR.php?php=8ef2ad4ca5e69672b3a14ed8b96dbfcd&rev=1.82.2.6#773 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.