Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: pmuldoon@redhat.com
Cc: gdb-patches@sourceware.org
Subject: Re: [python] [patch] PR python/12656 (API for special blocks)
Date: Mon, 10 Oct 2011 18:27:00 -0000	[thread overview]
Message-ID: <m3ipnwbt3k.fsf@fleche.redhat.com> (raw)
In-Reply-To: <m34nzhchro.fsf@redhat.com> (Phil Muldoon's message of "Mon, 10	Oct 2011 10:34:03 +0100")

>>>>> "Phil" == Phil Muldoon <pmuldoon@redhat.com> writes:

Phil> +@defun Block.is_global ()
Phil> +@defun Block.is_static ()

Tom> Why are these methods rather than attributes?

Phil> Because is_valid is a method in py-block.c, and I decided to continue
Phil> the is_* APIs to be methods.  It confuses my *why* is_valid is a method
Phil> over an attribute, too.

Just history.

I think these should be attributes.  Value.is_optimized_out is one.
Symbol has various is_* attributes.

Tom


  reply	other threads:[~2011-10-10 18:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-07 17:02 Phil Muldoon
2011-10-07 20:41 ` Tom Tromey
2011-10-10  9:34   ` Phil Muldoon
2011-10-10 18:27     ` Tom Tromey [this message]
2011-10-11 16:00       ` Phil Muldoon
     [not found]         ` <09787EF419216C41A903FD14EE5506DD030BEC56DF@AUSX7MCPC103.AMER.DELL.COM>
2011-10-11 16:06           ` Paul Koning
2011-10-11 18:32             ` Phil Muldoon
2011-10-11 17:30         ` Tom Tromey
2011-10-17 10:59           ` Phil Muldoon
2011-10-17 11:57             ` Eli Zaretskii
2011-10-17 12:49               ` Phil Muldoon
2011-10-17 15:07                 ` Eli Zaretskii
2011-10-20 12:58                   ` Phil Muldoon

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=m3ipnwbt3k.fsf@fleche.redhat.com \
    --to=tromey@redhat.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