public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tsyvarev at ispras dot ru" <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 11:09:00 -0000	[thread overview]
Message-ID: <20081205110839.13603.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38411-682@http.gcc.gnu.org/bugzilla/>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]



------- Comment #19 from tsyvarev at ispras dot ru  2008-12-05 11:08 -------
It seems that C++ standard contains contradiction about thousands separator in
"C" locale:

22.2.3.1, p1 says:

The instantiations required in Table 51 (22.1.1.1.1), namely numpunct<wchar_t>
and numpunct<char>, provide classic “C” numeric formats, i.e. they contain
information equivalent to that contained in the “C” locale or their wide
character counterparts as if obtained by a call to widen.

also, 22.2.3.1.2 p.2 says:

char_type do_thousands_sep() const;

Returns: A character for use as the digit group separator. The required
instantiations return ’,’ or L’,’.

It appears, that according to C++ standard, thousands separator for "C" locale
is ','.

But according to the ISO standard of "C"("POSIX") locale (Section 7.3, Locale
Definition), thousands separator in this locale should be '\0', which means N/A
or not assigned.

Or is this reasoning wrong?


-- 

tsyvarev at ispras dot ru changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tsyvarev at ispras dot ru


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38411


  parent reply	other threads:[~2008-12-05 11:09 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
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 [this message]
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=20081205110839.13603.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: link
Be 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).