From: Tom Tromey <tromey@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: Handling of structure dereferencing
Date: Thu, 06 Dec 2001 15:41:00 -0000 [thread overview]
Message-ID: <87k7vzap57.fsf@creche.redhat.com> (raw)
In-Reply-To: Daniel Jacobowitz's message of "Thu, 6 Dec 2001 12:07:39 -0500"
>>>>> "Daniel" == Daniel Jacobowitz <drow@mvista.com> writes:
Daniel> Right now, and historically, gdb has accepted things like:
Daniel> struct foo {char a} *b, **c, ***d;
Daniel> (gdb) print b.a
Daniel> So, straw poll: how would people feel about:
Daniel> - not letting this happen; only explicit dereferencing
I use `p PTR.field' instead of `p PTR->field' all the time in gdb.
I'd prefer to keep it if possible.
However, I do notice that I only use this in the `b' case.
I don't recall ever using it when there is more than one level of
indirection involved.
Tom
next prev parent reply other threads:[~2001-12-06 23:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 9:07 Daniel Jacobowitz
2001-12-06 11:48 ` Eli Zaretskii
2001-12-06 12:43 ` Daniel Jacobowitz
2002-01-02 20:25 ` Andrew Cagney
2002-02-05 9:31 ` Daniel Berlin
2002-02-05 10:17 ` Daniel Jacobowitz
2001-12-06 15:41 ` Tom Tromey [this message]
2001-12-06 23:36 ` Eli Zaretskii
2001-12-06 9:46 Michael Elizabeth Chastain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k7vzap57.fsf@creche.redhat.com \
--to=tromey@redhat.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox