[Octave-bug-tracker] [bug #53277] textscan(...) does not parse sequence of integers separated by dots (.)

[Philip Nienhuis]

Follow-up Comment #10, bug #53277 (project octave):

As I expected, TMW attempted to put me off with:
"... recommend to avoid that a dot only follows a number which is meant to be
integer."
I nudged them to rethink that a bit I still have little faith there.

While I second TMW's advice (sorry Matthias) I agree that Octave's textscan
might do better than Matlab as regards reading data specified as integers.
Is there a C++ equivalent of sscanf in Octave's code base that can be used for
this?

BTW 1: We now hit this bug with dots, but exponent characters lead to similar
problems. Didn't dare yet to try with i and j (complex).

BTW2: I'll add a note to strread.m's texinfo header to avoid dots and exponent
characters as literals or separators for numeric fields; experimenting a bit
with those did uncover unexpected / unpredictable results.
Maybe it is better to (provisionally) add such a note to textscan's header as
well.



    _______________________________________________________

Reply to this item at:

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

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