merged branch igorw/cookbook-fatal (PR #735)

This PR was merged into the 1.0 branch.

Discussion
----------

Add note on how to handle fatal errors

I'm not so happy with this solution from a usability perspective, but I don't want to have global error handlers in silex itself.

An option we could consider is making symfony's ErrorHandler fall back to an internal ``ExceptionHandler`` for fatal errors. But obviously that is not very elegant either. Ideas welcome.

Commits
-------

7a222ce5 Add note on how to handle fatal errors, as per mailing list

doc/cookbook/error_handler.rst

@@ -29,8 +29,19 @@ You register it by calling the static ``register`` method::
 It is recommended that you do this in your front controller, i.e.
 ``web/index.php``.
 
-.. note::
+Handling fatal errors
+---------------------
 
-    The ``ErrorHandler`` has nothing to do with the ``ExceptionHandler``. The
-    ``ExceptionHandler`` is responsible for displaying caught exceptions
-    nicely.
+To handle fatal errors, you can additionally register a global
+``ExceptionHandler``::
+
+    use Symfony\Component\HttpKernel\Debug\ExceptionHandler;
+
+    ExceptionHandler::register();
+
+In production you may want to disable the debug output by passing ``false`` as
+the ``$debug`` argument::
+
+    use Symfony\Component\HttpKernel\Debug\ExceptionHandler;
+
+    ExceptionHandler::register(false);