From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb-patches@sources.redhat.com
Subject: Re: -var-info-path-expression
Date: Fri, 31 Aug 2007 09:08:00 -0000 [thread overview]
Message-ID: <u8x7s137t.fsf@gnu.org> (raw)
In-Reply-To: <E1IQ4g5-00081E-EP@zigzag.lvk.cs.msu.su> (message from Vladimir Prus on Tue, 28 Aug 2007 21:16:33 +0400)
> From: Vladimir Prus <ghost@cs.msu.su>
> Date: Tue, 28 Aug 2007 21:16:33 +0400
>
> Vladimir Prus wrote:
>
> >
> > This is the hopefully final revision of the patch
> > to add the -var-info-path-expression command.
> > The code part of the patch was already approved in:
> >
> > http://article.gmane.org/gmane.comp.gdb.patches/34902
> [...]
> > Eli, do doc changes look fine?
Here are my comments:
> +Returns the expression that is represented by the variable object
> +@var{name}, that is relative to parent variable object and is
> +suitable for presenting this variable object is user interface:
^^
That "is" looks like a typo. Did you mean "in", perhaps?
> +@smallexample
> + -var-info-path-expression @var{name}
> +@end smallexample
> +
> +Returns a full expression that can be evaluated in the current
> +context and corresponds to the variable object. Unlike the
> +@code{-var-info-expression} command, the returned expression is not relative
> +to parent and can be used to create another variable object that will
> +always have the same value as the other variable object. Typical
> +use of @code{-var-info-path-expression} is creating a watchpoint from
> +a variable object.
> +
> +Example output:
> @smallexample
> lang=@var{lang-spec},exp=@var{expression}
> @end smallexample
I'd like to improve the documentation of -var-info-path-expression and
-var-info-expression, such that the difference between them is clearly
explained. Right now, having read the documentation of both of them,
I am confused about how they differ. What does it mean, exactly,
"expression represented by the variable object", and what does it mean
"relative to parent variable object"? The examples don't help,
either, because they are identical.
How about if you write a real-life example of the output generated by
both commands (i.e. with real expressions, not @var{something}), and
place both of the examples in each section to show how the two
commands differ? Alternatively, have only one example in each
section, and point to the other, as in "Contrast this with the output
generated by -var-info-path-expression below."
> --- gdb/doc/gdb.texinfo (revision 4579)
> +++ gdb/doc/gdb.texinfo (local)
Why there are two patches for gdb.texinfo?
next prev parent reply other threads:[~2007-08-31 9:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 11:23 -var-info-path-expression Vladimir Prus
2007-08-22 15:28 ` -var-info-path-expression Daniel Jacobowitz
2007-08-28 17:18 ` -var-info-path-expression Vladimir Prus
2007-08-28 19:55 ` -var-info-path-expression Eli Zaretskii
2007-08-31 9:08 ` Eli Zaretskii [this message]
2007-08-31 9:57 ` -var-info-path-expression Vladimir Prus
2007-08-31 18:04 ` -var-info-path-expression Eli Zaretskii
2007-08-31 18:53 ` -var-info-path-expression Vladimir Prus
2007-09-01 7:56 ` -var-info-path-expression Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2007-06-18 10:43 -var-info-path-expression Vladimir Prus
2007-06-18 19:40 ` -var-info-path-expression Eli Zaretskii
2007-06-21 5:15 ` -var-info-path-expression Vladimir Prus
2007-07-03 17:14 ` -var-info-path-expression Daniel Jacobowitz
2007-07-03 17:51 ` -var-info-path-expression Vladimir Prus
2007-07-03 17:58 ` -var-info-path-expression Daniel Jacobowitz
2006-12-25 9:02 -var-info-path-expression Vladimir Prus
2007-01-03 22:39 ` -var-info-path-expression Daniel Jacobowitz
2007-01-05 9:14 ` -var-info-path-expression Vladimir Prus
2007-01-27 21:49 ` -var-info-path-expression Vladimir Prus
2007-01-28 0:46 ` -var-info-path-expression Nick Roberts
2007-01-28 7:57 ` -var-info-path-expression Vladimir Prus
2007-01-28 8:35 ` -var-info-path-expression Nick Roberts
2007-01-29 10:53 ` -var-info-path-expression Vladimir Prus
2007-01-29 12:17 ` -var-info-path-expression Daniel Jacobowitz
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=u8x7s137t.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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