From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8852 invoked by alias); 3 Dec 2002 16:08:43 -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 8823 invoked from network); 3 Dec 2002 16:08:26 -0000 Received: from unknown (HELO uniton.integrable-solutions.net) (62.212.99.186) by sources.redhat.com with SMTP; 3 Dec 2002 16:08:26 -0000 Received: from uniton.integrable-solutions.net (localhost [127.0.0.1]) by uniton.integrable-solutions.net (8.12.3/8.12.3/SuSE Linux 0.6) with ESMTP id gB3G3btv016967; Tue, 3 Dec 2002 17:03:37 +0100 Received: (from gdr@localhost) by uniton.integrable-solutions.net (8.12.3/8.12.3/Submit) id gB3G3bAW016966; Tue, 3 Dec 2002 17:03:37 +0100 X-Authentication-Warning: uniton.integrable-solutions.net: gdr set sender to gdr@integrable-solutions.net using -f To: Michael Elizabeth Chastain Cc: gdb@sources.redhat.com Subject: Re: Another "ptype B" validity question References: <200212031556.gB3Fuwb30282@duracef.shout.net> From: Gabriel Dos Reis In-Reply-To: <200212031556.gB3Fuwb30282@duracef.shout.net> Organization: Integrable Solutions Date: Tue, 03 Dec 2002 08:08:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-12/txt/msg00052.txt.bz2 Michael Elizabeth Chastain writes: [...] | # gdb HEAD, gcc HEAD, binutils 2.13.1, stabs+ | ptype class B | type = class B : public A { | public: | A; [...] | My questions are: | | . What should gdb print for this ptype operation? | | . If gdb does print the "A;" member, is that acceptable or not? | Note that this is a slightly different question! I think the line class B : public A saying that B inherits from A is self-explanatory and there is no need to display A as a member-declaration -- it is not, and that is confusing. [...] | In this case, I think that most C++ programmers | would understand the nature of the "A;" line, Well, I find it very confusing -- it is too close to nested-type declaration. -- Gaby