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: [c++0x] Ambiguity using std::to_string

From: Paolo Carlini <paolo dot carlini at oracle dot com>
To: Germán Diago <germandiago at gmail dot com>
Cc: libstdc++ at gcc dot gnu dot org
Date: Thu, 12 Nov 2009 12:33:59 +0100
Subject: Re: [c++0x] Ambiguity using std::to_string
References: <b798010f0911100024j7d509756x39f2ac3eab5236de@mail.gmail.com> <99A2D883-81AC-440E-80BB-2FFB9430C25F@bubblescope.net> <4AF98A14.6090600@oracle.com> <E5BBEE77-293A-41E6-9F81-34B85421112A@bubblescope.net> <b798010f0911120330j5c0b50a2k5f7891e291019d50@mail.gmail.com>

Germán Diago wrote:
>> Yes, on the case, will submit DR and get a discussion going. However this is fixed, the current situation is clearly embarrassing.
>>     
> Anyway I think someone could add in gcc the overloads as an extension.
>   
I added the overloads yesterday, per the proposed resolution of DR 1261
as filed by Chris.

Paolo.

References:
- [c++0x] Ambiguity using std::to_string
  - From: Germán Diago
- Re: [c++0x] Ambiguity using std::to_string
  - From: Christopher Jefferson
- Re: [c++0x] Ambiguity using std::to_string
  - From: Paolo Carlini
- Re: [c++0x] Ambiguity using std::to_string
  - From: Christopher Jefferson
- Re: [c++0x] Ambiguity using std::to_string
  - From: Germán Diago

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