This is the mail archive of the
mailing list for the Archer project.
Re: Method to retrieve a type's objfile, and an objfile's global scope
- From: Tom Tromey <tromey at redhat dot com>
- To: Jim Blandy <jimb at red-bean dot com>
- Cc: Project Archer <archer at sourceware dot org>
- Date: Fri, 24 Jul 2009 17:01:57 -0600
- Subject: Re: Method to retrieve a type's objfile, and an objfile's global scope
- References: <email@example.com>
- Reply-to: Tom Tromey <tromey at redhat dot com>
>>>>> "Jim" == Jim Blandy <firstname.lastname@example.org> writes:
Jim> One solution would be to provide access to a type's objfile, and then
Jim> to an objfile's global scope --- or perhaps more directly, simply
Jim> provide a function that returns the scope in which a type is defined.
Yeah, I think we need something like this.
There are a few places where we should pass in some optional things to
modify type lookup: a block (or other sort of scope or scope proxy), an
arch, and a language. Basically most occurrences of python_gdbarch and
python_language are bugs. In this case, the ones in typy_lookup_typename.
I think archer already has some of the block stuff done. I'm on another
branch right now, so it isn't convenient to check.
If you can't do this, please file a bug against archer.
I'd like us to be a bit more systematic about this; now is a good time
to start :-)