Re: [python] [patch] Add is_valid to several classes

[Phil Muldoon <pmuldoon@redhat.com>]

Paul Koning <paul_koning@Dell.com> writes:

> 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

That's fine with me.  If Eli approves it, I will place it in the manual
text.

Cheers

Phil