From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16671 invoked by alias); 3 Aug 2004 19:16:22 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 16662 invoked from network); 3 Aug 2004 19:16:21 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 3 Aug 2004 19:16:21 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i73JGLe3017724 for ; Tue, 3 Aug 2004 15:16:21 -0400 Received: from localhost.redhat.com (porkchop.devel.redhat.com [172.16.58.2]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i73JGFa26679; Tue, 3 Aug 2004 15:16:15 -0400 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id E756C2B9D; Tue, 3 Aug 2004 15:16:09 -0400 (EDT) Message-ID: <410FE479.1020104@gnu.org> Date: Tue, 03 Aug 2004 19:16:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040801 MIME-Version: 1.0 To: Michael Chastain Cc: gdb@sources.redhat.com, david.carlton@sun.com, carlton@bactrian.org Subject: Re: new testsuite function for c++ ptype References: <410F9C94.nail8KU11N4AM@mindspring.com> In-Reply-To: <410F9C94.nail8KU11N4AM@mindspring.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-08/txt/msg00010.txt.bz2 > Here is a sample. Consider the C++ class: > > class A : virtual public V > { > public: > virtual int f(); > private: > int a; > }; > > The call to test this is: > > cp_test_ptype_class "ptype A" "ptype A" \ > "class" "VA" { "public virtual V" } \ > { "V" } \ > { > { "private" "int a;" } > } \ > { > { "public" "virtual int f();" } > } \ > "" Yes, we desperatly need this. Some random ideas. - can the list of fields be grouped vis: .... { { { "private" "int a;" } } { { "public" "virtual int f();" } } } ... so that the formatting / indentation looks more C++ like. - could, for fields and methods, they have explicit tag fields vis: { { field private "int a;" } { method public "virtual int f();" } } or: { field { private "int a;" } method { public "virtual int f();" } } so that there are more textual clues on what is going on (it's a very long parameter list) - I don't undersand why "V" appears twice in: > "class" "VA" { "public virtual V" } \ > { "V" } \ I guess I'm really asking if "V" can be extracted from "public virtual V" Have fun. Andrew