This is the mail archive of the
mailing list for the GCC project.
Re: [v3] libstdc++/7811
- From: Matt Austern <austern at apple dot com>
- To: Benjamin Kosnik <bkoz at redhat dot com>
- Cc: roland at redhat dot com, pcarlini at unitus dot it, jakub at redhat dot com, gcc-patches at gcc dot gnu dot org
- Date: Fri, 6 Sep 2002 12:04:07 -0700
- Subject: Re: [v3] libstdc++/7811
On Friday, September 6, 2002, at 11:54 AM, Benjamin Kosnik wrote:
It's not just a good idea, it's the law. The C++ Standard requires
std::locale::name() and std::setlocale() to use the same format for
composite locales. This is a nontrivial requirement.
Don't see it specified. Are you referring to std::locale::global?
Yes. I don't think it's possible to interpret that requirement
as anything but saying that std::locale::name() and
std::setlocale() must use the same format. OK, that's just
slightly too strong. More precisely, it implies that the set of
locale names understood by std::locale's constructor
must be a subset of the names understood by std::setlocale().
I think it would be permissible for std::setlocale to
accept names that aren't understood by std::locale's constructor,
but not the converse.