public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: PR symtab/14441 - rvalue references
Date: Mon, 29 Oct 2012 14:54:00 -0000	[thread overview]
Message-ID: <87txtdz76a.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CAH6eHdRRCnd0PtKZT09UiYKWgc2OS7g+WW9MBXhaTx00=YCdrg@mail.gmail.com>	(Jonathan Wakely's message of "Sun, 28 Oct 2012 20:34:40 +0000")

>>>>> "Jonathan" == Jonathan Wakely <jwakely.gcc@gmail.com> writes:

Jonathan> I'm trying to fix
Jonathan> http://sourceware.org/bugzilla/show_bug.cgi?id=14441 by adding
Jonathan> support for rvalue references.  I plan to contribute this if I
Jonathan> get it finished before anyone else fixes it, so I'll get a
Jonathan> copyright assignment for GDB filed with the FSF clerk.

Very nice, thank you.

Jonathan> Before I continue altering every function that checks TYPE_CODE_REF,
Jonathan> is my approach the right one?  Is adding TYPE_CODE_RVAL_REF and
Jonathan> touching dozens of functions the best approach, or should I go back to
Jonathan> my first attempt and just fix the few places that need to handle
Jonathan> lvalue and rvalue references differently?

I would accept either one.  Abstractly, I suppose a new type code would
be more in keeping with the current design.  But I think the other
choice would be ok, too, if it is a reasonably accurate model of C++.  I
don't know enough about rvalue references to say whether this is the
case.

Tom

  reply	other threads:[~2012-10-29 14:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-28 20:34 Jonathan Wakely
2012-10-29 14:54 ` Tom Tromey [this message]
2012-10-29 23:40   ` Jonathan Wakely
2012-10-30 15:05 ` Tom Tromey

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=87txtdz76a.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=jwakely.gcc@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).