This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Nested std::tr1::bind problem

From: Douglas Gregor <doug dot gregor at gmail dot com>
To: libstdc++ <libstdc++ at gcc dot gnu dot org>
Date: Thu, 13 Mar 2008 20:20:50 -0400
Subject: Re: Nested std::tr1::bind problem
References: <frb94q$8bp$1@ger.gmane.org> <016401c88510$e18f8770$6407a80a@pdimov2> <frbel8$1ja$1@ger.gmane.org> <47D962F7.3060406@suse.de>

On Mar 13, 2008, at 1:23 PM, Paolo Carlini wrote:

Rodolfo Schulz de Lima wrote:

Peter Dimov wrote:
_Args&... should probably be changed to _Args&&..., with the
appropriate std::forward<_Args> inserted in the body if it isn't
there already.
I'll be filling a bug report for that, thanks.

Note, we are actually talking about std::bind, *not* std::tr1::bind,
certainly we are not going to use rvalue references in TR1.

We're actually allowed to use rvalue references in TR1... but obviously we can only do so in C++0x mode.

- Doug

Follow-Ups:
- Re: Nested std::tr1::bind problem
  - From: Paolo Carlini

References:
- Nested std::tr1::bind problem
  - From: Rodolfo Lima
- Re: Nested std::tr1::bind problem
  - From: Peter Dimov
- Re: Nested std::tr1::bind problem
  - From: Rodolfo Schulz de Lima
- Re: Nested std::tr1::bind problem
  - From: Paolo Carlini

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]