[Octave-patch-tracker] [patch #8783] C++ implementation of textscan

[Philip Nienhuis]

Follow-up Comment #10, patch #8783 (project octave):

Yeah I figured the out-of-sync was due to something simple :-)

%[a-f] is also appealing to me, but I suppose (no time to check now) that
Matlab will treat it as characters "a", "-" and "f" rather than a,b, c, d, e
and f. Is there a monkey-proof way of allowing a-e syntax?

textscan.m doesn't implement returnonerror like ML but that is because it
works columnwise rather than ploughing linearly through a data file. This can
be fixed later in textscan.cc

"\n" on incomplete last lines - we'll have to look up what Matlab's textscan
does.
One of the ambitions was to have a binary textscan serve as workhorse for
strread.m and textread.m, rather than the other way round as it is now. Those
functions have special treatment for "\n" on incomplete last "lines".
Also to be fixed later.

As to comments, I think we'd need to follow what Matlab does, optionally and
where reasonable extended. Maybe also s/th to fix later...

I'll have a go at the new patch this weekend.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/patch/?8783>

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