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: tromey at redhat dot com
- Cc: gdb-patches at sourceware dot org
- Date: Thu, 11 Jun 2009 18:40:01 -0400
- Subject: Re: Patch: add gdb.parse_and_eval
- References: <m3y6rybinn.fsf@fleche.redhat.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> 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