From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1511 invoked by alias); 5 Feb 2002 17:31:05 -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 1350 invoked from network); 5 Feb 2002 17:30:49 -0000 Received: from unknown (HELO dberlin.org) (64.246.6.106) by sources.redhat.com with SMTP; 5 Feb 2002 17:30:49 -0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by dberlin.org (8.11.6/8.11.6) with ESMTP id g15HUfr05061; Tue, 5 Feb 2002 12:30:41 -0500 Date: Tue, 05 Feb 2002 09:31:00 -0000 From: Daniel Berlin To: Andrew Cagney cc: Daniel Jacobowitz , Eli Zaretskii , Subject: Re: Handling of structure dereferencing In-Reply-To: <3C33DD48.2050801@cygnus.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-02/txt/msg00106.txt.bz2 On Thu, 3 Jan 2002, Andrew Cagney wrote: > > On Thu, Dec 06, 2001 at 09:47:50PM +0200, Eli Zaretskii wrote: > > > >> > Date: Thu, 6 Dec 2001 12:07:39 -0500 > >> > From: Daniel Jacobowitz > >> > > >> > Right now, and historically, gdb has accepted things like: > >> > struct foo {char a} *b, **c, ***d; > >> > > >> > (gdb) print b.a > >> > (gdb) print d->a > > > b->a and b.a are probably commonly used - don't some languages even > accept both forms? As for ``d.a'', I don't have an opinion - hmm, now > that I know about it I might just start using it :-( > I switch them all the time. For pointers, i usually start by printing [0] of it, then [0].some member[0], etc. I almost never use ->. Why should I have to care whether the object is really a pointer or not to be able to print a member? I only care about printing the member, or else i wouldn't have asked for it. Is there some good reason to not allow either to work? IE is allowing it breaking something else, or preventing something else from being implemented? If not, why make it *harder* for users to do what they want? I don't want to have to remember whether in the expression "a.x.d.b.c", whether b is a poiner or not. I only care about seeing c. If this is changed, it would, at least for me (and i imagine a large number of others) make gdb a lot harder to use. --Dan