[Octave-bug-tracker] [bug #54622] test importdata fails in dev octave with windows

[Dan Sebald]

Follow-up Comment #10, bug #54622 (project octave):

The file is the same in both cases, so it isn't the input file that is the
source of the problem.

None of these data reading routines is documented well with regard to the
output, in this case A.  It's strange that it is creating the expected matrix
as a sub-element of a structure, then also some extra bit of information.  It
appears to me that the extra bit of information is a bunch of strings that the
routine cannot translate.  That textdata, i.e.,


    textdata =
    {
      [1,1] = Inf
      [2,1] = -Inf
      [3,1] = NaN
    }


suggests that importdata, or dlmread, or something else is in a mode in which
"Inf" etc. cannot be properly read as float/double values.  Perhaps one of the
previous texts changed some flag somewhere that controls that.

I find it odd that textdata doesn't have some means of associating the text
field with its (possibly multiple) position in the matrix.  Since that
information is lost, it's not of much use after the import to the user in
terms of reconstructing what happened.

    _______________________________________________________

Reply to this item at:

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

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