reset_hooks.c File Reference

#include <stdio.h>
#include <genC.h>
#include "misc.h"

Include dependency graph for reset_hooks.c:

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...

Function Documentation

reset_hooks_call()

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.

{
  // call reset functions
  FOREACH(VOID_STAR, f, reset_hooks)
    (*((reset_func_t) f))();
 
  // cleanup
  gen_free_list(reset_hooks);
  reset_hooks = NIL;
}

References f(), FOREACH, gen_free_list(), NIL, reset_hooks, and VOID_STAR.

Referenced by reset_static_phase_variables().

Here is the call graph for this function:

Here is the caller graph for this function:

reset_hooks_is_empty()

void reset_hooks_is_empty

(

void

)

check that the stack was cleaned.

Definition at line 66 of file reset_hooks.c.

{
  pips_assert("no reset functions", reset_hooks == NIL);
}

References NIL, pips_assert, and reset_hooks.

Referenced by catch_user_error().

Here is the caller graph for this function:

reset_hooks_register()

void reset_hooks_register

(

reset_func_t

function

)

add function to be called for cleanup if an exception is raised.

reset_hooks.c

Parameters

function

unction

Definition at line 44 of file reset_hooks.c.

{
  pips_assert("reset function not already in list",
              !gen_in_list_p(function, reset_hooks));
  reset_hooks = CONS(VOID_STAR, function, reset_hooks);
}

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().

Here is the call graph for this function:

Here is the caller graph for this function:

reset_hooks_unregister()

void reset_hooks_unregister

(

reset_func_t

function

)

remove registered cleanup hook.

Parameters

function

unction

Definition at line 73 of file reset_hooks.c.

{
  // should it really be the first? probably too optimistic.
  /*
  pips_assert(reset_hooks &&
              VOID_STAR(CAR(reset_hooks)) == function,
              "unregister reset functions in reverse order");
  */
  pips_assert("unregister a function already registered",
              gen_in_list_p(function, reset_hooks));
  gen_remove_once(&reset_hooks, function);
}

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().

Here is the call graph for this function:

Here is the caller graph for this function:

Variable Documentation

reset_hooks

list reset_hooks = NIL

static

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().