Hi, I'm going into the creation / design of a framework and the first thing I'd like to know about is what a debugging class is.

__________________
VillageIdiot can have my babbies ;d

A debugging class would be a component of the framework that eases the debugging if something goes wrong while executing. An example of a debugging component could be to generate a backtrace using debug_backtrace() into some easily understandable trace, so errors/warnings/exceptions can be tracked and you can figure out where you went wrong.

__________________

On this subject - how would you go an create an Error class for a framework, and how would you implement it and use it?

__________________

Create an Error class for a framework? I'm not entirely sure that you would want to do so.

Why wouldn't you want to create an errorclass that handles Exceptions and stuff ?

__________________

Firstly, error conditions and exceptions are different beasts. Secondly, you probably wouldn't want one class to take care of everything, but rather tie a collection of classes together: these will be different depending on your framework and requirements wanted.

Well, isn't Exceptions a form of Error Handling - yes?
I didn't specify Error conditions, I just said Errorclass.

But okay, I see.. well, but still does anyone know a tutorial or anything about how to create a "collection of classes" to handle exceptions? Sure - it may be different than the framework I use, but I'm just looking for some guidance to understand the concept. I know how Exceptions work, I just need to understand how an Exception class works ^_^

__________________

Would this work with error_get_last?

__________________
VillageIdiot can have my babbies ;d

error_get_last() or register your own error handlers (set_error_handler & set_exception_handler) which pops all the errors onto a stack and then list all registered errors upon debugging shutdown.

__________________

How should I create a debugging class? That's all I'm wondering now.

__________________
VillageIdiot can have my babbies ;d

I would rather use a set of procedural functions for debugging than a class, instead of making a class where almost all methods are better served static (from my point of view).

All you need is a set of functions thats usable for debugging, and only included when debug mode is triggered (if your system ofcourse have a debugging mode).

Example of functions can be:

• Backtracing in a nice manner thats more detailed that the regular debug_print_backtrace() output
• Functions for catching and displaying exceptions and errors in somewhat unified interface, combining this with the backtrace is a good idea, as it can show if anywhere in the backtrace something occured
• Assertions, http://www.php.net/assert

__________________