Hooks implementation

As discussed in Subsection 10.3.8, when hooks execution is enabled, implementation-specific instrumentation is executed. Using the --generate-hooks option on the Babel command line when generating implementation-side bindings results in the automatic generation of a _pre and _post method for every static and non-static method associated with each class in the specification. For the aStaticMethod specified in Subsection 10.3.8, the generated _pre method implementation is$:$


  public static void aStaticMeth_pre_Impl ( int i, int io )
    throws sidl.RuntimeException.Wrapper
  {
    // DO-NOT-DELETE splicer.begin(hooks.Basics.aStaticMeth_pre)
    /*
     * Add instrumentation here to be executed immediately prior
     * to dispatch to aStaticMeth().
     */
    // DO-NOT-DELETE splicer.end(hooks.Basics.aStaticMeth_pre)
  }

while that of the _post method is$:$


  public static void aStaticMeth_post_Impl ( int i, int o, int io, int _retval )
    throws sidl.RuntimeException.Wrapper
  {
    // DO-NOT-DELETE splicer.begin(hooks.Basics.aStaticMeth_post)
    /*
     * Add instrumentation here to be executed immediately after
     * return from dispatch to aStaticMeth().
     */
    // DO-NOT-DELETE splicer.end(hooks.Basics.aStaticMeth_post)
  }

Per the normal implementation process, the desired instrumentation should be added within the splicer blocks of aStaticMethod_pre and aStaticMethod_post. As stated in the comments within those blocks, aStaticMethod_pre will be executed immediately prior to dispatch to aStaticMethod when the latter is invoked by a client. Assuming no exceptions are encountered, aStaticMethod_post is executed immediately upon return from aStaticMethod.





babel-1.4.0
users_guide Last Modified 2008-10-16

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