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: Some details on the named locale problem

From: Paolo Carlini <pcarlini at unitus dot it>
To: Ulrich Drepper <drepper at redhat dot com>
Cc: libstdc++ at gcc dot gnu dot org, ncm at cantrip dot org, bkoz at redhat dot com
Date: Tue, 29 Jan 2002 00:32:05 +0100
Subject: Re: Some details on the named locale problem
References: <3C554198.61F947F6@unitus.it> <20020128230339.A80012@cantrip.org> <3C55DB02.5708C4FA@unitus.it> <m3elka83am.fsf@myware.mynet>

Ulrich Drepper wrote:

> No.  If the locale contains an empty string it means an empty string.
> The grouping string is irrelevant since adding an empty string
> anywhere wouldn't change the output.  If you substitute ',' for NUL
> this what be completely wrong.

Ok... Thanks.

Therefore, in general we will leave the thousands separator as returned by libc
and, in the case of glibc, we will infer from the particular value \0 a grouping
== "", right?

The patch I have just posted, for the time being does just this.

Cheers,
Paolo.

Follow-Ups:
- Re: Some details on the named locale problem
  - From: Ulrich Drepper

References:
- Some details on the named locale problem
  - From: Paolo Carlini
- Re: Some details on the named locale problem
  - From: Nathan Myers
- Re: Some details on the named locale problem
  - From: Paolo Carlini
- Re: Some details on the named locale problem
  - From: Ulrich Drepper

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