From: Tom Tromey <tromey@redhat.com>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb@sources.redhat.com
Subject: Re: MI & pretty-printing
Date: Wed, 09 Sep 2009 22:34:00 -0000 [thread overview]
Message-ID: <m33a6vpx1s.fsf@fleche.redhat.com> (raw)
In-Reply-To: <h7tasq$j74$1@ger.gmane.org> (Vladimir Prus's message of "Sat, 05 Sep 2009 13:26:51 +0400")
>>>>> "Volodya" == Vladimir Prus <vladimir@codesourcery.com> writes:
Volodya> 1. Do you think it would be OK to make the has_more field
Volodya> always present? This will allow to simplify the frontend code
Volodya> a bit?
I actually did this already just to simplify the code :)
Volodya> For non-dynamic varobjs, it should be non-zero in var-create
Volodya> response if there are children.
For non-dynamic ones, numchild is correct and has_more=0 always.
This made the most sense to me. But, we can change it if you want.
Volodya> 2. Do you think it would be OK to add a special field to
Volodya> indicate that varobj is dynamic? For example, if I expand a
Volodya> regular varobj, I probably want to fetch every field, while for
Volodya> dynamic, I want to fetch just 10.
It would be fine by me. Just let me know what you want it to be called
and I will implement it tomorrow.
Tom
next prev parent reply other threads:[~2009-09-09 22:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 17:42 Vladimir Prus
2009-07-14 1:55 ` Nick Roberts
2009-07-15 12:19 ` Vladimir Prus
2009-08-06 21:02 ` Tom Tromey
2009-08-07 5:18 ` Vladimir Prus
2009-08-15 20:43 ` Vladimir Prus
2009-08-17 18:48 ` Tom Tromey
2009-08-18 7:19 ` Vladimir Prus
2009-08-18 18:41 ` Tom Tromey
2009-08-19 6:51 ` Vladimir Prus
2009-08-19 19:50 ` Tom Tromey
2009-08-20 6:04 ` Vladimir Prus
2009-09-05 9:27 ` Vladimir Prus
2009-09-09 22:34 ` Tom Tromey [this message]
2009-09-14 11:19 ` Vladimir Prus
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=m33a6vpx1s.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@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