Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC][python] Fixes and improvements to gdb.Value.
Date: Sun, 04 Jan 2009 04:20:00 -0000	[thread overview]
Message-ID: <uk59bn1m9.fsf@gnu.org> (raw)
In-Reply-To: <1231024147.8380.166.camel@localhost.localdomain>

> From: Thiago Jung Bauermann <bauerman@br.ibm.com>
> Cc: gdb-patches@sourceware.org
> Date: Sat, 03 Jan 2009 21:09:07 -0200
> 
> In a nutshell, my answer is "no, I don't think it should". :-)

Then perhaps having an index entry "gdb.history" is not important,
either?

> If @var{number} is negative, then @value{GDBN} will take its absolute value
> and count backward from the last element (i.e., the most recent element) to
> find the value to return.  If @var{number} is zero, then @value{GDBN} will
> return the most recent element.  If the element specified by @value{number}
> doesn't exist in the value history, a @code{RuntimeError} exception will be
> raised.
> 
> What do you think?

Sounds good.

> 2009-01-03  Tom Tromey  <tromey@redhat.com>
> 
> 	* gdb.texinfo (Basic Python): Document gdb.history.

Thanks, I'm happy now.


  reply	other threads:[~2009-01-04  4:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-03  2:25 Thiago Jung Bauermann
2009-01-03  9:42 ` Eli Zaretskii
2009-01-03 23:09   ` Thiago Jung Bauermann
2009-01-04  4:20     ` Eli Zaretskii [this message]
2009-01-05 21:01     ` Tom Tromey
2009-01-29 14:16       ` Thiago Jung Bauermann
2009-02-02 13:06 [RFA][python] Fixes for existing Python code Thiago Jung Bauermann
2009-02-02 18:30 ` Tom Tromey
2009-02-04  1:01   ` [RFC][python] Fixes and improvements to gdb.Value. (was Re: [RFA][python] Fixes for existing Python code.) Thiago Jung Bauermann
2009-02-04 19:40     ` [RFC][python] Fixes and improvements to gdb.Value Tom Tromey
2009-02-04 21:57       ` Thiago Jung Bauermann

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=uk59bn1m9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=bauerman@br.ibm.com \
    --cc=gdb-patches@sourceware.org \
    /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