Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: tromey@redhat.com
Cc: gdb-patches@sourceware.org
Subject: Re: Patch: add gdb.parse_and_eval
Date: Thu, 11 Jun 2009 22:40:00 -0000	[thread overview]
Message-ID: <E1MEswD-0002x8-5c@fencepost.gnu.org> (raw)
In-Reply-To: <m3y6rybinn.fsf@fleche.redhat.com> (message from Tom Tromey on 	Thu, 11 Jun 2009 14:49:16 -0600)

> From: Tom Tromey <tromey@redhat.com>
> Reply-To: tromey@redhat.com
> Date: Thu, 11 Jun 2009 14:49:16 -0600
> 
> +@findex gdb.parse_and_eval
> +@defun parse_and_eval expression
> +Parse @var{expression} as an expression in the current language,
> +evaluate it, and return the result as a @code{gdb.Value}.
> +@var{expression} must be a string.
> +@end defun

Thanks.  This is okay, but given the recent discussions which
indicated that this feature is necessary for a broad class of scripts,
I would expect a bit more text in the manual about it, describing when
and how this would be useful.

The user manual is not just a reference list of existing commands and
options.  It contains, in addition, the glue: explanations of how
these features fit together to support important use-cases one meets
while debugging programs.  Without this glue, the manual would be a
much less useful document.

TIA


  reply	other threads:[~2009-06-11 22:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-11 20:49 Tom Tromey
2009-06-11 22:40 ` Eli Zaretskii [this message]
2009-12-02 21:57   ` Tom Tromey
2009-12-03  3:51     ` 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=E1MEswD-0002x8-5c@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@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