[Octave-bug-tracker] [bug #33536] strread returns incorect results and is not compatibile with Matlab

[Philip Nienhuis]

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

Sorry for being picky, but:
What exactly do you mean by "crash"? (I suppose that strread bails out rather
than that Octave crashes.)

A while ago I've sent in patches for textread & strread, a.o. for better ML
compatibility (mainly whitespace processing; see bug #32720).

With these patches, in your:
- Case 1: strread ends normally but gives 's]' as result => still wrong (Note
there's a stray '[' in your example).
- Case 2: Still fails.

I'll look into this, hopefully next week.
I'm in a similar situation as you (porting loads of ML code to Octave) and I
found textread/strread/textscan do need some attention... 
I might have a go at bugs #31380 and #31778 as well.

The test stanzas in strread.m were in need of some polishing anyway; the
"cases" you brought forward seem like good candidates for better test cases.


    _______________________________________________________

Reply to this item at:

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

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