[Octave-bug-tracker] [bug #63462] sscanf reports incorrect number of output values.

[Rik]

Follow-up Comment #18, bug #63462 (project octave):

I think this may be related to underlying behavior of '>>' operator or
'peek()' function with the particular version of C++.  With my version of
libstdc++ I believe the failbit and the eofbit get set when reading touches
the EOF.

Nevertheless, the patch appears reasonable. For consistency, it should be
duplicated across the other calls to "if (octave_scan (...))" in that switch
block.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?63462>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/