From: Eli Zaretskii <eliz@gnu.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: bob@brasko.net, gdb-patches@sources.redhat.com
Subject: Re: [PATCH: gdb/mi + doco] -var-update
Date: Mon, 04 Jul 2005 22:24:00 -0000 [thread overview]
Message-ID: <ubr5ip33y.fsf@gnu.org> (raw)
In-Reply-To: <17097.42837.514419.9496@farnswood.snap.net.nz> (message from Nick Roberts on Tue, 5 Jul 2005 09:17:09 +1200)
> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Tue, 5 Jul 2005 09:17:09 +1200
> Cc: Bob Rossi <bob@brasko.net>, gdb-patches@sources.redhat.com
>
> I've changed the English slightly from last time, and because
> "-var-list-children" and "-var-update" have the same optional argument, I only
> describe it explictly once. "-stack-list-locals" is slightly different
> because print-values is not optional and "--print-simple-values" prints the
> type also.
>
> I've also corrected a spelling and made a couple of changes to the
> GDB/MI command description format to reflect reality.
Thanks.
Allow me a few comments:
> +Display the local variable names for the current frame. A value for
> +@var{print-values} of 0 or @code{--no-values}, prints only the names
> +of the variables; a value of 1 or @code{--all-values}, prints also
> +their values; and a value of 2 or @code{--simple-values}, prints the
> +name, type and value for simple data types and the name and type for
> +arrays, structures and unions.
It would be much simpler to rephrase like this:
Display the local variable names for the current frame. If
@var{print-values} is 0 or @code{--no-values}, print only the names
of the variables; if it is 1 or @code{--all-values}, print their
values as well; if it is 2 or @code{--simple-values}, print ...
you get the point. Note that I also changed "prints" -> "print",
since the sentence before that says "Display", not "Displays".
> +In this last case, the idea is that
> +the user can see the value of simple data types immediately and he can
> +create variable objects for other data types if he wishes to explore
> +their values in more detail.
I think the GNU project's convention is not to use "he" where "she" is
also possible.
> +Returns a list of the children of the specified variable object. A
> +single argument or an optional value for @var{print-values} of 0 or
> +@code{--no-values}, prints only the names of the variables; a value
> +for @var{print-values} of 1 or @code{--all-values}, also prints their
> +values; and a value of 2 or @code{--simple-values} prints the name and
> +value for simple data types and just the name for arrays, structures
> +and unions.
This could also use similar rephrasing.
> -A @samp{*} causes all existing variable objects to be updated.
> +A @samp{*} causes all existing variable objects to be updated.
These two lines are identical, except that the second one has 2
trailing blanks. Please remove those blanks.
> +The option @var{print-values} determines whether names and values, or
> +just names are printed in the manner described for @code{-var-list-children}.
Please add a cross-reference here that points to the description of
"-var-list-children". (Since the commands don't have each one its own
node, you will have to use @anchor to create a point-able place for
the xref.)
next prev parent reply other threads:[~2005-07-04 22:24 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-20 2:06 Nick Roberts
2005-02-20 5:02 ` Eli Zaretskii
2005-02-20 5:51 ` Nick Roberts
2005-02-20 15:31 ` Eli Zaretskii
2005-02-21 4:33 ` Nick Roberts
2005-02-21 7:17 ` Eli Zaretskii
2005-02-22 9:23 ` Nick Roberts
2005-02-22 9:34 ` Eli Zaretskii
2005-02-27 5:03 ` Nick Roberts
2005-02-27 16:53 ` Eli Zaretskii
2005-02-27 16:56 ` Nick Roberts
2005-02-28 12:27 ` Eli Zaretskii
2005-03-19 3:55 ` Nick Roberts
2005-04-01 1:51 ` Bob Rossi
2005-04-01 11:01 ` Nick Roberts
2005-05-02 2:06 ` Nick Roberts
2005-05-02 4:05 ` Daniel Jacobowitz
2005-05-02 7:24 ` Nick Roberts
2005-06-17 3:43 ` Daniel Jacobowitz
2005-06-17 10:09 ` Eli Zaretskii
2005-06-17 14:04 ` Daniel Jacobowitz
2005-06-18 8:53 ` Eli Zaretskii
2005-07-03 19:56 ` Daniel Jacobowitz
2005-07-04 3:07 ` Nick Roberts
2005-07-04 3:51 ` Daniel Jacobowitz
2005-07-04 4:55 ` Eli Zaretskii
2005-07-04 5:02 ` Daniel Jacobowitz
2005-07-04 10:17 ` Nick Roberts
2005-07-06 10:00 ` Nick Roberts
2005-07-15 1:44 ` Daniel Jacobowitz
2005-07-15 3:59 ` Nick Roberts
2005-07-15 4:16 ` Daniel Jacobowitz
2005-07-15 15:11 ` Nick Roberts
2005-07-15 15:28 ` Daniel Jacobowitz
2005-07-15 22:37 ` Nick Roberts
2005-07-04 21:15 ` Nick Roberts
2005-07-04 22:24 ` Eli Zaretskii [this message]
2005-07-05 3:25 ` Nick Roberts
2005-07-05 19:37 ` Eli Zaretskii
2005-07-15 9:42 ` Nick Roberts
2005-06-17 11:42 ` Nick Roberts
2005-06-17 14:06 ` Daniel Jacobowitz
2005-06-17 23:12 ` Nick Roberts
2005-02-21 2:36 ` Andrew Cagney
2005-02-21 3:28 ` Nick Roberts
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=ubr5ip33y.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bob@brasko.net \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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