Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [doc] improve MI varobj introduction
Date: Tue, 19 Dec 2006 22:29:00 -0000	[thread overview]
Message-ID: <17800.26295.304176.572103@kahikatea.snap.net.nz> (raw)
In-Reply-To: <200612191103.55137.vladimir@codesourcery.com>


I think it's a good idea to add this.

 > +For a leaf variable object it is possible to obtain its value as a
 > +string, or set the value from a string.  String value can be also
                                    ^^^^^^
-var-assign var1 8  <- not a string
^done,value="8"

 > +obtained for a non-leaf variable object, but its generally a string
 > +that only indicates the type of the object, and does not list its
 > +content.  Assignment to a non-leaf variable object is not allowed.
 >
 > +A frontend need not read the values of all variable objects each time
 > +the program stops.  Instead, MI provides update command that lists all
 > +variable objects which values has changed since the last update
 > +operation.  This considerably reduces the amount of data that must
 > +be transferred to the frontend.

and this:

 > +                                                   and return the
 > +list of variable object which values has changed as the result.

                                                       and return the
    list of variable object whose values have changed.

However, I'm not sure that the replaced parts of the introduction are an
improvement, or that elaborating on the PRINT-VALUES option is a good idea.

Also expanding the introduction allows the removal of the summary of commands
which just duplicates what comes after.

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2006-12-19 22:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-19  8:04 Vladimir Prus
2006-12-19 22:29 ` Nick Roberts [this message]
2006-12-20 11:47   ` Vladimir Prus
2006-12-20 20:52     ` Nick Roberts
2006-12-21  6:15       ` Vladimir Prus
2006-12-26 15:32         ` Daniel Jacobowitz
2006-12-26 15:52           ` Vladimir Prus
2006-12-26 22:38             ` Daniel Jacobowitz
2007-01-04 18:21               ` Vladimir Prus
2007-01-04 18:23               ` Vladimir Prus
2007-01-04 21:48                 ` Eli Zaretskii
2007-01-05  8:39                   ` Vladimir Prus
2007-01-05  9:26                     ` Eli Zaretskii
2007-01-08 14:50                       ` Vladimir Prus
2007-01-08 19:45                         ` Eli Zaretskii
2007-01-08 20:09                           ` Vladimir Prus
2007-01-09  4:18                             ` 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=17800.26295.304176.572103@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=gdb-patches@sources.redhat.com \
    --cc=vladimir@codesourcery.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