[Octave-bug-tracker] [bug #52550] textscan drops delimiter character for multi-character, cell-specified delimiter option

[Dan Sebald]

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

Attached is a small bug fix.  Not much explanation beyond what is in said in
the changeset comment is needed.  Does this solve everything in terms of the
multi-character (i.e., cell-specified) delimiter?  Not sure, but I don't want
to think too much about that right now.  Try the patch for some scenarios I
guess.  At least the following works:


octave:7> b = "987123654123456"
b = 987123654123456
octave:8> c = "987120654123456"
c = 987120654123456
octave:9> textscan(b, '%s', 'delimiter', {'123'})
ans =
{
  [1,1] =
  {
    [1,1] = 987
    [2,1] = 654
    [3,1] = 456
  }

}

octave:10> textscan(c, '%s', 'delimiter', {'123'})
ans =
{
  [1,1] =
  {
    [1,1] = 987120654
    [2,1] = 456
  }

}



(file #42515)
    _______________________________________________________

Additional Item Attachment:

File name: octave-cell_specified_delimiter-bug52550-djs2017nov28.patch Size:0
KB


    _______________________________________________________

Reply to this item at:

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

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