Re: Error_Stack

PEAR_Goof sounds good to me, or even better PEAR_F***up Then we can just call PEAR::f***edup() to see if there are any errors :) However, I would be very unhappy to force a require of PEAR.php unless destructor code is nuked. There are several static methods that may be called often, and as this is forward-compatible, it would be impossible to put them in another class. I will be moving the singleton array into a private static member just as soon as a PHP5-only version of PEAR is released, and this will mean that only internal methods will have access to it. Incidentally, I don't believe Err is less clear than Error, to err means to cause an error. I would be very happy if its name stayed the same, even if it is bundled with PEAR. This would allow future error handling enhancements to all be in the Error/ directory. Pierre, any thoughts? Greg Joe Stump wrote:

When looking for other names it's always good to check out dictionary.com's Thesaurus :) http://thesaurus.reference.com/search?q=error PEAR_Boner, PEAR_Goof, PEAR_Slip-Up, PEAR_Muff and PEAR_Flub are all good ones ;) In all seriousness though it should be renamed and I definitely don't like the "PEAR_Errors" name. How often would PEAR_Error_Stack need to be called? If it's rare then who cares. If it's often then why not roll some checking functions into PEAR as was done with PEAR::isError?