public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/38411] [4.4 Regression] Revision 142439 caused 22_locale/locale/cons/7.cc execution test Date: Fri, 05 Dec 2008 09:11:00 -0000 [thread overview] Message-ID: <20081205091034.7566.qmail@sourceware.org> (raw) In-Reply-To: <bug-38411-682@http.gcc.gnu.org/bugzilla/> ------- Comment #9 from jakub at gcc dot gnu dot org 2008-12-05 09:10 ------- Forcing "," thousands separator when none should be used is very weird. Does C++ standard mandate that behavior? "" means thousands shouldn't be separated by any separator. In most cases such locales also have grouping 0;0 or -1, but there are buggy? locales, e.g. bg_BG, that specify empty thousands_sep, yet have grouping 3;3. For empty thousands_sep glibc just forces no grouping: if ((wide && thousands_sepwc == L'\0') || (! wide && *thousands_sep == '\0')) grouping = NULL; BTW, thousands_sep is a multibyte string, it can be multiple bytes (or none, as discussed here). Say ru_RU has: "<U2002>" which is 3 bytes: <U2002> /xe2/x80/x82 EN SPACE and a bunch of locales are using "<U00A0>", which is 2 bytes: <U00A0> /xc2/xa0 NO-BREAK SPACE _NL_NUMERIC_THOUSANDS_SEP_WC is always just one wchar_t though. thousands_sep is one of the things that changed in fr_FR this year, see sourceware #6040. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38411
next prev parent reply other threads:[~2008-12-05 9:11 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-12-05 3:07 [Bug libstdc++/38411] New: [4.4 Regression] " hjl dot tools at gmail dot com 2008-12-05 3:10 ` [Bug libstdc++/38411] " hjl dot tools at gmail dot com 2008-12-05 5:28 ` [Bug libstdc++/38411] [4.4 Regression] Revision 142439 caused " hjl dot tools at gmail dot com 2008-12-05 5:36 ` hjl dot tools at gmail dot com 2008-12-05 8:25 ` paolo dot carlini at oracle dot com 2008-12-05 8:38 ` jakub at gcc dot gnu dot org 2008-12-05 8:48 ` paolo dot carlini at oracle dot com 2008-12-05 8:51 ` paolo dot carlini at oracle dot com 2008-12-05 8:57 ` paolo dot carlini at oracle dot com 2008-12-05 9:11 ` jakub at gcc dot gnu dot org [this message] 2008-12-05 9:14 ` jakub at gcc dot gnu dot org 2008-12-05 9:17 ` paolo dot carlini at oracle dot com 2008-12-05 9:18 ` paolo dot carlini at oracle dot com 2008-12-05 9:40 ` jakub at gcc dot gnu dot org 2008-12-05 9:44 ` paolo dot carlini at oracle dot com 2008-12-05 9:45 ` paolo dot carlini at oracle dot com 2008-12-05 9:49 ` jakub at gcc dot gnu dot org 2008-12-05 9:53 ` paolo dot carlini at oracle dot com 2008-12-05 9:56 ` paolo dot carlini at oracle dot com 2008-12-05 9:56 ` paolo dot carlini at oracle dot com 2008-12-05 11:09 ` tsyvarev at ispras dot ru 2008-12-05 13:10 ` paolo at gcc dot gnu dot org 2008-12-05 13:11 ` paolo dot carlini at oracle dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20081205091034.7566.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).