Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Closing application after an error
Message
 
 
To
09/08/2005 10:12:57
General information
Forum:
Visual FoxPro
Category:
The Mere Mortals Framework
Environment versions
Visual FoxPro:
VFP 8 SP1
OS:
Windows XP SP2
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01039447
Message ID:
01039548
Views:
18
>Hi Naomi,
>of course.
>
>A decent application has to have a complete control of the bugs:
>- a structure of hierarchical traps
>- the principal trap has to be immune from the bugs and owes
>to capture every predictable or unpredictable bug
>- every transaction has to have a specific trap
>- every interaction has to have a specific trap
>- other levels are desirable
>- every predictable error has to be listed
>for gravity in basic to the effects that it provokes
>- in the case the trap of level N can contain the effects to local level
>it is enough that it interrupt the local sequence and return to the preceding state
>- in the case doesn't succeed or doesn't know whether to resolve it besides returning to the state, precedent has to pass the error to the trap N-1.
>In practice, a program is well done if the system of traps succeeds
>to survive or to check (eventually committing suicide itself) to every possible sequence of code, also casual, so that the output is Always correct
>(better any outputs that the possibility of a wrong output)
>
>Unfortunately the traps of VFP use the traps of C++ that use the traps of the OS that it uses the traps of the CPU, and therefore to write traps without bugs in VFP is an illusion.
>
>Fabio

Fabio,

Thanks a lot for your input. My question is more practical and I am especially interested in other MereMortals users experience in dealing with this problem. Yesterday I briefly checked MereMortals Error handling mechanism implementation and found it very simplistic. The Error Handler basically sets a flag to shutdown the system in case of an error. It doesn't care, if the system could be really closed, so all sequential errors are not trapped properly. Did anyone besides me found it a problem?

At my previous job we used Mike Asherman's Error Handler, which is quite sophisticated. I don't remember of hand, if we ever had a problem when VFP native error pops up after Error Handler reported the error. I think, there were such occurrances, but in a lesser rate than we're having now...
If it's not broken, fix it until it is.


My Blog
Previous
Reply
Map
View

Click here to load this message in the networking platform