Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Paul Koning <paul_koning@Dell.com>
To: <pmuldoon@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [python] [patch] Add is_valid to several classes
Date: Wed, 16 Mar 2011 20:14:00 -0000	[thread overview]
Message-ID: <2153F4C3-F1FE-488F-80C7-3368B2FCDD79@Dell.com> (raw)
In-Reply-To: <m3lj0evnlt.fsf@redhat.com>


On Mar 16, 2011, at 4:04 PM, Phil Muldoon wrote:

> Paul Koning <paul_koning@Dell.com> writes:
> 
>> On Mar 16, 2011, at 12:02 PM, Phil Muldoon wrote:
>> 
>>> ...
>>> +A @code{gdb.Block} object has the following methods:
>>> +
>>> +@table @code
>>> +@defmethod Block is_valid
>>> +Returns true if the @code{gdb.Block} object is valid, false if not. A
>>> +block object can become invalid if the block it refers to doesn't
>>> +exist anymore in the inferior.  All @code{gdb.Block} methods will
>>> +throw an exception if it is invalid at the time the method is called.
>>> +This method is also made available to the Python iterator object that
>>> +@code{gdb.Block} supports via the Python method @code{iter} function.
>> 
>> The iter built-in function, or any iteration context, right?  For example, if b is a gdb.Block, you could say "for x in b:", presumably, and then "x.is_valid()" works.
> 
> Yep, all iteration contexts that are valid with Python.

So how about this wording:
   This method is also made available to the Python iterator object that @code{gdb.Block} provides in iteration context and via the Python @code{iter} built-in function.

	paul


  reply	other threads:[~2011-03-16 20:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-16 16:46 Phil Muldoon
2011-03-16 17:32 ` Tom Tromey
2011-03-17 12:19   ` Phil Muldoon
2011-03-16 19:26 ` Eli Zaretskii
2011-03-16 19:59   ` Paul Koning
2011-03-16 20:06     ` Phil Muldoon
2011-03-16 20:04   ` Phil Muldoon
2011-03-16 20:13     ` Eli Zaretskii
2011-03-16 21:50       ` Phil Muldoon
2011-03-16 20:02 ` Paul Koning
2011-03-16 20:08   ` Phil Muldoon
2011-03-16 20:14     ` Paul Koning [this message]
2011-03-16 22:01       ` Phil Muldoon
2011-03-16 23:54       ` Eli Zaretskii

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=2153F4C3-F1FE-488F-80C7-3368B2FCDD79@Dell.com \
    --to=paul_koning@dell.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pmuldoon@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