From: Tom Tromey <tromey@redhat.com>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Python pretty-printing [6/6]
Date: Mon, 18 May 2009 23:34:00 -0000 [thread overview]
Message-ID: <m3my9a0yvg.fsf@fleche.redhat.com> (raw)
In-Reply-To: <loom.20090518T052234-940@post.gmane.org> (Vladimir Prus's message of "Mon\, 18 May 2009 05\:25\:00 +0000 \(UTC\)")
>>>>> "Vladimir" == Vladimir Prus <vladimir@codesourcery.com> writes:
Vladimir> 1. From the *MI* docs it is not apparent why the
Vladimir> 'visualizer' passed is called with varobj to get the real
Vladimir> visualizer. Docs probably should be more explicit.
I will update the docs.
Vladimir> 2. I am unsure about the -var-set-child-range function --
Vladimir> why is this an integral part of this patch? Was this tried
Vladimir> with any frontend, and found sufficient/good? I don't think
Vladimir> we ever reached a conclusion as to how to deal with big
Vladimir> number of children.
Yes, it is not intrinsically related. However, it is very easy for
users to end up with huge objects when a pretty-printer is installed.
That is, I think pretty-printing makes an existing problem more
noticeable.
AFAIK, no front end is currently using this function. So, I can
remove it if you would prefer that.
Tom
next prev parent reply other threads:[~2009-05-18 23:34 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
2009-05-18 23:34 ` Tom Tromey [this message]
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=m3my9a0yvg.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=vladimir@codesourcery.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