[Octave-bug-tracker] [bug #53277] textscan(...) does not parse sequence of integers separated by dots (.)

[Matthias Brennwald]

Follow-up Comment #11, bug #53277 (project octave):

I can relate to the concept that using dots to separate integers may seem like
a bad idea. However, large parts of the world HAVE used this notation for
dates for a long time, and certainly for much longer than before Octave or its
commercial colleague came to exist. I don't think Octave (or any other
software out there) is in a position to dictate the world what date formats
are wrong or right.

I don't care about Matlab. But if an Octave function does not work as
described in the docs, it should be fixed (either the function or the
documentation). In this case, the textscan(...) function changed somewhere
from version 4.0 (where it works correctly) to 4.2 (where it does not work
correctly).

I am just an Octave user who does not know a thing about C/C++. I can't help
fixing the source code, and I leave it to the Octave maintainers to do
whatever they think is right.

    _______________________________________________________

Reply to this item at:

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

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