From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com, gdb@sources.redhat.com
Subject: Re: Handling of structure dereferencing
Date: Thu, 06 Dec 2001 09:46:00 -0000 [thread overview]
Message-ID: <200112061745.LAA12491@duracef.shout.net> (raw)
> So, straw poll: how would people feel about:
> - not letting this happen; only explicit dereferencing
As a user, this would be fine with me, although I can see how it would
bother other users.
It's 10x more important to me that "print foo.a" and "print foo.b()"
never return incorrect data. I can live with virtual baseclass botch,
but when the debugger prints an incorrect value, that destroys my
faith in all the other values it prints. If getting rid of the
implicit dereference helps, I'm all for it.
Michael C
next reply other threads:[~2001-12-06 17:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 9:46 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2001-12-06 23:36 ` Eli Zaretskii
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=200112061745.LAA12491@duracef.shout.net \
--to=mec@shout.net \
--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