[Octave-bug-tracker] [bug #47553] textscan Whitespace characters different from Matlab

[Lachlan Andrew]

Follow-up Comment #7, bug #47553 (project octave):

Rik, Philip's comment reminded me why the Octave documentation disagrees with
Matlab's: Matlab's was unclear to me, and I describes the best that I could
reverse-engineer from Matlab's actual behaviour.


Philip, thanks for those test cases.  I'll look into them, and (maybe) fix
them and/or add BIST cases.


You have demonstrated another non-textscan incompatibility.  On Linux at
least, Octave gives


>> str = ['1' char(8) '2' char(9) '3' char(10) '4' char(13) '5']
str = 2 3
5
>>
octave:2>


Note the absence of '4'.  Octave's GUI treats char(13) as a true carriage
return rather than Matlab's behaviour of treating it as NL+CR.

    _______________________________________________________

Reply to this item at:

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

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