From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-66909-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 4240 invoked by alias); 16 Sep 2009 09:36:04 -0000
Received: (qmail 4216 invoked by uid 22791); 16 Sep 2009 09:36:03 -0000
X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 	tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By: sourceware.org
Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.25)     by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 16 Sep 2009 09:35:59 +0000
Received: from totara (34.60.255.123.dynamic.snap.net.nz [123.255.60.34]) 	by viper.snap.net.nz (Postfix) with ESMTP id 975C33DA13F; 	Wed, 16 Sep 2009 21:35:52 +1200 (NZST)
Received: by totara (Postfix, from userid 1000) 	id 2A154C164; Wed, 16 Sep 2009 21:35:45 +1200 (NZST)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <19120.45425.53760.689552@totara.tehura.co.nz>
Date: Wed, 16 Sep 2009 09:36:00 -0000
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Patch: implement new dynamic varobj spec
In-Reply-To: <h8ptl6$4sm$1@ger.gmane.org>
References: <m3r5uejz4y.fsf@fleche.redhat.com> 	<19120.6268.50257.257928@totara.tehura.co.nz> 	<h8ptl6$4sm$1@ger.gmane.org>
From: nickrob@snap.net.nz (Nick Roberts)
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2009-09/txt/msg00504.txt.bz2

 > > It's probably unusual for the key to be a structure 
 > 
 > Rather, it's very typical in C++. std::map<std::string, whatever> is used
 > all over.

A string is represented by a single value like a scalar.  The case being
considered was  "a struct or some other complicated varobj with children".

 >...
 > > -var-create - * m1
 > > -var-list-children -var1
 > > 
 > >    var1.0       = "map_element"
 > >    var1.0.key   = key0
 > >    var1.0.key.a = 5
 > >    var1.0.key.b = 7.5
 > >    var1.0.value = "a string"
 > 
 > What if 'values' wishes to have a field named 'key'? 

I don't understand.  The frontend would know from var1.0 that key value pairs
follow.  So presumably:

    var1.0.key.key = 5

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