[Octave-bug-tracker] [bug #59848] dlmread returns wrong values when skipping non-numerical columns

[Hartmut]

Follow-up Comment #8, bug #59848 (project octave):

Yes, that's the key point. Thanks for noting it!

When I change the line endings in my csv files (from currently CR) to CRLF,
then everything works fine. I then get the expected (and Matlab compatible)
results with my demo code in comment #0.

The history of those csv files is as follows: They were sent to me by email.
It might well be that these file were originally created on a Mac OS (but I
cannot be 100% sure, because it was not me creating them). I then massivly
edited the content of those csv files in order to prepare something small and
compact for this bug report. But I assume that this file editing (under
Windows as well as under Linux) did not change the existing line endings (i.e.
leaving it CR).

MY CONCLUSION: As a result, I would now reformulate the essence of this bug
report: "The dlmread function does not work properly with data files that have
CR line endings." This is a comptibility issue, because Matlab treats those
csv files with CR just fine. And this is also a usability issue, because I
understand Octave as a cross platform tool, that should be able to accept
files (at least data files like csv) also from other OS origin.

(My use case is the following: I demand the generation of data files and
corresponding m-files as a kind of homework. I then let the resulting code and
their corresponding data files run on my PC. And I would like Octave to work
properly, regardless of the OS that the person preparing the files uses. This
mostly works fine, in 99% of the cases. But in this corner case it seems to
fail.)

Can we fix this?

    _______________________________________________________

Reply to this item at:

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

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