[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #42343] textscan: difference between NaN and e
From: |
Philip Nienhuis |
Subject: |
[Octave-bug-tracker] [bug #42343] textscan: difference between NaN and empty values |
Date: |
Fri, 16 May 2014 09:18:21 +0000 |
User-agent: |
Mozilla/5.0 (Windows NT 5.1; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26 |
Update of bug #42343 (project octave):
Item Group: Matlab Compatibility => Incorrect Result
Operating System: GNU/Linux => Any
_______________________________________________________
Follow-up Comment #3:
[OT: Found out that my Mercurial version (2.1.1) is too old for @ bookmarks
:-( Will be fixed only when I upgrade my Linux distro, one of these days.]
Anyway this wasn't a matter of ML compatibility but a plain bug: textscan.m
would redo the emptyvalue work done by strread.m (its workhorse) assuming
strread.m returns NaN for empty fields. However strread.m does it right (the
example works fine with just strread).
I think that's why this bug was concealed for so long: it was triggered only
when hitting original NaN input fields.
Another bug was that textscan.m ignored user-specified emptyvalue when padding
output data for incomplete last lines of input files (also fixed now).
So, in case of user-specified emptyvalue, I expect textscan.m to work a tiny
bit faster now :-)
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?42343>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/