From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12992 invoked by alias); 14 Sep 2009 11:19:15 -0000 Received: (qmail 12981 invoked by uid 22791); 14 Sep 2009 11:19:14 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 14 Sep 2009 11:19:03 +0000 Received: (qmail 31786 invoked from network); 14 Sep 2009 11:18:55 -0000 Received: from unknown (HELO wind.localnet) (vladimir@127.0.0.2) by mail.codesourcery.com with ESMTPA; 14 Sep 2009 11:18:55 -0000 From: Vladimir Prus To: tromey@redhat.com Subject: Re: MI & pretty-printing Date: Mon, 14 Sep 2009 11:19:00 -0000 User-Agent: KMail/1.11.90 (Linux/2.6.24-24-generic; KDE/4.2.90; i686; svn-979530; 2009-06-10) Cc: gdb@sources.redhat.com References: <200907132142.18043.vladimir@codesourcery.com> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200909141518.55078.vladimir@codesourcery.com> Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-09/txt/msg00175.txt.bz2 On Thursday 10 September 2009 Tom Tromey wrote: > >>>>> "Volodya" == Vladimir Prus 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. I though about this, and I think the current behaviour is fine. Sorry for incoherent comments. > 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. I guess I need to play more with this to figure if I need it now. Can we please have this in CVS HEAD, so that I can have other kdevelop users bang at it? Thanks, Volodya who can play?