PIPS
|
Go to the source code of this file.
Functions | |
void | reset_hooks_register (reset_func_t function) |
add function to be called for cleanup if an exception is raised. More... | |
void | reset_hooks_call (void) |
this function is expected to be called when catching an exception. More... | |
void | reset_hooks_is_empty (void) |
check that the stack was cleaned. More... | |
void | reset_hooks_unregister (reset_func_t function) |
remove registered cleanup hook. More... | |
Variables | |
static list | reset_hooks = NIL |
reset functions to call on exceptions to be used by pipsmake? More... | |
void reset_hooks_call | ( | void | ) |
this function is expected to be called when catching an exception.
Definition at line 53 of file reset_hooks.c.
References f(), FOREACH, gen_free_list(), NIL, reset_hooks, and VOID_STAR.
Referenced by reset_static_phase_variables().
void reset_hooks_is_empty | ( | void | ) |
check that the stack was cleaned.
Definition at line 66 of file reset_hooks.c.
References NIL, pips_assert, and reset_hooks.
Referenced by catch_user_error().
void reset_hooks_register | ( | reset_func_t | function | ) |
add function to be called for cleanup if an exception is raised.
function | unction |
Definition at line 44 of file reset_hooks.c.
References CONS, gen_in_list_p(), pips_assert, reset_hooks, and VOID_STAR.
Referenced by atomize_as_required(), hpfc_close(), hpfc_common(), hpfc_compile(), hpfc_directives_handler(), hpfc_filter(), hpfc_init(), module_to_value_mappings(), and print_module_icfg().
void reset_hooks_unregister | ( | reset_func_t | function | ) |
remove registered cleanup hook.
function | unction |
Definition at line 73 of file reset_hooks.c.
References gen_in_list_p(), gen_remove_once(), pips_assert, and reset_hooks.
Referenced by atomize_as_required(), free_value_mappings(), hpfc_close(), hpfc_common(), hpfc_compile(), hpfc_directives_handler(), hpfc_filter(), hpfc_init(), and print_module_icfg().
reset functions to call on exceptions to be used by pipsmake?
should it be a stack? should there by a stack of stacks for different TRY/CATCH levels? should it be processed up to a marker? would an additionnal void* for arguments make sense?
Definition at line 40 of file reset_hooks.c.
Referenced by reset_hooks_call(), reset_hooks_is_empty(), reset_hooks_register(), and reset_hooks_unregister().