octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #50485] textscan() behavior incompatible with


From: Motius
Subject: [Octave-bug-tracker] [bug #50485] textscan() behavior incompatible with matlab in case of empty lines
Date: Tue, 21 Nov 2017 07:14:05 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0

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

I think a found a related bug:

a = "\t\ta\tb\tc\n"
textscan(a, '%s', 'delimiter', sprintf('\t'))


does not have the same output on Octave 4.0.3 and 4.2.1. 
Version 4.0.3 matches MatLab's (v2017a) interpretation.

With v4.0.3:

{
  [1,1] = 
  {
    [1,1] = 
    [2,1] = 
    [3,1] = a
    [4,1] = b
    [5,1] = c
  }
}


With 4.2.1:

{
  [1,1] = 
  {
    [1,1] = a
    [2,1] = b
    [3,1] = c
  }
}



    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]