[Octave-bug-tracker] [bug #50619] textscan weird behaviour when reading a csv

[Philip Nienhuis]

Follow-up Comment #14, bug #50619 (project octave):

Good detective work, Dan. Obviously it looked like some buffer size issue but
which buffer and where it is to be found ...

Answer to comment #11 Q1:
< "endofline", "" > is perfectly legal syntax and can be useful when reading
from strings (i.e., not a text file, or a file not standard organized along
lines like e.g., XML or html)

AFAIU from my textscan.m/strread.m work from years gone by, endofline is
whitespace but whitespace *is* a default delimiter unless "%s" (character
string) format specifiers come into play, in which case endofline is moved to
the delimiter collection. Or something like that ... the (=TMW's) logic is
almost untractable.


    _______________________________________________________

Reply to this item at:

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

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