From: Phil Muldoon <pmuldoon@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [python][patch] And range method to type
Date: Fri, 04 Dec 2009 17:10:00 -0000 [thread overview]
Message-ID: <4B194271.1060908@redhat.com> (raw)
In-Reply-To: <834oo6lppw.fsf@gnu.org>
On 12/04/2009 03:32 PM, Eli Zaretskii wrote:
>> Date: Fri, 04 Dec 2009 15:25:16 +0000
>> From: Phil Muldoon <pmuldoon@redhat.com>
>>
>> This patch adds a "range" method for GDB.Types. It only supports types
>> that support a range, or the range type itself.
>>
>> Ok?
>
> A couple of comments to the doco part:
>
>> +@defmethod Type range
>> +Return a Python @code{Tuple} object that contains two elements. The
>> +first element of the @code{Tuple} contains the low bound of the type; the
>> +second element contains the high bound of the type.
+@defmethod Type range
+Return a Python @code{Tuple} object that contains two elements: the
+low bound of the argument type and the high bound of that type. If the
+type does not have a range, @value{GDBN} will raise a @code{RuntimeError}.
+@end defmethod
With your suggestions, adding the missing full-stop and changing "throw" to "raise"
in the exception case, is this ok?
Cheers,
Phil
next prev parent reply other threads:[~2009-12-04 17:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-04 15:25 Phil Muldoon
2009-12-04 15:32 ` Eli Zaretskii
2009-12-04 17:10 ` Phil Muldoon [this message]
2009-12-04 19:30 ` Eli Zaretskii
2009-12-04 17:19 ` Joel Brobecker
2009-12-04 18:13 ` Tom Tromey
2009-12-05 9:19 ` Phil Muldoon
2009-12-05 9:22 ` Eli Zaretskii
2009-12-07 19:54 ` Tom Tromey
2009-12-08 14:14 ` Phil Muldoon
2009-12-09 3:00 ` Hui Zhu
2009-12-09 7:47 ` Phil Muldoon
2009-12-09 11:27 ` Eli Zaretskii
2009-12-09 11:41 ` Andreas Schwab
2009-12-09 7:52 ` Phil Muldoon
2009-12-09 7:56 ` Hui Zhu
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=4B194271.1060908@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