[Octave-bug-tracker] [bug #37961] textscan : whitespace specification doesn't work

[Philip Nienhuis]

Follow-up Comment #3, bug #37961 (project octave):

Sure, but OP refers to 3.6.3.

I can't track 'undefined whitespace' around L.114 in the dev version of
textscan.m, so that 'whitespace undefined' bug has been fixed already.
Perusing the file log I'd say probably > 2 years ago (when was 3.6.0 (last
stable version) released?)
Similarly for a missing ';' at L.109.

Anyway I can't reproduce OP's problems in the dev version. I get output but no
errors using his files, but obviously I cannot judge if it is good or not. I
think not as I get numbers rather than strings. Let the OP give us relevant
info.

My point about ';'-literal and defining it as whitespace still stands.

To the OP (maf88_): advice: grab textscan.m, textread.m and strread.m (they
are closely related) from here:
  http://hg.savannah.gnu.org/hgweb/octave/file/1e9a6285acc4/scripts/io
and swap them for the versions you have in
/usr/local/share/octave/3.6.3/m/io/
,try again and report back.

    _______________________________________________________

Reply to this item at:

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

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