Bindings implementation

Implementation details must be added to the ``Impl'' files generated in Subsection 9.4.1. Changes to these files must be made between code splicer pairs to ensure their retention in subsequent invocations of Babel. Below is an example of the standard, automatically generated code splicer pairs.


! DO-NOT-DELETE splicer.begin(_miscellaneous_code_start)
! Insert-Code-Here {_miscellaneous_code_start} (extra code)
! DO-NOT-DELETE splicer.end(_miscellaneous_code_start)

.
.
.

recursive subroutine Pkg_Class_name_mi(self, arg, exception)
  use sidl
  use sidl_BaseInterface
  use sidl_RuntimeException
  use Pkg_Class
  use Pkg_Class_impl
  ! DO-NOT-DELETE splicer.begin(Pkg.Class.name.use)
  ! Insert-Code-Here {Pkg.Class.name.use} (use statements)
  ! DO-NOT-DELETE splicer.end(Pkg.Class.name.use)
  implicit none
  type(Pkg_Class_t) :: self ! in
  integer (kind=sidl_int) :: arg ! in
  type(sidl_BaseInterface_t) :: exception ! out

! DO-NOT-DELETE splicer.begin(Pkg.Class.name)
! Insert-Code-Here {Pkg.Class.name} (name method)
! DO-NOT-DELETE splicer.end(Pkg.Class.name)
end subroutine Pkg_Class_name_mi

The comment ``Insert-Code-Here'' associated with the ``miscellaneous code start'' splicer pair will need to be replaced with details such as additional abbreviation file(s) and any local, or private, subroutines. For the subroutine's ``use'' splicer pair, the ``Insert-Code-Here {Pkg.Class.name.use} (use statements)'' comment must be replaced with any use statements needed by the subroutine. Finally, the implementation between the subroutine body's splicer pairs must be added in place of the ``Insert-Code-Here {Pkg.Class.name} (name method)'' comment.





babel-1.4.0
users_guide Last Modified 2008-10-16

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