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

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

[Octave-bug-tracker] [bug #52892] textread incorrectly reads a text file


From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #52892] textread incorrectly reads a text file when empty lines are present
Date: Mon, 15 Jan 2018 09:02:17 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0

Follow-up Comment #2, bug #52892 (project octave):

Well, I'm the one who suggested Pedro to use textread.m, but to my own
diappointment I soon found out that textread.m (in fact its backend strread.m)
chokes on the specific form of the comment lines in the file. It looks like
consecutive comment chars (rather than one comment char + text + EOL) screw up
somewhere; that happens with any single comment char, also with % rather than
#. I dived into it a bit but ran out of time.

FYI some years ago I have done a lot of work on strread.m (and textread.m) but
the comment processing code is Rik's.

I'm not sure if at this stage a separate bug report is required for that,
maybe later. Note that strread.m and textread.m are not so much deprecated but
rather disadvised by the Mathworks and I suppose Octave follows suite there.


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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