octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #53277] textscan(...) does not parse sequence


From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #53277] textscan(...) does not parse sequence of integers separated by dots (.)
Date: Thu, 8 Mar 2018 05:53:56 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0 SeaMonkey/2.48

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/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]