This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: New scope checking patch
- From: Tom Tromey <tromey at redhat dot com>
- To: "Rob Quill" <rob dot quill at gmail dot com>
- Cc: "Eli Zaretskii" <eliz at gnu dot org>, "Jim Blandy" <jimb at red-bean dot com>, gdb-patches at sourceware dot org
- Date: Tue, 29 Jul 2008 14:31:22 -0600
- Subject: Re: New scope checking patch
- References: <baf6008d0711120829l3c0201aakf477dd4d6cfd440e@mail.gmail.com> <m3hchcm7x5.fsf@codesourcery.com> <baf6008d0801171935s225a9dd2q664953b53bc68401@mail.gmail.com> <m3r6gf6kcz.fsf@codesourcery.com> <baf6008d0801181443s5321e5d5ud1c935aa8487a549@mail.gmail.com> <m34pda7ira.fsf@codesourcery.com> <baf6008d0801300405i47646b05pdb799d32ab71e005@mail.gmail.com> <u1w7zxjid.fsf@gnu.org> <8f2776cb0801301557t2e265b62u56d6df7cbcec1c84@mail.gmail.com> <utzkuws6q.fsf@gnu.org> <baf6008d0807271645o7d03dd94rd5b3f0d08302085a@mail.gmail.com>
- Reply-to: tromey at redhat dot com
>>>>> "Rob" == Rob Quill <rob.quill@gmail.com> writes:
Rob> 2008-07-27 Rob Quill <rob.quill@gmail.com>
Rob> Add $in_scope as a type of expression.
This seems like a good candidate for an internal function. The syntax
is nearly identical.
The only difference is that, at the GCC Summit, we agreed that
arguments to internal functions would be expressions. So, instead of
$in_scope(x) you would have to write $in_scope("x").
Internal functions are only in the python repository right now. The
patch consists of two parts: an internals-only part, and the part that
exposes the functionality to the Python layer.
I think we can submit the internals part as a separate patch. AFAIK
the only reason we haven't is just that there's been no need for it
outside the Python work.
Tom