[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #41579] textscan: file offset after partial re
|
From: |
Mike Miller |
|
Subject: |
[Octave-bug-tracker] [bug #41579] textscan: file offset after partial read differs from Matlab |
|
Date: |
Mon, 28 Mar 2016 17:38:33 +0000 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0 |
Update of bug #41579 (project octave):
Summary: HeaderLines parameter in textscan different between
Octave and ML => textscan: file offset after partial read differs from Matlab
_______________________________________________________
Follow-up Comment #9:
And if I add
fseek(fid, 40);
after the first textscan, then the script works without the Octave check.
So the core issue seems to be the file offset after textscan returns, not the
interpretation of the headerlines parameter.
Retitling appropriately.
Some more examples in Matlab showing what the file offset is after a partial
read would be helpful here.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?41579>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/