[Top][All Lists]

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

[Octave-bug-tracker] [bug #33955] fscanf with -NaN, -Inf, -NA

From: Rik
Subject: [Octave-bug-tracker] [bug #33955] fscanf with -NaN, -Inf, -NA
Date: Fri, 05 Aug 2011 20:49:27 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0

Update of bug #33955 (project octave):

                  Status:                    None => Confirmed              


Follow-up Comment #1:

Confirmed.  -Inf makes sense to me but the others don't.  I don't think we
should accept "-NA" or "-NaN" inputs because we don't have a way to represent
them in Octave.

For example, trying these conversions in Octave I get

x = -NA
x = NaN

x = -NaN
x = NaN

The first one is very wrong as it changes an NA value to a NaN value.  The
next one is modestly wrong as it changes the sign of the NaN value.  Thus, I
would vote to fix "-Inf" but leave "-NA" and "-NaN" to stop the conversion
procedure and inform the user to change their input file.  


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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