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: New const char* ctor for C++-0x

From: Paolo Carlini <paolo dot carlini at oracle dot com>
To: Ed Smith-Rowland <3dw4rd at verizon dot net>
Cc: Jonathan Wakely <jwakely dot gcc at gmail dot com>, libstdc++ at gcc dot gnu dot org
Date: Thu, 24 Dec 2009 18:40:53 +0100
Subject: Re: New const char* ctor for C++-0x
References: <4348dea50912240618v9d5d377w1526077d3cdb3a4c@mail.gmail.com> <4B337BE7.5070903@oracle.com> <4348dea50912240645n30bbc1bala11f116c86e4a68b@mail.gmail.com> <4B33A288.2060209@verizon.net>

On 12/24/2009 06:19 PM, Ed Smith-Rowland wrote:
> Here is a new patch incorporating the test changes suggested by
> Jonathan and removing the stupid paste-o size_t thing.
Ok, thanks, I think it can go in.
> Regtested and bootstrapped of course.
>
> In addition, for discussion, is a patch with the umsigned long long
> changes.  I made the ctor available ic C++-x *and* have long long.  So
> in we're doing C++-0x and long long is not available you should still
> get the unsigned long ctor.
In general terms, frankly, this doesn't make sense: C++0x, among tons of
different things, also standardizes long long, thus it cannot be
unavailable in C++0x mode.

Paolo.

Follow-Ups:
- Re: New const char* ctor for C++-0x
  - From: Paolo Carlini

References:
- [c++0x patch] allow std::bind<void>
  - From: Jonathan Wakely
- Re: [c++0x patch] allow std::bind<void>
  - From: Paolo Carlini
- Re: [c++0x patch] allow std::bind<void>
  - From: Jonathan Wakely
- Re: [c++0x patch] allow std::bind<void>
  - From: Ed Smith-Rowland

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