Return-Path: 
 <dev-return-7891-apmail-stdcxx-dev-archive=stdcxx.apache.org@stdcxx.apache.org>
Delivered-To: apmail-stdcxx-dev-archive@www.apache.org
Received: (qmail 22764 invoked from network); 19 Jun 2008 16:33:34 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 19 Jun 2008 16:33:34 -0000
Received: (qmail 30613 invoked by uid 500); 19 Jun 2008 16:33:34 -0000
Delivered-To: apmail-stdcxx-dev-archive@stdcxx.apache.org
Received: (qmail 30603 invoked by uid 500); 19 Jun 2008 16:33:34 -0000
Mailing-List: contact dev-help@stdcxx.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@stdcxx.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@stdcxx.apache.org>
List-Post: <mailto:dev@stdcxx.apache.org>
List-Id: <dev.stdcxx.apache.org>
Reply-To: dev@stdcxx.apache.org
Delivered-To: mailing list dev@stdcxx.apache.org
Received: (qmail 30592 invoked by uid 99); 19 Jun 2008 16:33:34 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Jun 2008 09:33:34 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: local policy)
Received: from [208.30.140.160] (HELO moroha.roguewave.com) (208.30.140.160)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Jun 2008 16:32:45 +0000
Received: from exchmail01.Blue.Roguewave.Com (exchmail01.blue.roguewave.com
 [10.22.129.22])
	by moroha.roguewave.com (8.13.6/8.13.6) with ESMTP id m5JGX1Tx018249
	for <dev@stdcxx.apache.org>; Thu, 19 Jun 2008 16:33:01 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: :decay related question
Date: Thu, 19 Jun 2008 10:32:37 -0600
Message-ID: 
 <CFFDD219128FD94FB4F92B99F52D0A499AA8B7@exchmail01.Blue.Roguewave.Com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: :decay related question
Thread-Index: AcjRjRczO6qmwoLVQlCsERR7V8yIZQABjZmgACJih8AAA0QqIA==
References: 
 <CFFDD219128FD94FB4F92B99F52D0A49010A3875@exchmail01.Blue.Roguewave.Com>
 <CFFDD219128FD94FB4F92B99F52D0A499AA8B5@exchmail01.Blue.Roguewave.Com>
 <CFFDD219128FD94FB4F92B99F52D0A49010A3877@exchmail01.Blue.Roguewave.Com>
From: "Travis Vitek" <Travis.Vitek@roguewave.com>
To: <dev@stdcxx.apache.org>
X-Virus-Checked: Checked by ClamAV on apache.org

=20

>Eric Lemings wrote:
>
>>=20
>> If that is right, then it essentially says that the 'make_tuple'
>> function transforms reference_wrapper<T> back to T& and for=20
>> other types does the normal decay transformation [function to
>> funciton pointer, array to array pointer, and cv-stripping of
>> all other types].
>
>That's what I thought.  That's also what other implementations are
>showing.
>
>Also, doesn't an array decay to a pointer to the element type?

Yes. Just a typo.

>
>Brad.
>