Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Martin Galvan <martin.galvan@tallertechnologies.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2][PR gdb/19893] Fix handling of synthetic C++ references
Date: Wed, 25 May 2016 18:24:00 -0000	[thread overview]
Message-ID: <2dc66791-b716-48a1-1a7e-3e853fd38127@redhat.com> (raw)
In-Reply-To: <CAOKbPbZjzy=KnbM1BYK27CQC9hfpko=BBT3E3svn6ACQ6_Nrcg@mail.gmail.com>

On 05/24/2016 09:35 PM, Martin Galvan wrote:

> So I think before proceeding we should decide which output is better.
> Perhaps we could show @address whenever possible, and <synthetic
> pointer> for the corner cases?

Yes, I think so.  Synthetic pointers are really
an implementation detail, not really something users care about.

> On a related note, it'd be great (for debugging at least!) if unions
> such as this had at least a discriminant of sorts.

It's the value's lval type.  :-)

> Right now I don't think so. The existing methods should be enough to
> handle these cases. Speaking of which, are there any plans to rewrite
> this sort of object-oriented code in C++? I'd love to take a shot at
> this in the future.

Certainly, that'd be welcome.

Thanks,
Pedro Alves


      reply	other threads:[~2016-05-25 18:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-23 16:00 Martin Galvan
2016-05-23 18:36 ` Martin Galvan
2016-05-24 10:48 ` Pedro Alves
2016-05-24 14:08   ` Martin Galvan
2016-05-24 14:51     ` Pedro Alves
2016-05-24 20:36       ` Martin Galvan
2016-05-25 18:24         ` Pedro Alves [this message]

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=2dc66791-b716-48a1-1a7e-3e853fd38127@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=martin.galvan@tallertechnologies.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