Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Siva Chandra <sivachandra@google.com>
Cc: Tom Tromey <tromey@redhat.com>,
	Phil Muldoon <pmuldoon@redhat.com>, Eli Zaretskii <eliz@gnu.org>,
		gdb-patches@sourceware.org
Subject: Re: [RFC - Python scripting] New methods Symtab.global_block and Symtab.static_block (docs included)
Date: Thu, 19 Apr 2012 19:18:00 -0000	[thread overview]
Message-ID: <CADPb22TvvQDSA1EL4ydoZRGkKBm1kTCGcHyB2dc3X28p8XqyAg@mail.gmail.com> (raw)
In-Reply-To: <CAGyQ6gzC_2hZfhBv4SQNGVem0bOLxMp+02Nmy=iwPtqNE=J8kg@mail.gmail.com>

On Thu, Apr 19, 2012 at 10:29 AM, Siva Chandra <sivachandra@google.com> wrote:
> Phil> FWIW, I would still like to see a clarification of the static/global
> Phil> documentation regarding the "this might change" comment.  Sorry to be
> Phil> a stickler on this, but I think it is important we don't start hinting
> Phil> at API breakages without an adequate explanation as to what may
> Phil> change, and why.  (Given that there is a need to put that disclaimer
> Phil> in there in the first place).
>
> Tom> I agree this text is a bit on the terse side.
> Tom>
> Tom> An issue I see with it is that, as a Python developer, you can't take
> Tom> any action to insulate yourself.  Perhaps being more specific about what
> Tom> "identical" means would be useful.
>
> OK. I will wait for Doug to clarify on this.
>
> /Siva Chandra

It would not be unexpected to me if a symbol disappeared from either
list, moved from one list to another, or a new symbol appeared.

[I also think exposing "global" vs "static" is an implementation
detail, and thus shouldn't be part of the API, akin to exposing symbol
table file names - symbols can have file names (like they have line
numbers), but symbol tables I'm less comfortable with.  Both of those
ships have already sailed, I know.]


  reply	other threads:[~2012-04-19 17:37 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-17  8:39 Siva Chandra
2012-04-17 13:00 ` Phil Muldoon
2012-04-17 17:34   ` Siva Chandra
2012-04-17 17:44     ` Tom Tromey
2012-04-17 17:41   ` Tom Tromey
2012-04-17 17:05 ` Eli Zaretskii
     [not found]   ` <CAGyQ6gxxEeYeCKw_iHXh74Gg223GHxMoW=gvt9kU+ax396kKBQ@mail.gmail.com>
2012-04-18  9:15     ` Siva Chandra
2012-04-18 20:45       ` Phil Muldoon
2012-04-18 20:48         ` Tom Tromey
2012-04-19 17:33           ` Siva Chandra
2012-04-19 19:18             ` Doug Evans [this message]
2012-04-20  6:48               ` Siva Chandra
2012-04-20 12:12                 ` Matt Rice
2012-04-20 14:16                   ` Doug Evans
2012-04-20 15:21                   ` Matt Rice
2012-04-20 19:12                   ` Tom Tromey
2012-04-20 19:53                     ` Doug Evans
2012-04-20 19:57                       ` Siva Chandra
2012-04-23 13:21                         ` Tom Tromey
2012-04-23 13:35                           ` Phil Muldoon
2012-04-23 14:11                             ` Eli Zaretskii
2012-04-23 14:45                               ` Phil Muldoon
2012-04-23 16:00                                 ` Eli Zaretskii
2012-04-24 11:15                                   ` Siva Chandra
2012-04-24 17:40                                     ` Eli Zaretskii
2012-04-25  7:11                                   ` Tom Tromey
2012-04-25  8:19                                     ` Siva Chandra
2012-04-26 12:35                                     ` Siva Chandra
2012-04-26 15:21                                       ` Doug Evans
2012-05-02 17:41                                         ` Siva Chandra
2012-05-02 18:15                                           ` Doug Evans
2012-05-03  7:13                                             ` Siva Chandra
2012-05-04 18:05                                               ` FAILing new testcase for -fdebug-types-section [Re: [RFC - Python scripting] New methods Symtab.global_block and Symtab.static_block (docs included)] Jan Kratochvil
2012-05-05  7:01                                                 ` Siva Chandra
2012-05-05  7:05                                                   ` Jan Kratochvil
2012-05-05  7:11                                                     ` Siva Chandra
2012-05-05  7:13                                                       ` Jan Kratochvil
2012-05-23 21:38                                                         ` [patch KFAIL] Re: FAILing new testcase for -fdebug-types-section (PR symtab/14148) Jan Kratochvil
2012-04-18 20:48       ` [RFC - Python scripting] New methods Symtab.global_block and Symtab.static_block (docs included) Tom Tromey
2012-04-20  8:13       ` Eli Zaretskii
2012-04-17 17:37 ` Tom Tromey
2012-04-18 18:41   ` Tom Tromey
2012-04-18 19:53     ` Siva Chandra
2012-04-18 20:49       ` Tom Tromey

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=CADPb22TvvQDSA1EL4ydoZRGkKBm1kTCGcHyB2dc3X28p8XqyAg@mail.gmail.com \
    --to=dje@google.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pmuldoon@redhat.com \
    --cc=sivachandra@google.com \
    --cc=tromey@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