[Octave-bug-tracker] [bug #38317] textread & textscan give different results in MATLAB and Octave

[Philip Nienhuis]

Update of bug #38317 (project octave):

                  Status:               Confirmed => Need Info              

    _______________________________________________________

Follow-up Comment #7:

Some observations: AFAICS in ML this only works if:
- the format string is empty
 AND
- you only specify one or no output argument (nargout <= 1)
 AND
- you only have numerical output (after headerline processing).

Attached is a patched textread.m that mimics ML's (AFAICS undocumented)
behavior.
Tests added and the bug I mentioned in comment #1 fixed (this bug fix is
already pushed, also for textscan.m).

Please try this textread.m (put it somewhere in your Octave search path, e.g.,
in your current working directory) and please report back if it works for
you.

I'm also busy amending textscan.m similarly but there I've got to investigate
possible interference with CollectOutput param.

Unfortunately I ran out of time to even prepare a changeset - hopefully next
week I can do that & finish textscan.m

(file #27466)
    _______________________________________________________

Additional Item Attachment:

File name: textread.m                     Size:8 KB


    _______________________________________________________

Reply to this item at:

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

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