[Octave-bug-tracker] [bug #37961] textscan : whitespace specification doesn't work

[Ben Abbott]

Follow-up Comment #16, bug #37961 (project octave):

Jordi, ignoring the style, deprecation, and spell-check changes, there are
five changesets (below) that impact the results.  Do you mean to imply that
adding all of these is too aggressive?  I tend to think it is, but am worried
that a subset might introduce unexpected behavior.


changeset:   14565:98aaebc56d7c
user:        Philip Nienhuis <prnienhuis@@users.sf.net>
date:        Fri Mar 30 18:44:01 2012 +0200
summary:     2012-03-25 Philip Nienhuis <address@hidden>

changeset:   14582:e97ec01d4157
user:        Alexander Graf <address@hidden>
date:        Fri Apr 27 17:22:07 2012 +0200
summary:     Correct assignment to wrong variable f headerlines processing

changeset:   14799:21197c43f984
user:        Philip Nienhuis <address@hidden>
date:        Fri Jun 22 19:09:30 2012 +0200
summary:     Better Matlab compatibility of textscan, bugs #36356 and #36392

changeset:   14800:a922f768ee09
user:        Philip Nienhuis <address@hidden>
date:        Fri Jun 22 20:01:35 2012 +0200
summary:     textscan, strread: improved ML compatibility (bug 36398)

changeset:   15263:2136343014d5
user:        Philip Nienhuis <address@hidden>
date:        Thu Aug 30 20:52:40 2012 +0200
summary:     bug #37023 (wrong reading of lines starting and/or ending with
whitespace)



    _______________________________________________________

Reply to this item at:

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

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