[Octave-bug-tracker] [bug #47553] textscan Whitespace characters different from Matlab

[Philip Nienhuis]

Update of bug #47553 (project octave):

        Operating System:               GNU/Linux => Any                    

    _______________________________________________________

Follow-up Comment #8:

That same non-textscan incompatibility exists on Windows as well.
I know because I sometime make counters in .m files that use CR to avoid
scrolling up. But those do not work in Matlab - scrolling is unavoidable
there.


Ruminating my last comments I think there appears to be some logic in how
Matlab processes endofline/whitespace/delimiters. There must be some
consistent logic, after all.

First it processes (eliminates) endofline, maybe add it to delimiters.
Next it seems to collapse multiple whitespace.
Then it adds remaining whitespace to the delimiter collection.
Then it splits up the text stream.

Some noise exists as delimiters can also be non-numeric characters cuddling a
preceding numeric field.

At least that is how far I got trying to understand textscan's logic.

    _______________________________________________________

Reply to this item at:

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

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