[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #38317] textread & textscan: different results
From: |
Philip Nienhuis |
Subject: |
[Octave-bug-tracker] [bug #38317] textread & textscan: different results for empy format strings than MATLAB |
Date: |
Sun, 24 Feb 2013 10:42:28 +0000 |
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.11) Gecko/20100701 SeaMonkey/2.0.6 |
Update of bug #38317 (project octave):
Item Group: None => Matlab Compatibility
Summary: textread & textscan give different results in MATLAB
and Octave => textread & textscan: different results for empy format strings
than MATLAB
_______________________________________________________
Follow-up Comment #10:
(Edited title to better reflect exact issue;
Changed Item group to Matlab compatibility)
I don't understand exactly what you mean, sorry.
Do you have some example Matlab commands + small data file outlining the
problem? I have ML at hand so I can try both Octave and ML.
As to data files containing lines with varying number of data fields, please
note that those cannot be read by Octave's current textread.m and textscan.m
A binary (compiled) textscan() might do that but it is still in the making
(even primordial yet).
BTW, can you point us to Matlab documentation outlining this behavior of
textread (and textscan)?
AFAICS we're still discussing undocumented (yet IMO useful) ML features.
FYI, last week I have patched textscan.m as well (it behaves a bit differently
than textread.m with empty format strings) and fixed textread.m's tests (I've
mixed up a few things in the version you tried). I've also patched another
(yet unreported) bug in textread.m.
I'm awaiting your examples before I proceed any further.
Thanks
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?38317>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #38317] Textread gives different results in MATLAB and Octave, anonymous, 2013/02/12
- [Octave-bug-tracker] [bug #38317] Textread gives different results in MATLAB and Octave, Philip Nienhuis, 2013/02/12
- [Octave-bug-tracker] [bug #38317] textread & textscan give different results in MATLAB and Octave, Philip Nienhuis, 2013/02/12
- [Octave-bug-tracker] [bug #38317] textread & textscan give different results in MATLAB and Octave, Stig, 2013/02/13
- [Octave-bug-tracker] [bug #38317] textread & textscan give different results in MATLAB and Octave, Philip Nienhuis, 2013/02/13
- [Octave-bug-tracker] [bug #38317] textread & textscan give different results in MATLAB and Octave, Stig, 2013/02/13
- [Octave-bug-tracker] [bug #38317] textread & textscan give different results in MATLAB and Octave, Philip Nienhuis, 2013/02/13
- [Octave-bug-tracker] [bug #38317] textread & textscan give different results in MATLAB and Octave, Philip Nienhuis, 2013/02/14
- [Octave-bug-tracker] [bug #38317] textread & textscan give different results in MATLAB and Octave, Stig, 2013/02/16
- [Octave-bug-tracker] [bug #38317] textread & textscan give different results in MATLAB and Octave, Stig, 2013/02/16
- [Octave-bug-tracker] [bug #38317] textread & textscan: different results for empy format strings than MATLAB,
Philip Nienhuis <=