------- Comment #2 from paolo dot carlini at oracle dot com 2008-10-30 16:15 ------- Maybe now I see, what's behind your report: you believe that, when val is set, eofbit should be set only when seeking another character to match. But that would essentially boil down to *never* set it, in that case, because val is set only when a target sequence is uniquely matched, thus we don't look beyond the last matched character.
If anything, I think this issue qualifies for a DR, I don't see compelling reasons to change the current behavior of v3, which makes sense and its consistent with the other numeric parsings. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37958
