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
integer*8 obj, except call hooks_Basics__create_f (obj, except) c c Enable hooks execution (enabled by default) c ...for static methods c call hooks_Basics__set_hooks_static_f (1, except) c c ...for non-static methods c call hooks_Basics__set_hooks_f (obj, 1, except) c c ...do something meaningful... c c c Disable hooks execution c ...for static methods c call hooks_Basics__set_hooks_static_f (0, except) c c ...for non-static methods c call hooks_Basics__set_hooks_f (obj, 0, except) c c ...do something meaningful... c
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 8.4.5.