I\'m developing some lower end code in my system that uses multiple child classes of the php exception class. Essentially I have the exceptions broken up to a few categorie
call set_exception_handler early in execution (don't forget to account for error_reporting()
). set_exception_handler
takes as its paramter what php calls a "callback". You can pass an object method like so:
// $object->methodName() will be called on errors
set_exception_handler(array($object, 'methodName'));
Wrap your dispatching code with try/catch
to catch any code that DOES throw exceptions. The catch part of your code will catch all your own codes' exceptions, plus some php errors that didn't generate an exception natively (eg fopen
or something), thanks to your set_exception_handler
call above. The php manual states:
The following error types cannot be handled with a user defined function: E_ERROR, E_PARSE, E_CORE_ERROR, E_CORE_WARNING, E_COMPILE_ERROR, E_COMPILE_WARNING, and most of E_STRICT raised in the file where set_error_handler() is called.
Log errors as necessary.
Create an error page template (the "View") that operates on an Exception object (the "Model") and pretty prints the whole stack trace for you, in development. Create a different template that goes to production. Branch on your environment, for example:
catch(Exception $e) {
// log error as necessary here.
if("in developement") {
// $e would be available to your template at this point
include "errortemplates/dev.php";
} else {
include "errortemplates/prod.php";
}
}