[Octave-bug-tracker] [bug #47413] string to numeric parsing problems with llvm libc++

[John W. Eaton]

Follow-up Comment #9, bug #47413 (project octave):

The following program seems to be enough to demonstrate the problem. I think
it should write "val: 1, failbit: 0" but it writes "val: 0, failbit: 4" when
using clang++ 3.7 and libc++.

If you put a space between the '1' and the 'a' in the stringstream, it works.
But I think it should stop reading the double value after the 1 either way. Am
I wrong? If the clang+libc++ behavior is standard conforming, we probably have
a lot of work to do to fix the way Octave reads numbers, so I hope I'm not
wrong...


#include <iostream>
#include <sstream>

int
main (void)
{
std::istringstream s1 ("1asdf");
double val = 0.0;
is >> val;
std::cerr << "val: " << val
<< ", failbit: " << (is.rdstate () & std::ios::failbit)
<< std::endl;
return 0;
}


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?47413>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/