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

[Rik]

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:

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

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