This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] guile: Add 'history-push!' procedure
- From: Eli Zaretskii <eliz at gnu dot org>
- To: ludo at gnu dot org (Ludovic CourtÃs)
- Cc: gdb-patches at sourceware dot org, xdje42 at gmail dot com
- Date: Wed, 19 Feb 2014 05:46:02 +0200
- Subject: Re: [PATCH] guile: Add 'history-push!' procedure
- Authentication-results: sourceware.org; auth=none
- References: <871tz06o4x dot fsf at gnu dot org>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: ludo@gnu.org (Ludovic CourtÃs)
> Date: Tue, 18 Feb 2014 23:40:14 +0100
>
> This patch adds the âhistory-push!â procedure to add a value in the
> history.
Thanks.
> +@deffn {Scheme Procedure} history-push! value
> +Push @var{value}, an instance of @code{<gdb:value>}, to @value{GDBN}'s
> +value history.
I think we should explain what "push" means in this context. It is
not self-evident.
> Return its index in the history, or @code{#f} if it is
> +not saved.
Why would it not be saved?
> +This function is useful to make it easier to access individual values
> +from a set of values displayed by a user function.
Not sure what this sentence is about. "Easier" how, and what do you
mean by "user function"?