From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Patch: add gdb.parse_and_eval
Date: Thu, 03 Dec 2009 03:51:00 -0000 [thread overview]
Message-ID: <83fx7slnsq.fsf@gnu.org> (raw)
In-Reply-To: <m3tyw9hwdn.fsf@fleche.redhat.com>
> From: Tom Tromey <tromey@redhat.com>
> Cc: gdb-patches@sourceware.org
> Date: Wed, 02 Dec 2009 14:57:40 -0700
>
> >>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
>
> >> +@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
>
> Eli> Thanks. This is okay, but given the recent discussions which
> Eli> indicated that this feature is necessary for a broad class of scripts,
> Eli> I would expect a bit more text in the manual about it, describing when
> Eli> and how this would be useful.
>
> How about this?
Fine with me, thanks.
prev parent reply other threads:[~2009-12-03 3:51 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
2009-12-02 21:57 ` Tom Tromey
2009-12-03 3:51 ` Eli Zaretskii [this message]
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=83fx7slnsq.fsf@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