From: Daniel Jacobowitz <drow@false.org>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb-patches@sourceware.org
Subject: Re: Python pretty-printing [3/6]
Date: Tue, 07 Apr 2009 02:27:00 -0000 [thread overview]
Message-ID: <20090407022652.GA18291@caradoc.them.org> (raw)
In-Reply-To: <1239069822.8871.74.camel@localhost.localdomain>
On Mon, Apr 06, 2009 at 11:03:42PM -0300, Thiago Jung Bauermann wrote:
> El lun, 06-04-2009 a las 21:16 -0400, Daniel Jacobowitz escribió:
> > On Mon, Apr 06, 2009 at 05:26:06PM -0600, Tom Tromey wrote:
> > At some point I know we'll want explicit lookup routines; there's
> > scope to consider.
>
> For scope specification and definition, I have created a gdb.Block class
> in the python branch. I'm not sure if you had a look at it. Is there any
> other way that scope could be defined?
Types are usually not block scoped, at least, I can't think of any
language where that's allowed, but it's adequate since they can be
function scoped. They can also be source file scoped, or you could
look up a type by name in an objfile or globally. Linkage of types is
not as well defined as for symbols.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-04-07 2:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 20:55 Tom Tromey
2009-04-03 15:16 ` Eli Zaretskii
2009-04-07 19:52 ` Tom Tromey
2009-04-07 21:45 ` Eli Zaretskii
2009-04-03 16:30 ` Daniel Jacobowitz
2009-04-06 23:26 ` Tom Tromey
2009-04-07 0:34 ` Thiago Jung Bauermann
2009-04-07 1:16 ` Daniel Jacobowitz
2009-04-07 2:03 ` Thiago Jung Bauermann
2009-04-07 2:27 ` Daniel Jacobowitz [this message]
2009-04-03 20:34 ` Thiago Jung Bauermann
2009-04-06 23:32 ` Tom Tromey
2009-04-08 18:26 ` Tom Tromey
2009-04-08 18:39 ` Tom Tromey
2009-04-08 19:23 ` Eli Zaretskii
2009-04-09 1:16 ` 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=20090407022652.GA18291@caradoc.them.org \
--to=drow@false.org \
--cc=bauerman@br.ibm.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