From: Siva Chandra <sivachandra@google.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC - Python Scripting] New method gdb.Symtab.blocks_iterator - docs included
Date: Wed, 11 Apr 2012 04:59:00 -0000 [thread overview]
Message-ID: <CAGyQ6gzJMgTzvayD+2=WjiJpL75PU-Ht4FqzBANC_9s1tmwmkw@mail.gmail.com> (raw)
In-Reply-To: <87398b4582.fsf@fleche.redhat.com>
Tom> I think it would be a bit more future-proof to just let the user access
Tom> the symtab's global and static blocks, then rely on iteration over
Tom> symbols within a block. This would mean also adding a way to fetch a
Tom> block's subblocks.
To begin with then, can I remove the idea of this iterator (and the
blocks method) and add two methods global_block and static_block?
Thanks,
Siva Chandra
next prev parent reply other threads:[~2012-04-11 4:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 18:34 Siva Chandra
2012-04-09 20:47 ` Eli Zaretskii
2012-04-10 1:38 ` Tom Tromey
2012-04-10 7:45 ` Siva Chandra
2012-04-10 17:16 ` Doug Evans
2012-04-10 22:21 ` Tom Tromey
2012-04-11 4:59 ` Siva Chandra [this message]
2012-04-11 5:44 ` Doug Evans
2012-04-12 15:20 ` 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='CAGyQ6gzJMgTzvayD+2=WjiJpL75PU-Ht4FqzBANC_9s1tmwmkw@mail.gmail.com' \
--to=sivachandra@google.com \
--cc=gdb-patches@sourceware.org \
--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