|
From: | kloof |
Subject: | [Octave-bug-tracker] [bug #33955] fscanf with -NaN, -Inf, -NA |
Date: | Mon, 08 Aug 2011 14:35:36 +0000 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.30 (KHTML, like Gecko) Ubuntu/11.04 Chromium/12.0.742.112 Chrome/12.0.742.112 Safari/534.30 |
Follow-up Comment #2, bug #33955 (project octave): I discovered this handling of -NaN accidentally: the first time my fscanf (via a 'while' loop) runs into a -NaN it converts that first occasion into 0.000 and all other (valid floating point) values in that same line of text are also converted to 0.0000. I would think it's better to give an error message and stop (i.e. not to convert other numbers in the text to 0.000). _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?33955> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |