public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/13369] __verify_grouping (and __add_grouping?) not correct
Date: Tue, 09 Dec 2003 14:30:00 -0000	[thread overview]
Message-ID: <20031209143009.26226.qmail@sources.redhat.com> (raw)
In-Reply-To: <20031209141517.13369.paolo@gcc.gnu.org>


------- Additional Comments From paolo at gcc dot gnu dot org  2003-12-09 14:30 -------
A value of CHAR_MAX for a group also means an unlimited group, and it's more 
interesting than zero, since the latter *cannot* actually occur in the stored
grouping: \0 delimits the string returned by __nl_langinfo_l(GROUPING, __cloc);



-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
   Last reconfirmed|2003-12-09 14:15:28         |2003-12-09 14:30:09
               date|                            |


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


  parent reply	other threads:[~2003-12-09 14:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-09 14:15 [Bug libstdc++/13369] New: " paolo at gcc dot gnu dot org
2003-12-09 14:15 ` [Bug libstdc++/13369] " paolo at gcc dot gnu dot org
2003-12-09 14:30 ` paolo at gcc dot gnu dot org [this message]
2003-12-09 14:30 ` paolo at gcc dot gnu dot org
2003-12-30 11:41 ` cvs-commit at gcc dot gnu dot org
2003-12-30 11:44 ` paolo at gcc dot gnu dot org
     [not found] <20031209141517.13369.pcarlini@suse.de>
2004-01-29  2:52 ` cvs-commit at gcc dot gnu dot org
2004-01-29  2:52 ` pcarlini at suse dot de

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=20031209143009.26226.qmail@sources.redhat.com \
    --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).