public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fang at csl dot cornell dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/29939] Add rvalue references (C++0x)
Date: Wed, 29 Nov 2006 19:00:00 -0000	[thread overview]
Message-ID: <20061129190035.1310.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29939-13604@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from fang at csl dot cornell dot edu  2006-11-29 19:00 -------
Subject: Re:  Add rvalue references (C++0x)

On 29 Nov 2006, hhinnant at apple dot com wrote:

> ------- Comment #3 from hhinnant at apple dot com  2006-11-29 18:36 -------
> Recent work:
>
> http://mndfck.org/~pedro.lamarao/projects/c++0x/
> http://home.twcny.rr.com/hinnant/cpp_extensions/rvalue_ref_test/

Excellent, these tests look like simple examples to learn from, as a
supplement to the technical reports.  Thanks for putting this together.
I'll be following developments and testing from time to time.
I'm highly anticipating this in the upcoming standard.

Fang


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29939


  parent reply	other threads:[~2006-11-29 19:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-22 14:19 [Bug c++/29939] New: Please implement rvalue references jyasskin at gmail dot com
2006-11-22 15:07 ` [Bug c++/29939] " fang at csl dot cornell dot edu
2006-11-22 16:22 ` hhinnant at apple dot com
2006-11-22 16:44 ` [Bug c++/29939] Add rvalue references (C++0x) pinskia at gcc dot gnu dot org
2006-11-29 18:36 ` hhinnant at apple dot com
2006-11-29 19:00 ` fang at csl dot cornell dot edu [this message]
2007-02-21 20:17 ` hhinnant at apple dot com
2007-02-21 20:26 ` fang at csl dot cornell dot edu
2007-05-31  1:18 ` dgregor at gcc dot gnu dot org
2007-05-31  1:29 ` dgregor at gcc dot gnu dot org

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=20061129190035.1310.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).