octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #53277] textscan(...) does not parse sequence


From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #53277] textscan(...) does not parse sequence of integers separated by dots (.)
Date: Sat, 3 Mar 2018 16:04:40 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.1

Update of bug #53277 (project octave):

                  Status:                    None => Invalid                
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #2:

Surprise for you:
Matlab r2018a prerelease does the same as Octave:

>> u = textscan ('5.2.1975','%d.%d.%d')

u =

  1×3 cell array

    {[5]}    {[1975]}    {0×1 int32}


I agree it is at least unexpected if not confusing, but Octave *is*
Matlab-compatible. 
Yes we can argue about bug-for-bug compatibility :-)


Then:
IIRC In Octave 4.0.3 textscan was still an .m-file function. We knew it wasn't
fully Matlab compatible then.

For the behavior you desire you can still use strread.m (FYI, before textscan
was re-implemented as a binary function, strread.m was textscan.m's work horse
behind the scenes):

>> [u, v, w] = strread ('5.2.1975','%d.%d.%d')
u = 5
v = 2
w = 1975
>>


For now I close this bug report as "Invalid".

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]