Question

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 categories. What I’m wanting to do is two things.

1. I need all exceptions that are fired in the application to be handled in a single place.
2. I need to be able to log and then handle/generate the view for the user to receive feedback on the apps. error.

What I’m wondering is should I have some sort of try/catch encapsulating the application? I don’t like that idea at all, it sounds like a very crappy implementation. I also don’t like the idea of set_exception_handler unless i can sett the function to be a method of an object. The reason for this is that if I designate a function to handle the exceptions this will be the first function in the application. Everything else is a method of an object.

Hopefully I’ve provided enough details about the scenario. I’m trying to keep this clean and follow best practices. This code will be going OSS so I don’t feel like writing it 10 times 🙂

Answer 1

1. Run your web requests through a Front Controller script

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

3. 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.

4. Log errors as necessary.

5. 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';     } }