[Octave-bug-tracker] [bug #33680] System stalled by using 'strread'

[Philip Nienhuis]

Follow-up Comment #1, bug #33680 (project octave):

I have been working on strread.m, textread.m and textscan.m for some time to
make them more ML-compatible, (properly) implement some ML features, and fix a
few bugs, see #31380, #32720 and #33536. (At a low pace as I'm occupied with
many things at the moment)

The offending statement you mentioned can more easily be replaced by a simple
strplit(), provided that before invoking it some cleanup is performed as
regards whitespace etc. 
But that may take loads of memory, too.

I've attached my current versions of strread.m and textread.m  (textscan.m is
still in the making), I'd like to know if these work better for you.
So please report back!

Please note that there is some confusion (at my side) on how to treat
newlines. In strread.m, a newline was always added to the delimiters but I
doubt whether this is correct.
The ML docs are a bit unclear if not contradictory about whether newlines are
always treated as delimiters, or not. I've asked on some Matlab forums but got
no response yet.
If you need newline delimiters, with these test versions you might need to
supply a 
 ..., "delimiter", "<any delimiters you need>n"
parameter/value pair on the call to strread / textread / textscan


(file #23604, file #23605)
    _______________________________________________________

Additional Item Attachment:

File name: textread.m                     Size:3 KB
File name: strread.m                      Size:14 KB


    _______________________________________________________

Reply to this item at:

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

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