From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb-patches@sources.redhat.com
Subject: Re: Python pretty-printing [6/6]
Date: Mon, 18 May 2009 05:25:00 -0000 [thread overview]
Message-ID: <loom.20090518T052234-940@post.gmane.org> (raw)
In-Reply-To: <m37i22bwoq.fsf@fleche.redhat.com>
Tom Tromey <tromey <at> redhat.com> writes:
>
> This patch adds MI support for pretty-printing.
>
> An MI varobj can now have dynamic children, supplied by a Python
> pretty-printer. Pretty-printing for a varobj can be disabled via an
> MI request.
>
> This patch also adds a way for MI users to fetch only a subset of
> available children.
>
> Finally, it adds the "python" MI feature.
I must admit I did not examine all of the code very closely -- and it's
probably not gonna be productive to be picking code nits in such a huge patch.
I have a couple of higher-level comments:
1. From the *MI* docs it is not apparent why the 'visualizer' passed is called
with varobj to get the real visualizer. Docs probably should be more explicit.
2. I am unsure about the -var-set-child-range function -- why is this an
integral part of this patch? Was this tried with any frontend, and found
sufficient/good? I don't think we ever reached a conclusion as to how to deal
with big number of children.
- Volodya
next prev parent reply other threads:[~2009-05-18 5:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 20:58 Tom Tromey
2009-04-03 15:31 ` Eli Zaretskii
2009-04-09 1:14 ` Tom Tromey
2009-04-09 7:42 ` Eli Zaretskii
2009-05-18 5:25 ` Vladimir Prus [this message]
2009-05-18 23:34 ` Tom Tromey
2009-05-21 18:11 ` Tom Tromey
2009-05-21 18:33 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20090518T052234-940@post.gmane.org \
--to=vladimir@codesourcery.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox