| [ Index ] |
PHP Cross Reference of Web Application Component Toolkit |
[Source view] [Print]
(no description)
| Version: | $Id: debug.inc.php,v 1.2 2004/10/16 20:43:49 jeffmoore Exp $ |
| File Size: | 238 lines (7 kb) |
| Included or required: | 0 times |
| Referenced: | 0 times |
| Includes or requires: | 0 files |
| handleerror($ErrorNumber, $ErrorMessage, $FileName, $LineNumber) X-Ref |
| Putting high-level operations in an error handler leads to the dreaded recursive error problem that is the bane of non exception based error handling. Yet its nice to allow error message pages to have the look and feel of the rest of the site. that said, this function directly outputs HTML, and instead should probably format its output using a template. That way, the template can be customized to match the look at feel of the site using the framework. The price of this is by using a template, there is an increased risk of a new error occurring while handling an error. A bad situation. |
| handleframeworkerror($ErrorMessage) X-Ref |
| Handles WACT specific framework errors. Currently "hacked" to disable multiple generation of error messages with compileall. BareBonesErrorHandler should be declared before calling importVarFile |
| displaytraceback() X-Ref |
| No description |
| handlegeneralerror($ErrorNumber, $ErrorMessage, $FileName, $LineNumber) X-Ref |
| Handles general erros (e.g. PHP errors) |
| bareboneserrorhandler($ErrorNumber, $ErrorMessage, $FileName, $LineNumber) X-Ref |
| This function is called only when an error has occured in the error handler. Usually this is because there is a problem accessing the template system. Here we heroicly attempt to print out something intelligable for the original error. |
| Generated: Sun Nov 28 19:36:09 2004 | Cross-referenced by PHPXref 0.5 |