[Octave-patch-tracker] [patch #7969] Organized textread.m for better error notification

[Philip Nienhuis]

Follow-up Comment #9, patch #7969 (project octave):

"it'll certainly be for the better" - that's not quite guaranteed, evidenced
by several helpful suggestions from you.

It just happens that I wrote a lot of the current textread/textscan/stread
code and used it intensively at work, so I got a bit blind to otherwise
obvious missing internal documentation and sub-optimal program logic. OTOH I
do know a few potential yet undocumented[1] pitfalls, as you have read.

I'd appreciate you scrutinizing when I'm finished (not this week)

What you could do -if you're interested- is to extend the textread.m test
suite; at present it comprises only a meager 4 or 5 real tests and it lets a
lot of bugs slip through.
Tests could be ripped from textscan.m, which basically functions similarly to
textread.

To be cont'd...

[1] rather: hard-to-document-concisely

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/patch/?7969>

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