Re: Patch: implement new dynamic varobj spec

Nick Roberts
2009-09-11T23:55:47Z

> Nick> 1) Children are reported (and presumably created) in var-update
> Nick> even though only a root variable object may have been created,
> Nick> i.e., not -var-list-children has been invoked.
>
> It should only report children if you previously requested them.

You're probably right, I can't reproduce this now. I've been testing on
archer-tromey-python branch at git://sourceware.org/git/archer.git as I've
presumed that's where the patch posted here came from.

Incidentally git is a great improvement: I noticed that variable objects are
now staying in scope when the executable restarted and couldn't see why. I
used 'git bisect' starting with 2000 revisions to find that it was due to Jan
Kratochvil's patch disabling randomisation. I don't think I could have done
that with gdb in CVS. I don't know how up to date the git mirror stays but it
would be grat if we could move to it at some point. There appear to be lots
of other benefits.

>...
> Nick> Existing documentation uses @var for field names, while new uses @samp.
>
> Yeah. @var seems clearly wrong there.
> I will change the new code though.

Really? I thought @samp was wrong. Eli will know.

I would really like to use these improvements in Emacs but the release isn't
far away. So I would request that -enable-pretty-printing is marked as an
EXPERIMENTAL feature in the manual. That way changes can be made without
anyone complaining. Maybe by 7.1 early next year there will be frontends
that have worked out how to use it and that marking could be removed.

--
Nick http://www.inet.net.nz/~nickrob