Generating error messages: conventions?

[abackstrom]

I'm writing some fairly complex functions, and running lots of sanity checks along the way. Right now, I have a few calls to error_generate(), but my error handling is far from perfect. I was wondering how others deal with this aspect of Xbasic programming.

I think my two main options are 1) error_generate() and on error goto, and 2) ui_msg_box() and special function return values which signal some sort of failure. At this point, I can't see the forest for the trees. I'm leaning towards error_generate(), but if anyone has sugguestions I'd be glad to hear them.

[csda1]

It depends upon the purpose of the function and how it is used.

My general best method returns an error value so that the calling routine can process the error, and potentially pass it up the chain of calls

Sometimes, you want to ask the user as to what to do, with a UI call, so that he can make an intelligent response as to what to do, but then this can be repeated alot if many errors crop up, annoying the user. At this point, you can often ask the user what he'd like to do automatically in the future for this kind of error, thus allowing the multiple calls to complete without constant prompting.

Also, sometimes you want to log the error to a file or table or sometimes just a global variable.

Something I often do is add an optional parameter at the end of the function arguments (typically called Flags) that allows me to specify how I want to handle errors for this call, as well as specify other things to the function. This is often just a character type argument with a default value of "", which I interpret as a default set of flags - typically standard return with error values.

I never have used error_generate(), except to force an error handler to be invoked. I believe this is typically bad programming practice for a function. The only good reason to use this is to force an error branch when you can't return it as the function's value, but I have never found a case where I can't come up with a return method.

[Finian Lennon]

A couple of things to remember ..

In a script or function, On error goto label will remain in force unless you insert an On error goto 0 to restore default A5 error trapping.

In addition you have error_text_get() and a bunch of other error functions to show unexpected errors. These are listed in the online help.

Finian