Dec 222017
Full Description of File
A Clipper 5 ErrorSys error handler. This
function is not an error handler in itself.
It shows all information about the error then
calls the normal Clipper error handler.
A Very good learning tool for the Clipper
programmer to learn more about ErrSys.
function is not an error handler in itself.
It shows all information about the error then
calls the normal Clipper error handler.
A Very good learning tool for the Clipper
programmer to learn more about ErrSys.
A Clipper 5 ErrorSys error handler. This function is not an error handler in itself. It shows all information about the error then calls the normal Clipper error handler. | |||
---|---|---|---|
File Name | File Size | Zip Size | Zip Type |
FILE_ID.DIZ | 266 | 162 | deflated |
SHOWERR.CH | 50 | 41 | deflated |
SHOWERR.OBJ | 3417 | 1830 | deflated |
SHOWERR.PRG | 6659 | 2108 | deflated |
SHOWERR.TXT | 2269 | 845 | deflated |
TEST.PRG | 960 | 436 | deflated |
Download File SHWERR.ZIP Here
Contents of the SHOWERR.TXT file
When an error occurs in Clipper 5.01, the errorsys is called and is passed
an error object. This object contains values that the errorsys acts upon.
This ShowErr() module will display those values (instance variables) in a
TBrowse so that they can be studied.
This program does not modify Clipper 5.01's errorsys. What it does is delay
it a little bit. To use this module simply place the line '#include
"showerr.ch"' in your program after your first variable declarations.
EXAMPLE #1
------------------------------------------------------------------------------
< start of file >
FUNCTION Main()
LOCAL < xVariable >
LOCAL < xVariable >
STATIC< xVariable >
#include "showerr.ch"
.
.< statements >
.
< end of file >
------------------------------------------------------------------------------
EXAMPLE # 2
------------------------------------------------------------------------------
< start of file >
LOCAL < xVariable >
LOCAL < xVariable >
STATIC< xVariable >
#include "showerr.ch"
.
.< statements >
.
< end of file >
-----------------------------------------------------------------------------
Then link in the object file ShowErr.obj:
RTLINK FI < filename >, ShowErr
Voila!
When an error occurs the TBrowse will display the error object's instance
variables, wait for a keypress, then continue with Clipper 5.0's errorsys.
Again, this does not overwrite or replace Clipper 5.0's errorsys. It just
inserts itself between your application and the errorsys. The only drawback
is that the calling procedures listing when a program is terminated through
an error, will list ShowErr() as one of the calling procedures. Small price
to pay, I think.
If you encounter any errors with this module please let me know. I'll hang
my head in shame.
*****************************************************************************
A source file, Test.prg, is included as an example of a program which will
create an error. Compile this program with the /n switch. When you run this
program, an open error will occur first. Choose the "Default" option to move
to the next error.
*****************************************************************************
an error object. This object contains values that the errorsys acts upon.
This ShowErr() module will display those values (instance variables) in a
TBrowse so that they can be studied.
This program does not modify Clipper 5.01's errorsys. What it does is delay
it a little bit. To use this module simply place the line '#include
"showerr.ch"' in your program after your first variable declarations.
EXAMPLE #1
------------------------------------------------------------------------------
< start of file >
FUNCTION Main()
LOCAL < xVariable >
LOCAL < xVariable >
STATIC< xVariable >
#include "showerr.ch"
.
.< statements >
.
< end of file >
------------------------------------------------------------------------------
EXAMPLE # 2
------------------------------------------------------------------------------
< start of file >
LOCAL < xVariable >
LOCAL < xVariable >
STATIC< xVariable >
#include "showerr.ch"
.
.< statements >
.
< end of file >
-----------------------------------------------------------------------------
Then link in the object file ShowErr.obj:
RTLINK FI < filename >, ShowErr
Voila!
When an error occurs the TBrowse will display the error object's instance
variables, wait for a keypress, then continue with Clipper 5.0's errorsys.
Again, this does not overwrite or replace Clipper 5.0's errorsys. It just
inserts itself between your application and the errorsys. The only drawback
is that the calling procedures listing when a program is terminated through
an error, will list ShowErr() as one of the calling procedures. Small price
to pay, I think.
If you encounter any errors with this module please let me know. I'll hang
my head in shame.
*****************************************************************************
A source file, Test.prg, is included as an example of a program which will
create an error. Compile this program with the /n switch. When you run this
program, an open error will occur first. Choose the "Default" option to move
to the next error.
*****************************************************************************
December 22, 2017
Add comments