[Top][All Lists]

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

[Octave-bug-tracker] [bug #41579] HeaderLines parameter in textscan diff

From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #41579] HeaderLines parameter in textscan different between Octave and ML
Date: Fri, 14 Feb 2014 22:50:24 +0000
User-agent: Mozilla/5.0 (Windows NT 5.1; rv:25.0) Gecko/20100101 Firefox/25.0 SeaMonkey/2.22.1

Follow-up Comment #5, bug #41579 (project octave):

Thanks for asking "upstream".

In the mean time, I think on the Octave side this cannot be fixed to be
ML-'compatible' - at present, that is.
Octave's textscan.m is more or less line-oriented, in contrast to Matlab's
which acts more like a character-oriented binary file reader. Fiddling with
textscan.m's whitespace/delimiter/endofline defaults and with the way they're
processed won't help much I'm afraid, as the real issue is the way Octave's
textscan.m reads from file (i.e., before it even does the first analyses).

For some years now there have been plans to create a binary textscan(); JWE
has even made a rough skeleton (IIRC 2 or 3 years ago), but no one has had
time and priority yet to finish it.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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