On Wed, 2004-01-21 at 21:37, [EMAIL PROTECTED] wrote: > > On Wed, 2004-01-21 at 20:19, Chris W wrote: > >> Robert Cummings wrote: > > May i ask how you handle your error handling Robert ? I'm considering > moving my class error handling to pear but then it'll need a custom class > or function anyway to handle the errors in different ways for different > applications and functions, exiting to the screen just isnt friendly for an > end user.
Well in my php.ini I set the following: error_reporting = E_ALL Other than that I use the InterJinn framework which defines an error handling service. The error handling service has a specific API, and honours the settings in the php.ini for outputting to screen or to log file. I format the errors when they are to be displayed and the InterJinn framework is running in web mode. The nice thing about the error handling service is that it can be extended or completely replaced by any other handler service following InterJinn's error service API and all Core code will automatically use the newly registered error service -- just like every other service in the framework (database, session, profile, url, form, etc, etc.). Cheers, Rob. -- .------------------------------------------------------------. | InterJinn Application Framework - http://www.interjinn.com | :------------------------------------------------------------: | An application and templating framework for PHP. Boasting | | a powerful, scalable system for accessing system services | | such as forms, properties, sessions, and caches. InterJinn | | also provides an extremely flexible architecture for | | creating re-usable components quickly and easily. | `------------------------------------------------------------' -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
