[Octave-bug-tracker] [bug #57086] textscan "TreatAsEmpty" option produces a garbled cell array

[Rik]

Update of bug #57086 (project octave):

                 Summary: textscan produces a garbled cell array: some data
are missing, some values are wrong. => textscan "TreatAsEmpty" option produces
a garbled cell array

    _______________________________________________________

Follow-up Comment #3:

There is something wrong with the "TreatAsEmpty" option.  I don't know if this
is the only problem, but it certainly exists.

I've attached a simpler example for this.  When there is a pattern that should
be treated as empty and it is in the last position in the file, it is returned
as 0 instead of as NaN.

Incidentally, since the expression in Hic.m is using "TreatAsEmpty", "?" it
should be replacing "?" with NaN everywhere in the file.  If I open up the
data file using a text editor and search and replace to change "?" to NaN and
then use Hic.m to read the file, then there are 7440 data lines as expected.

(file #47724, file #47725)
    _______________________________________________________

Additional Item Attachment:

File name: tst_empty.m                    Size:0 KB
    <https://savannah.gnu.org/file/tst_empty.m?file_id=47724>

File name: tst_empty.csv                  Size:0 KB
    <https://savannah.gnu.org/file/tst_empty.csv?file_id=47725>



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?57086>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/