Global Error Handler

[xCav8r]

I found another article with some useful information on the subject of error handling: http://www.developerfusion.com/show/1741/

What exactly does a global error handler DO? Handle ALL errors? You could easily end up with a monster routine larger than the original app.

This thread is long, and the worthy content is sporadic and convoluted, so I don't fault you for not having read all of the posts that gradually led to answers to the questions you pose here. 500) {this.width=500;this.alt='Full View';}" border=0>

I admitted that global error handler was a slight misnomer, because it conveys to some the idea of a single error handler, which is not the concept I intended when I started the thread, and I apologize for not having been clearer up front. For the purposes of this discussion, global error handler refers to a set of routines that in conjunction respond to and log unhandled errors.

Does this makes any sense? Topic is open for discussion.

I?m not sure that I totally follow what you?re saying, but I think some of your comments might have been directed to a different notion of global error handler.

I group my procedures together with procedures that deal with similar things. For example, I have a standard module that does stuff with printers (gets information about available printers, selects trays, changes duplex settings, sends big print jobs in batches to avoid problems with memory limitations in certain printers, etc). Although some procedures work with others in the same module to achieve a goal, the same could be said of procedures across modules. And, because it?s not uncommon for a task to be accomplished using multiple procedures all in different modules, it?s difficult to conceive of something I could do at a module level (standard, not class) along the lines of what you described.

Don't forget if you design your error handling wel you could also use a separate DLL to process the Error log. This could be slimmed down for a release version but if need be you could easily replace that with a bulkier one!

That's a consideration, I think, for farther down the road.

But the Error lines have to be in the code to begin with otherwise that trick won't work...

Indeed. That'll need to be the last step before releasing a project that uses this error handling scheme.