public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "chris at bubblescope dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/22131] std::num_get fails for input with invalid groups Date: Fri, 24 Jun 2005 08:52:00 -0000 [thread overview] Message-ID: <20050624085217.10511.qmail@sourceware.org> (raw) In-Reply-To: <20050620234814.22131.sebor@roguewave.com> ------- Additional Comments From chris at bubblescope dot net 2005-06-24 08:52 ------- It's probably me being blind, but could you point out the part of the standard which defines what should be happening? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22131
next prev parent reply other threads:[~2005-06-24 8:52 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-06-20 23:48 [Bug libstdc++/22131] New: " sebor at roguewave dot com 2005-06-24 8:52 ` chris at bubblescope dot net [this message] 2005-06-24 12:18 ` [Bug libstdc++/22131] " pcarlini at suse dot de 2005-06-24 17:11 ` sebor at roguewave dot com 2005-06-24 18:22 ` pcarlini at suse dot de 2005-06-29 11:49 ` cvs-commit at gcc dot gnu dot org 2005-06-29 12:08 ` 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=20050624085217.10511.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).