[Bug libstdc++/22131] std::num_get fails for input with invalid groups

2005-06-29 Thread pcarlini at suse dot de
--- Additional Comments From pcarlini at suse dot de 2005-06-29 12:08 --- Fixed for 4.1.0. -- What|Removed |Added Status|ASSIGNED|RESOLVED

[Bug libstdc++/22131] std::num_get fails for input with invalid groups

2005-06-29 Thread cvs-commit at gcc dot gnu dot org
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-06-29 11:49 --- Subject: Bug 22131 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2005-06-29 11:48:54 Modified files: libstdc++-v3 : ChangeLog libstdc++-v3/inclu

[Bug libstdc++/22131] std::num_get fails for input with invalid groups

2005-06-24 Thread pcarlini at suse dot de
--- Additional Comments From pcarlini at suse dot de 2005-06-24 18:22 --- Thanks Martin for the clarification: 100% agreed, also about the grammar thing. I will fix that in a few days, as soon as I'm back from GCCSummit. -- What|Removed |Added ---

[Bug libstdc++/22131] std::num_get fails for input with invalid groups

2005-06-24 Thread sebor at roguewave dot com
--- Additional Comments From sebor at roguewave dot com 2005-06-24 17:11 --- Yes, sorry for being too terse. The value is supposed to be stored even if the placement of the thousands separators is invalid, just as long as the input sequence matches the grammar in 22.2.3.1, p2. For examp

[Bug libstdc++/22131] std::num_get fails for input with invalid groups

2005-06-24 Thread pcarlini at suse dot de
--- Additional Comments From pcarlini at suse dot de 2005-06-24 12:18 --- If I understand correctly Martin, the point is that, according to 22.2.2.1.2/11-12, even when the groups are invalid (indeed, he expects a fail in the second assert) the value is stored in val anyway. If this is h

[Bug libstdc++/22131] std::num_get fails for input with invalid groups

2005-06-24 Thread chris at bubblescope dot net
--- 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