octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #42343] textscan: difference between NaN and e


From: sergey plotnikov
Subject: [Octave-bug-tracker] [bug #42343] textscan: difference between NaN and empty values
Date: Tue, 13 May 2014 08:05:37 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.132 Safari/537.36

URL:
  <http://savannah.gnu.org/bugs/?42343>

                 Summary: textscan: difference between NaN and empty values
                 Project: GNU Octave
            Submitted by: nul0m
            Submitted on: Tue 13 May 2014 08:05:35 AM GMT
                Category: Octave Function
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Matlab Compatibility
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: GNU/Linux

    _______________________________________________________

Details:

There's a nuance in Matlab's behavior of _textscan()_ -- NaNs which were found
in a text are not treated as empty values but as NaNs literally.

These may cause different result comparing to ML's one. See below.

*Matlab*


>> textscan(',NaN','','delimiter',',','emptyValue',Inf)
ans = 
    [Inf]    [NaN]


*Octave*


>> textscan(',NaN','','delimiter',',','emptyValue',Inf)
ans =
{
  [1,1] = Inf
  [1,2] = Inf
}





    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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