Manipulate error/throw descriptors.
More...
Manipulate error/throw descriptors.
These routines do useful stuff on error descriptors
Notice that if the argument is an error descriptor, and you pass NULL, they always expect it to refer the current Active error descriptor
◆ event()
◆ Yap_errorName()
char * Yap_errorName |
( |
yap_error_number |
e | ) |
|
◆ Yap_errorNumber()
yap_error_number Yap_errorNumber |
( |
yap_error_class_number |
c, |
|
|
const char * |
s |
|
) |
| |
given a string(s, lookup for a corresponding error class r numbe
given a string(s) and class context, lookup for a corresponding error numbe
Definition at line 1570 of file errors.c.
◆ Yap_get_exception()
bool Yap_get_exception |
( |
USES_REGS1 |
| ) |
|
◆ Yap_GetException()
clone Active Error
Definition at line 1389 of file errors.c.
◆ Yap_PeekException()
is an error active?
Definition at line 1377 of file errors.c.
◆ Yap_PrintException()
print descriptor to user_output/stdout
Definition at line 1401 of file errors.c.
◆ Yap_RaiseException()
bool Yap_RaiseException |
( |
| ) |
|
◆ Yap_ResetException()
clean up (notice that the code ensures ActiveError exists on exit
Definition at line 1425 of file errors.c.
◆ Yap_RestartException()
clean up (notice that the code ensures ActiveError exists on exit
Definition at line 1438 of file errors.c.