Re: [PATCH 0/7] Handle nested functions in DAP

[Tom Tromey <tromey@adacore.com>]

>>>>> "Tom" == Tom Tromey <tromey@adacore.com> writes:

Tom> DAP doesn't really describe what to do for nested functions.  We
Tom> discussed it internally a little, and I came up with this series.  The
Tom> idea here is that variables from the outer scope ought to be visible,
Tom> so this series lets Python code follow a frame's static link, and then
Tom> changes the DAP frame decorators to use this ability.

I'm going to check this in.

I'm also going to backport it to gdb-14, since it is a change for DAP;
and the generic changes should be pretty harmless.

Tom> At some point I think we'll need a "frame decorator v2", like we added
Tom> for pretty-printers.  But, I've been putting this off a little and
Tom> still haven't done it here.

I think this is a bit trickier than it first appears, because frame
filters not only generate objects that conform to the decorator API --
they also use them.

So I'm not sure what to do, if the need really arises.  Maybe we need to
break the API a little.

Tom