RE: [PEAR] RE : [PEAR] Inquiry: Any interest in an ErrorHandler class?

Hi Greg, I don't understand why they didn't appreciate your classes, especially as there is nothing of this kind in the repository yet. Is there anything I can do to help your bid? What I was especially missing is an easy way to track Pear::DB transaction errors for an easy rollback/commit check. The DB package is missing this (as far as I have noticed). I have now implemented this into my own little error handler class (which is not as complex as yours). If you are interested in any details I could send you some sample files. I don't mind if you say 'no' ;) Regards, Torsten -----Original Message----- From: Greg Beaver [mailto:greg@chiaraquartet.net] Sent: Tuesday, December 16, 2003 2:52 PM To: Torsten Roehr Cc: pear-general@lists.php.net Subject: Re: [PEAR] RE : [PEAR] Inquiry: Any interest in an ErrorHandler class? Hi Torsten, I proposed these classes a long time ago to lukewarm response, you are welcome to compete :). I am actually much more interested in developing a stack-based implementation of error handling, where it would be possible to return multiple errors from the same function, so I will be re-designing my classes from scratch to implement this. You're welcome to hack out anything you see in my classes that appeals to you. Regards, Greg Torsten Roehr wrote: > Hi Arnaud, > > thanks for the link. Obviously Greg is already trying to get his package(s) > into PEAR - so there is no need to compete with this ;) > > Thanks & regards, > > Torsten > > > >>Hi, > > >>You might want to have a look at Greg Beaver Error_Raise and Error_Handler >>at > > >>http://www.chiaraquartet.net/apidoc/ > > >>Arnaud. > > >>Hi there, >> >>is anyone interested in an ErrorHandler class? I couldn't >>find anything like that in the PEAR repository. Possible features are: >>- Handling of PEAR and PHP errors all in one >>- Option to print errors out on screen (for debugging) or >>quietly email to Administrator (for real life operation) >>- Manages user messages (errors and notices), e.g.: >> "Incomplete/invalid input: >> - Please enter a correct name >> - Please enter a valid email address", >> "The new record set has been saved." and so on >>- Formatting of user messages (errors and notices) via CSS >>- Possibility to track and count transaction errors for easy >>commit/rollback checking >>- maybe even output buffering to catch fatal errors (haven't >>tried this yet) >> >>I'm using a class like that for my applications and >>especially the email function and user messages management >>are quite handy. Nearly every application has to display >>messages for the users. So why not combine this with the >>handling of the application errors. The printed/emailed >>application errors will contain detailed information about >>the error (failed SQL statement etc.). >> >>If you have questions, proposals or would like to see a >>demonstration, please answer to the mailing list. >> >> >>Thanks and best regards, >> >>Torsten Roehr >> >>-- >>PEAR General Mailing List (http://pear.php.net/) >>To unsubscribe, visit: http://www.php.net/unsub.php >>