[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #46493] Incorrect result from fscanf and scanf
From: |
Doug Stewart |
Subject: |
[Octave-bug-tracker] [bug #46493] Incorrect result from fscanf and scanf |
Date: |
Sat, 21 Nov 2015 23:49:28 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.86 Safari/537.36 |
Follow-up Comment #2, bug #46493 (project octave):
more info
format short g
good = '"01","02","03","04","05","06"';
good1 = '"07"';
bad1 = '"08"';
bad2 = '"09"';
good2 = '"10"';
good3 = '"8"';
good4 = '"9"';
frm = '"%i" ,"%i","%i","%i","%i","%i"n';
v = sscanf(good,frm)'
v1 = sscanf(good1,frm)'
v2 = sscanf(bad1,frm)'
v3 = sscanf(bad2,frm)'
v4 = sscanf(good2,frm)'
v5 = sscanf(good3,frm)'
v6 = sscanf(good4,frm)'
>From this we can see that 08 and 09 are wrong but 8 and 9 are ok
and 01 02 03 04 05 06 07 are ok also
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?46493>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #46493] Incorrect result from fscanf and scanf, anonymous, 2015/11/21
- [Octave-bug-tracker] [bug #46493] Incorrect result from fscanf and scanf, Doug Stewart, 2015/11/21
- [Octave-bug-tracker] [bug #46493] Incorrect result from fscanf and scanf,
Doug Stewart <=
- [Octave-bug-tracker] [bug #46493] Incorrect result from fscanf and scanf with %i format, Rik, 2015/11/22
- [Octave-bug-tracker] [bug #46493] Incorrect result from fscanf and scanf with %i format, Richard Suchland, 2015/11/22
- [Octave-bug-tracker] [bug #46493] Incorrect result from fscanf and scanf with %i format, Anselm Köhler, 2015/11/24
- [Octave-bug-tracker] [bug #46493] Incorrect result from fscanf and scanf with %i format, Mike Miller, 2015/11/24
- [Octave-bug-tracker] [bug #46493] Incorrect result from fscanf and scanf with %i format, Philip Nienhuis, 2015/11/25
- [Octave-bug-tracker] [bug #46493] Incorrect result from fscanf and scanf with %i format, Mike Miller, 2015/11/25