From: Phil Muldoon <pmuldoon@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [python] [patch] Add is_valid to several classes
Date: Wed, 16 Mar 2011 21:50:00 -0000 [thread overview]
Message-ID: <m3fwqmvn6y.fsf@redhat.com> (raw)
In-Reply-To: <83oc5aq17q.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 16 Mar 2011 22:06:49 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Phil Muldoon <pmuldoon@redhat.com>
>> Cc: gdb-patches@sourceware.org
>> Date: Wed, 16 Mar 2011 20:02:13 +0000
>>
>> >> +@code{gdb.Block} supports via the Python method @code{iter} function.
>> >
>> > Did you really mean to say "Python method `iter' function"? I think
>> > either "method" or "function", no?
>>
>> iter() is a built in Python function (nothing to do with GDB), that
>> extracts an iterator from a Python object if the object supports it. I
>> don't mind how we word it. It was purely illustrative. In fact in
>> Python there are many ways to invoke iteration in an object that
>> supports it. The "in" keyword for example (IE, for x in y).
>> What do you think?
>
> How about
>
> @code{gdb.Block} supports via the Python method @code{iter}.
>
> ? Is that accurate?
Paul's wording seems like a super-set of the above. That seems to work
for me, does it for you?
Cheers
Phil
next prev parent reply other threads:[~2011-03-16 20:13 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 [this message]
2011-03-16 20:02 ` Paul Koning
2011-03-16 20:08 ` Phil Muldoon
2011-03-16 20:14 ` Paul Koning
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=m3fwqmvn6y.fsf@redhat.com \
--to=pmuldoon@redhat.com \
--cc=eliz@gnu.org \
--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