This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: libstdc++, generic locale configuration, and c++0x
- From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- To: Doug Semler <dougsemler at gmail dot com>
- Cc: "libstdc++" <libstdc++ at gcc dot gnu dot org>
- Date: Mon, 7 Jun 2010 00:55:26 +0100
- Subject: Re: libstdc++, generic locale configuration, and c++0x
- References: <AANLkTinGdh6X4yKymGJbAo0jcCNir9Q8dp_HXdeMSo09@mail.gmail.com> <76EA67BD-2158-45A7-BFBA-1DFBD8E35FC0@oracle.com> <AANLkTinmVgtteP0heyCXtNG0imq33f9SFJlSq29ToT4p@mail.gmail.com> <AANLkTinnwj1obWy49K2vYy6VHnhs4HdsPZYyPGAmZDU0@mail.gmail.com>
On 6 June 2010 19:31, Jonathan Wakely wrote:
> (Shouldn't this be on the libstdc++ list?)
Moved, see http://gcc.gnu.org/ml/gcc/2010-06/msg00254.html for the
original thread.
> On 6 June 2010 19:02, Doug Semler wrote:
>>
>> So...would you consider this a bug in the documentation, or a bug in
>> the library?
>
> I would say the docs, and only partly because it's easier to fix ;-)
Actually, it's not so hard to fix the code, I have a prototype patch
using a mutex lock around changes to the global locale, but it's
likely to seriously affect performance in multithreaded programs.