From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30127 invoked by alias); 15 Dec 2001 05:50:07 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 30094 invoked from network); 15 Dec 2001 05:50:04 -0000 Received: from unknown (HELO localhost.cygnus.com) (24.114.42.213) by sources.redhat.com with SMTP; 15 Dec 2001 05:50:04 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.cygnus.com (Postfix) with ESMTP id 8B5203D60; Sat, 15 Dec 2001 00:50:03 -0500 (EST) Message-ID: <3C1AE48B.70809@cygnus.com> Date: Fri, 14 Dec 2001 21:50:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.6) Gecko/20011207 X-Accept-Language: en-us MIME-Version: 1.0 To: Jim Ingham Cc: gdb-patches@sources.redhat.com Subject: Re: gdb-patches Digest 9 Dec 2001 19:14:34 -0000 Issue 896 References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2001-12/txt/msg00396.txt.bz2 > Andrew, > > This works fine for me. Looks better too. Thanks for the feedback, it is in. > I always thought it was kind of odd that when you were emitting a table, you > still sent the tags for each item, rather than just emitting the table as a > list of rows, each row being just a simple list of entries. Then the client > of the MI could use the header to identify the elements of each row. We > could still pass in the column name into ui_out_field_x, and use it to > sanity check the table as we were building it, but just not emit the tag > when we are emitting the element. I would need to dig up notes. I think one reason is that, as illustrated by the breakpoint, things are not as correctly laid out as you might expect. The colums within a row are tuples since, for a given table, the number of colums and their names should be known and each column could have a type different to the next. Hmm, and tuple fields get names :-) > This would be a lot more efficient for big tables. We use a table for the > shared library info on X, and it can get very big - one developer had 600 > shared libraries/plugins in his app! > > However, PB uses the current form of the table, so I am not in a big hurry > to fix this. Just something to think about. BTW, I missed the varobj stuff when reviewing all the output. Andrew