Hooks execution

If a given component supports pre- and post-method invocation instrumentation, also known as ``hooks'', their execution can be enabled or disabled at runtime through the built-in _set_hooks method. For example, given the following SIDL specification$:$


package hooks version 1.0
{
  class Basics {
    /**
     * Basic illustration of hooks for static methods.
     */
    static int aStaticMeth(in int i, out int o, inout int io);

    /**
     * Basic illustration of hooks for static methods.
     */
    int aNonStaticMeth(in int i, out int o, inout int io);
  }
}

which has a single static function and a member function for the Basics class, the processes for enabling and disabling execution of the implementation-specific hooks are$:$


#ifdef SIDL_USE_UCXX
using namespace ucxx;
#endif

    try {
      hooks::Basics obj = hooks::Basics::_create();

      /* Enable hooks execution (enabled by default) */
      /* ... for static methods */
      hooks::Basics::_set_hooks_static(TRUE);

      /* ... for non-static methods */
      obj._set_hooks(TRUE);
   

      /* ...do something meaningful... */


      /* Disable hooks execution (on by default) */
      /* ... for static methods */
      hooks::Basics::_set_hooks_static(FALSE);

      /* ... for non-static methods */
      obj._set_hooks(FALSE);


      /* ...do something meaningful... */

    } catch (::sidl::RuntimeException e) {
      cout << e.getNote() << endl;
    }

It is important to keep in mind that the _set_hooks_static method must be used to enable/disable invocation of hooks for static methods and the _set_hooks method must be used for those of non-static methods. Also, Babel does not provide client access to the _pre and _post methods; therefore, they cannot be invoked directly. More information on the instrumentation process is provided in Subsection 7.4.5.





babel-1.4.0
users_guide Last Modified 2008-10-16

http://www.llnl.gov/CASC/components
components@llnl.gov