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

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

[Octave-bug-tracker] [bug #47538] textscan result different from 4.0.0 t


From: Lachlan Andrew
Subject: [Octave-bug-tracker] [bug #47538] textscan result different from 4.0.0 to dev
Date: Sun, 10 Apr 2016 09:58:48 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0

Update of bug #47538 (project octave):

                  Status:             In Progress => Patch Submitted        
             Assigned to:                    None => lachlan                

    _______________________________________________________

Follow-up Comment #5:

Philip, I agree that the old mode of trying to continue is problematic.  It is
probably better just to alert the user that the file is problematic.  If the
user needs something more flexible, they should probably do their own
parsing.

The attached patch gets rid of the "continue" option entirely, so that we only
have the two Matlab-compatible options.

Rik's original example still behaves differently from 4.0.0, but I believe it
now does what Matlab does: return only {[1]}.

(file #36888)
    _______________________________________________________

Additional Item Attachment:

File name: bug_47538_textscan_no_continue_on_error.cset Size:7 KB


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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