RHJ4 Diagnostics

There are only three commonly used methods to debug code:

1. Iteratively alter the code until you get the desired effect. This is useful for fine-tuning screen layouts, but not for code bugs.
2. Use diagnostic trace statements to capture critical flow information.
3. Use a debugger with breakpoints so you can stop and examine code and variables.

1. The error log file's location is defined in php.ini and, depending on your configuration, may not be visible to you.
2. You can easily enable and disable logging at various places in your code.
3. Diagnostic statements can be written into a variety of files or even databases.
4. You can add the shortcode [rhj4_diagnostics show=true] to any page and see the entire contents of the current logfile.
5. The shortcode [rhj4_diagnostics clear=true] will delete the logfile.

RHJ4Diagnostics::instance('enabled'=>true|false);

$diags->option(array ('level' => E_ALL & ~E_DEPRECATED & ~E_NOTICE & ~E_STRICT);

$diags->option(array ('level' => 0);

$diags = RHJ4Diagnostics::instance(); $diags->diagnostic('Message # 1', 'FUNCTION A: '); ... $diags->diagnostic('Message # 2', 'FUNCTION B: '); ... $diags->diagnostic('Message # 3', 'FUNCTION C: ');

$diags->diagnostic('Message text', array('output'=> array( 'function' => 'my_diagnostic_test_output', 'logfile' => 'demo.log')));

Yes. The "threshold" option determines which messages will be displayed. If the current threshold value is 10 and the message's threshold value is greater than 10, the message will not be logged. If the message threshold is 10 or less, it will be logged. $diags = RHJ4Diagnostics::instance(); $diags->options(array('enabled' => true, 'threshold' => 6); $diags->diagnostic('This message will not be logged',array('threshold'=>7)); $diags->diagnostic('This message will be logged',array('threshold'=>5));

Yes. On the first page establish your settings like this: $diags = RHJ4Diagnostics::instance(); $diags->set(array('enabled' => true, 'threshold' => 6);