[PATCH] bound? in docs

[PATCH] bound? in docs

[Christopher Cramer]

bound? was removed on 2001-05-10, but it's still in the documentation.
This patch updates the documentation.

Index: doc/ref/scheme-binding.texi
===================================================================
RCS file: /cvsroot/guile/guile/guile-core/doc/ref/scheme-binding.texi,v
retrieving revision 1.1.2.5
diff -u -r1.1.2.5 scheme-binding.texi
--- doc/ref/scheme-binding.texi	15 Mar 2002 09:23:18 -0000	1.1.2.5
+++ doc/ref/scheme-binding.texi	3 Aug 2002 12:03:34 -0000
@@ -263,9 +263,7 @@
 @section Querying variable bindings
 
 Guile provides a procedure for checking whether a symbol is bound in the
-top level environment.  If you want to test whether a symbol is locally
-bound in expression, you can use the @code{bound?} macro from the module
-@code{(ice-9 optargs)}, documented in @ref{Optional Arguments}.
+top level environment.
 
 @c NJFIXME explain [env]
 @deffn {Scheme Procedure} defined? sym [env]
Index: doc/ref/scheme-procedures.texi
===================================================================
RCS file: /cvsroot/guile/guile/guile-core/doc/ref/scheme-procedures.texi,v
retrieving revision 1.1.2.9
diff -u -r1.1.2.9 scheme-procedures.texi
--- doc/ref/scheme-procedures.texi	20 Apr 2002 15:48:29 -0000	1.1.2.9
+++ doc/ref/scheme-procedures.texi	3 Aug 2002 12:03:37 -0000
@@ -136,7 +136,7 @@
 procedures these are used from.  The items in @var{rest-arg} are
 sequentially bound to the variable names are given. When @var{rest-arg}
 runs out, the remaining vars are bound either to the default values or
-left unbound if no default value was specified. @var{rest-arg} remains
+@code{#f} if no default value was specified. @var{rest-arg} remains
 bound to whatever may have been left of @var{rest-arg}.
 
 After binding the variables, the expressions @var{expr} @dots{} are
@@ -211,8 +211,7 @@
 creates a procedure with fixed arguments @var{a} and @var{b}, optional
 arguments @var{c} and @var{d}, and rest argument @var{e}. If the
 optional arguments are omitted in a call, the variables for them are
-unbound in the procedure. This can be checked with the @code{bound?}
-macro (documented below).
+bound to @code{#f}.
 
 @code{lambda*} can also take keyword arguments. For example, a procedure
 defined like this:
@@ -261,14 +260,6 @@
 are equivalent in all respects to @code{lambda*}. This is provided for
 more similarity to DSSSL, MIT-Scheme and Kawa among others, as well as
 for refugees from other Lisp dialects.
-@end deffn
-
-@deffn {library syntax} bound? variable
-Check if a variable is bound in the current environment.
-
-The procedure @code{defined?} doesn't quite cut it as it stands, since
-it only checks bindings in the top-level environment, not those in local
-scope only.
 @end deffn
 
 

-- 
Christopher Cramer <crayc@pyro.net> <http://www.pyro.net/~crayc/>
On résiste à l'invasion des armées; on ne résiste pas à l'invasion
des idées.  -- Victor Hugo

_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile

Re: [PATCH] bound? in docs

[Marius Vollmer]

Christopher Cramer <crayc@pyro.net> writes:

> bound? was removed on 2001-05-10, but it's still in the documentation.
> This patch updates the documentation.

Thanks!  Applied.

_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile