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

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

[Octave-bug-tracker] [bug #41579] textscan: file offset after partial re


From: Dan Sebald
Subject: [Octave-bug-tracker] [bug #41579] textscan: file offset after partial read differs from Matlab
Date: Tue, 24 Oct 2017 18:51:12 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0

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

"Maybe the only difference in the examples I gave is that regular delimiters
after the last read field are skipped but just not endofline. But when reading
continues, endofline seems to be treated as leading whitespace (I have to
confirm the latter)."

That's what I observed too, this was my goal for the modification.  That is,
the EOL-skip should be done prior to the scan action, not after.  I believe
there is currently a skip_whitespace prior to the scan action that does this. 
And that's the reason I had to remove the skip_whitespace() from the
skip_delim(), because otherwise it would remove the EOL.


"And then there is the thing that whitespace is treated differently when
reading text, than when reading numeric data."

I believe that is the case.  But I think handling such a thing inside
skip_whitespace() and skip_delim() makes for lots of conditional tests.  On
the other hand, a separate skip_eol() means that context can be kept out of
the lower-level routines.

Anyway, there is another collection of textscan() bugs being sorted through at
the moment, so we'll let the dust settle there and come back to this after
some thought.

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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