Re: MI: type prefixes for values

[Vladimir Prus <ghost at cs dot msu dot su>]

On Monday 20 February 2006 21:58, Jim Ingham wrote:
> Making variable objects is always slower than just printing the
> values if you are only doing it one time.  The variable objects don't
> do any magic to get their values - they go through the same code as
> "print" does ultimately, but they do a little more work getting
> there.  The overhead is not all that great, however.  Just malloc'ing
> some data structures and inserting them into a list somewhere.
>
> The advantage of variable objects is that they cache the parsed
> expression.  So the second & third etc. evaluation is much faster.
> This is a pretty common usage pattern, especially with local
> variables, since you usually step a number of times in any given
> frame, and the locals all have to be updated with each step.  The
> variable objects have some other convenient features, like the -var-
> update command which refreshes the values will report only the
> variable objects whose values have changed, so the front end has to
> fetch less data.

Say, I've created a bunch of variable objects for for local variables. When I 
leave the function, those variables become invalid. How do you detect this 
case? Do you have a command '-list-var-objects-that-are-dead', or some other 
mechanism.

> We also added the option to return all the locals in all the blocks
> in a function.  This allows you to present all the variables, and
> then mark the ones which are not currently in scope appropriately.  I
> find this less confusing than having the contents of the variables
> window come and go as you step through the function.  Most of our
> users seem to agree.

Heck, such a feature will immediately fix:

    http://bugs.kde.org/show_bug.cgi?id=120439

Is this patch available on some branch in the public CVS repository?

- Volodya