* gdbint.texinfo (User Interface): Mention add_setshow_cmd and

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index bec2067..5305dab 100644 (file)
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,8 @@
+2002-06-26  Tom Tromey  <tromey@redhat.com>
+
+       * gdbint.texinfo (User Interface): Mention add_setshow_cmd and
+       add_setshow_cmd_full.
+
 2002-06-25  Don Howard  <dhoward@redhat.com>
 
        * gdb.texinfo (Memory Region Attributes): Document new behavior

diff --git a/gdb/doc/gdbint.texinfo b/gdb/doc/gdbint.texinfo
index bb787a2..b3cfefb 100644 (file)
--- a/gdb/doc/gdbint.texinfo
+++ b/gdb/doc/gdbint.texinfo
@@ -50,7 +50,7 @@ Software Foundation raise funds for GNU development.''
 @end tex
 
 @vskip 0pt plus 1filll
-Copyright @copyright{} 1990,1991,1992,1993,1994,1996,1998,1999,2000,2001
+Copyright @copyright{} 1990,1991,1992,1993,1994,1996,1998,1999,2000,2001, 2002
    Free Software Foundation, Inc.
 
 Permission is granted to copy, distribute and/or modify this document
@@ -722,6 +722,14 @@ the main command list, and should be used for those commands.  The usual
 place to add commands is in the @code{_initialize_@var{xyz}} routines at
 the ends of most source files.
 
+@findex add_setshow_cmd
+@findex add_setshow_cmd_full
+To add paired @samp{set} and @samp{show} commands, use
+@code{add_setshow_cmd} or @code{add_setshow_cmd_full}.  The former is
+a slightly simpler interface which is useful when you don't need to
+further modify the new command structures, while the latter returns
+the new command structures for manipulation.
+
 @cindex deprecating commands
 @findex deprecate_cmd
 Before removing commands from the command set it is a good idea to