data-rep.texi fix to replace scm_make_gsubr with scm_c_define_gsubr

[Richard Y. Kim]

As far as I can tell from reading guile documentation for version
1.5.4., scm_make_gsubr is deprecated.  scm_c_define_gsubr seems to be
the new name.  However, the guile manual still refers to the old name.
Here is a patch that updates the document to use the new name.

Without this change, the new name does not appear in the index of the
info file which means that documentation for scm_c_define_gsubr cannot
be reached via `info-lookup' GNU Emacs command.

bash$ diff -c data-rep.texi data-rep.texi-new
*** data-rep.texi       Sun Mar 31 17:10:08 2002
--- data-rep.texi-new   Sun Mar 31 17:21:52 2002
***************
*** 980,986 ****
  @var{x} is not a subr.
  @end deftypefn
  
! @deftypefun SCM scm_make_gsubr (char address@hidden, int @var{req}, int 
@var{opt}, int @var{rest}, SCM (address@hidden)())
  Create a new subr object named @var{name}, based on the C function
  @var{function}, make it visible to Scheme the value of as a global
  variable named @var{name}, and return the subr object.
--- 980,987 ----
  @var{x} is not a subr.
  @end deftypefn
  
! @c This used to be scm_make_gsubr which is now deprecated.
! @deftypefun SCM scm_c_define_gsubr (char address@hidden, int @var{req}, int 
@var{opt}, int @var{rest}, SCM (address@hidden)())
  Create a new subr object named @var{name}, based on the C function
  @var{function}, make it visible to Scheme the value of as a global
  variable named @var{name}, and return the subr object.
***************
*** 1005,1012 ****
  subr can take one required argument, or one required and one optional
  argument, but a subr can't take one required and two optional arguments.
  It's bizarre, but that's the way the interpreter was written.  If the
! arguments to @code{scm_make_gsubr} do not fit one of the predefined
! patterns, then @code{scm_make_gsubr} will return a compiled closure
  object instead of a subr object.
  @end deftypefun
  
--- 1006,1013 ----
  subr can take one required argument, or one required and one optional
  argument, but a subr can't take one required and two optional arguments.
  It's bizarre, but that's the way the interpreter was written.  If the
! arguments to @code{scm_c_define_gsubr} do not fit one of the predefined
! patterns, then @code{scm_c_define_gsubr} will return a compiled closure
  object instead of a subr object.
  @end deftypefun