--- Comment #5 from paolo at gcc dot gnu dot org 2008-12-04 17:17 ---
Subject: Bug 38368
Author: paolo
Date: Thu Dec 4 17:16:27 2008
New Revision: 142439
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=142439
Log:
2008-12-04 Paolo Carlini [EMAIL PROTECTED]
PR
--- Comment #6 from paolo dot carlini at oracle dot com 2008-12-04 17:19
---
Fixed for 4.4.0.
--
paolo dot carlini at oracle dot com changed:
What|Removed |Added
--- Comment #1 from paolo dot carlini at oracle dot com 2008-12-03 10:34
---
This sort-of inconsistency is essentially due to the glibc specifics (+ the
fact that we are dealing separately with C locale) see the below GNU C
snippet. In particular, note in numeric_members.cc that we
--- Comment #2 from paolo dot carlini at oracle dot com 2008-12-03 10:46
---
Or maybe we should just report the __MON_DECIMAL_POINT == '\0' thing to glibc,
which seems special to me (THOUSANDS_SEP == '\0' is well known, on the other
hand).
--
--- Comment #3 from tsyvarev at ispras dot ru 2008-12-03 16:27 ---
Yes, I see, this is feature of glibc: for POSIX locale it defines
THOUSANDS_SEP, __MON_THOUSANDS_SEP and __MON_DECIMAL_POINT as .
According to documentation for C-locale, this value means N/A (not assigned).
But this
--- Comment #4 from paolo dot carlini at oracle dot com 2008-12-03 17:15
---
Ok, let's try to enforce this kind of consistency.
--
paolo dot carlini at oracle dot com changed:
What|Removed |Added
