[Octave-bug-tracker] [bug #45808] fscanf odd behavior with newlines

[Jordi Burguet Castell]

Follow-up Comment #2, bug #45808 (project octave):

Thanks for the input. That would work for this particular example, but I'm
finding the problem as part of a larger script that parses a more-or-less
complex text file. I've tried several changes, including your suggestion, and
it breaks the parsing later on, one way or another, in a non-trivial way.

The fact is that matlab can easily parse those files, and I've given up for
the moment trying to have octave parse them too with the same code, because it
got so complicated.

In any case, octave is behaving different than matlab there, so it can be
fixed. Unfortunately I don't know about a workaround that worked for me, but I
can wait until it's fixed in octave.

    _______________________________________________________

Reply to this item at:

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

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