HTML_CSS : The Definitive Guide

There are many scenarios in which fine-grained control over error raising is absolutely necessary.

The first level to control error generation is the php.ini directives display_errors and log_errors. When these directives are set to TRUE, then browser and file outputs are effective.

	Tip
	If you want to ignore all errors raised (no display, no logs) and avoid to include PEAR core class, then you should have something like : <?php require_once 'HTML/CSS.php';   function myErrorHandler() {     return null; }   $errorConf = array('error_handler' => 'myErrorHandler'); $css = new HTML_CSS(null, $errorConf); // ... ?>

Note for users of HTML_CSS 1.4.0 or greater

You may want to decide to print (yes/no), log (yes/no) error messages with a full free user function local to HTML_CSS <?php require_once 'HTML/CSS.php';   function myErrorAction($css_error) {     // do what you want: print and/or log $css_error instance of HTML_CSS_Error object }   $errorConf = array('error_callback' => 'myErrorAction'); $css = new HTML_CSS(null, $errorConf); // ... ?> rather than using global PEAR error handler (PEAR::setErrorHandling, PEAR::pushErrorHandling, PEAR::popErrorHandling). <?php require_once 'HTML/CSS.php';   function myErrorAction($css_error) {     // do what you want: print and/or log $css_error instance of HTML_CSS_Error object }   PEAR::setErrorHandling(PEAR_ERROR_CALLBACK, 'myErrorAction');   $css = new HTML_CSS(); // ... ?>

With push_callback option, you can decides to stop script execution (as done with exceptions by default: returns PEAR_ERROR_DIE constant), or continue without filtering (returns NULL).

If you want to write your own callback function for the push_callback option, this one should have two arguments: first one will get the error code, and second will get error level. These are all the necessary informations to do a filtering. Example that follow show how to be aware that a script use wrong argument data type.