Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: "Paul Pluzhnikov" <ppluzhnikov@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] [patch] 'p->x' vs. 'p.x' and 'print object on'
Date: Thu, 07 Aug 2008 17:31:00 -0000	[thread overview]
Message-ID: <m3tzdwhgv1.fsf@fleche.redhat.com> (raw)
In-Reply-To: <8ac60eac0807301050id1051q8072925c0d11b96d@mail.gmail.com> (Paul Pluzhnikov's message of "Wed\, 30 Jul 2008 10\:50\:24 -0700")

>>>>> "Paul" == Paul Pluzhnikov <ppluzhnikov@google.com> writes:

Paul> Thanks for bringing that up. I've modified the test case to have
Paul> a field 'y' in both the base and derived classes (attached at the
Paul> end), and the current situation is (IMHO) just as confusing before
Paul> the patch as it is after :(

Thanks for doing this.

Paul> C) Do what the language does: lookup field 'x' in the static type,
Paul>    and only try dynamic type if the first lookup failed:

Paul> I think "C" is the least confusing alternative.
Paul> It may actually be good to do "C" independent of the 'print object'
Paul> setting.

I agree.  This does sound better.

Paul> Yes, I just wanted to see what people think about this before
Paul> creating the test case.

FWIW I'm definitely in favor.

Tom


  reply	other threads:[~2008-08-07 17:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-17 21:49 Paul Pluzhnikov
2008-07-22  0:53 ` Tom Tromey
2008-07-30 17:51   ` Paul Pluzhnikov
2008-08-07 17:31     ` Tom Tromey [this message]
2008-08-07 20:20       ` Daniel Jacobowitz
2008-08-11 15:09     ` Tom Tromey
2008-08-19 18:05       ` Paul Pluzhnikov
2008-08-26 16:45         ` Paul Pluzhnikov
2008-10-22 22:32         ` Ulrich Weigand

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=m3tzdwhgv1.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=ppluzhnikov@google.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