Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Phil Muldoon <pmuldoon@redhat.com>
To: Paul Koning <paul_koning@Dell.com>
Cc: Eli Zaretskii <eliz@gnu.org>, <gdb-patches@sourceware.org>
Subject: Re: [python] [patch] Add is_valid to several classes
Date: Wed, 16 Mar 2011 20:06:00 -0000	[thread overview]
Message-ID: <m3pqpqvno2.fsf@redhat.com> (raw)
In-Reply-To: <335A57D4-8F8C-4D2D-A909-334C02E9475B@dell.com> (Paul Koning's	message of "Wed, 16 Mar 2011 15:26:08 -0400")

Paul Koning <paul_koning@Dell.com> writes:

> On Mar 16, 2011, at 3:22 PM, Eli Zaretskii wrote:
>
>>> From: Phil Muldoon <pmuldoon@redhat.com>
>>> Date: Wed, 16 Mar 2011 16:02:44 +0000
>>> ...
>> 
>>> +@defmethod Inferior is_valid
>>> +Returns true if the @code{gdb.Inferior} object is valid, false if
>>           ^^^^                                             ^^^^^
>> You mean @code{true} and @code{false}, right?  These are Python
>> symbols, aren't they?
>
> Actually, the Python symbols are @code{True} and @code{False} (first letter uppercase).  It would make sense to write it that way whenever the Python bool values are referenced.

Thanks to you both for catching this, and to Paul for noting the Python
notation.

Cheers

Phil


  reply	other threads:[~2011-03-16 20:03 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 [this message]
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
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=m3pqpqvno2.fsf@redhat.com \
    --to=pmuldoon@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=paul_koning@Dell.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