I have an idea (or 2 or more) of an inc file to "Beef-Up" normal Error Handling Techniques (some redundant, some a bit more detailed) that seem to be coming along fine, but hopefully some people can help me shortcut some research (or explain some stuck points I hit in my understanding of documentation)
Right now, this is kinda generic until I can post code to demonstrate, but some questions that come to mind are:
ERL: Return the last line number encountered before the most recent error.
ERROR <Insert Number>
Next is a bit Harder, but my ideas of errors that could occur in DLL's or INC files that I did not write were to log a copy of Function and parameters passed (Just like TRACE, but a lil bit deeper). My First try was with anything out of my control was to have a string variable that before I call I place a string copy of what is about to be called (since unknown number of parameters, and unknown function to be called)...then I started seeing a pattern....and then another discussion mentioned "DISPPARAMS"
Anyways, enough of confusing questions, but hopefully some people out there have some constructive ideas???
Right now, this is kinda generic until I can post code to demonstrate, but some questions that come to mind are:
ERL: Return the last line number encountered before the most recent error.
- Since ERL is a PB KeyWord, is there an API equivelent?
- Does ERL only work if in the core *.bas file??? (My initial Tests tell me this is the case, cause in my *.Inc, it always shows line 0 or 1 (depending on how I write the code) meaning either error at the time of passing, or I need to do a bit more beefing because ERL changes once I pass on to another function?
ERROR <Insert Number>
- Can not be raised within callback, because I escape the callback, and any messages not handled are "Lost"??? (or I think this is the case???)
- SetLastError = the API equiv of ERROR (but I still must raise the error to fire the event?)
Next is a bit Harder, but my ideas of errors that could occur in DLL's or INC files that I did not write were to log a copy of Function and parameters passed (Just like TRACE, but a lil bit deeper). My First try was with anything out of my control was to have a string variable that before I call I place a string copy of what is about to be called (since unknown number of parameters, and unknown function to be called)...then I started seeing a pattern....and then another discussion mentioned "DISPPARAMS"
- Is "DISPPARAMS" only used with objects (like OCX???)
- How is it used?? (Simple example would help) since examples I have seen are confusing at the moment
- Is there a better procedural way??? (Been figuring that one out myself, but maybe that wheel has already been invented???)
Anyways, enough of confusing questions, but hopefully some people out there have some constructive ideas???

Comment