Error() > Instance variables |
Generic numeric error code.
Data type: | N | Default: | NIL |
The instance variable contains a numeric value representing a generic error code. If :genCode contains zero, an unknown error has occurred. #define constants are listed in Error.ch for other generic error conditions.
Generic error codes
Constant | Value | Description |
---|---|---|
EG_ARG | 1 | Argument error |
EG_BOUND | 2 | Bound error |
EG_STROVERFLOW | 3 | Bound error, |
EG_NUMOVERFLOW | 4 | Numeric overflow |
EG_ZERODIV | 5 | Zero divisor |
EG_NUMERR | 6 | Zero divisor |
EG_SYNTAX | 7 | Syntax error |
EG_COMPLEXITY | 8 | Operation too complex |
EG_MEM | 11 | Memory low |
EG_NOFUNC | 12 | Undefined function |
EG_NOMETHOD | 13 | No exported method |
EG_NOVAR | 14 | Variable does not exist |
EG_NOALIAS | 15 | Alias does not exist |
EG_NOVARMETHOD | 16 | No exported variable |
EG_BADALIAS | 17 | Illegal characters in alias |
EG_DUPALIAS | 18 | Alias already in use |
EG_NOOBJECT | 19 | Not an object |
EG_CREATE | 20 | Create error |
EG_OPEN | 21 | Open error |
EG_CLOSE | 22 | Close error |
EG_READ | 23 | Read error |
EG_WRITE | 24 | Write error |
EG_PRINT | 25 | Print error |
EG_UNSUPPORTED | 30 | Operation not supported |
EG_LIMIT | 31 | Limit exceeded |
EG_CORRUPTION | 32 | Corruption detected |
EG_DATATYPE | 33 | Data type error |
EG_DATAWIDTH | 34 | Data width error |
EG_NOTABLE | 35 | Workarea not in use |
EG_NOORDER | 36 | Workarea not indexed |
EG_SHARED | 37 | Exclusive required |
EG_UNLOCKED | 38 | Lock required |
EG_READONLY | 39 | Write not allowed |
EG_APPENDLOCK | 40 | Append lock failed |
EG_LOCK | 41 | Lock Failure |
EG_ARRACCESS | 46 | array access |
EG_ARRASSIGN | 47 | array assign |
EG_ARRDIMENSION | 48 | array dimension |
EG_NOTARRAY | 49 | not an array |
EG_CONDITION | 50 | conditional |
EG_BADSELF | 51 | Invalid self |
EG_ARRREF | 52 | reserved |
EG_OLEEXECPTION | 1001 | (OLE exception occurred) |
Note: if an Error object is created in a user-defined error handling routine, the above generic error codes should be used, if possible. A textual description of the error can then be retrieved using HB_LangErrMsg() which is then assigned to oError:description.
http://www.xHarbour.com