This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Patch: add gdb.parse_and_eval
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Thu, 03 Dec 2009 05:49:25 +0200
- Subject: Re: Patch: add gdb.parse_and_eval
- References: <m3y6rybinn.fsf@fleche.redhat.com> <E1MEswD-0002x8-5c@fencepost.gnu.org> <m3tyw9hwdn.fsf@fleche.redhat.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> 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.