Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb-patches@sources.redhat.com
Subject: MI docs: remove historic note
Date: Wed, 15 Nov 2006 14:38:00 -0000	[thread overview]
Message-ID: <200611151735.25903.vladimir@codesourcery.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 564 bytes --]


The section of manual that talks about MI variable objects starts by some
texts that looks more like email message than documentation, and does not 
say anything important. I recall I was absolutely buffled when I first saw 
this section. It seems this section appeared there historically, but no 
longer is needed.

This patch removes that text. Now section on variable object starts with 
explanation what is variable object -- which looks quite reasonable.

OK?

- Volodya

        * gdb.texinfo (Motivation for Variable Objects in GDB/MI): 
        Remove.



[-- Attachment #2: remove_historic_note__gdb_mainline.diff --]
[-- Type: text/x-diff, Size: 1524 bytes --]

=== gdb/doc/gdb.texinfo
==================================================================
--- gdb/doc/gdb.texinfo	(/mirrors/gdb_mainline)	(revision 2104)
+++ gdb/doc/gdb.texinfo	(/patches/gdb/remove_historic_note/gdb_mainline)	(revision 2104)
@@ -19482,40 +19482,6 @@
 @node GDB/MI Variable Objects
 @section @sc{gdb/mi} Variable Objects
 
-
-@subheading Motivation for Variable Objects in @sc{gdb/mi}
-
-For the implementation of a variable debugger window (locals, watched
-expressions, etc.), we are proposing the adaptation of the existing code
-used by @code{Insight}.
-
-The two main reasons for that are:
-
-@enumerate 1
-@item
-It has been proven in practice (it is already on its second generation).
-
-@item
-It will shorten development time (needless to say how important it is
-now).
-@end enumerate
-
-The original interface was designed to be used by Tcl code, so it was
-slightly changed so it could be used through @sc{gdb/mi}.  This section
-describes the @sc{gdb/mi} operations that will be available and gives some
-hints about their use.
-
-@emph{Note}: In addition to the set of operations described here, we
-expect the @sc{gui} implementation of a variable window to require, at
-least, the following operations:
-
-@itemize @bullet
-@item @code{-gdb-show} @code{output-radix}
-@item @code{-stack-list-arguments}
-@item @code{-stack-list-locals}
-@item @code{-stack-select-frame}
-@end itemize
-
 @subheading Introduction to Variable Objects in @sc{gdb/mi}
 
 @cindex variable objects in @sc{gdb/mi}

             reply	other threads:[~2006-11-15 14:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-15 14:38 Vladimir Prus [this message]
2006-11-15 18:23 ` Eli Zaretskii
2006-11-29 15:54   ` Vladimir Prus
2006-11-29 18:44     ` Eli Zaretskii
2006-11-29 18:58       ` Vladimir Prus
2006-11-29 19:11         ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200611151735.25903.vladimir@codesourcery.com \
    --to=vladimir@codesourcery.com \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox