[Top][All Lists]

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

[Octave-bug-tracker] [bug #43181] Function datenum incorectly handles tw

From: anonymous
Subject: [Octave-bug-tracker] [bug #43181] Function datenum incorectly handles two digit years
Date: Tue, 09 Sep 2014 20:15:58 +0000
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0


                 Summary: Function datenum incorectly handles two digit years
                 Project: GNU Octave
            Submitted by: None
            Submitted on: Tue 09 Sep 2014 08:15:57 PM UTC
                Category: Octave Function
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Incorrect Result
                  Status: None
             Assigned to: None
         Originator Name: mreich
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 3.8.1
        Operating System: Other




Running Octave 3.8.1 under Cygwin under MSwin 7.
After updating today, the function datenum works as illustrated:

datenum("26-jun-00 14:56:00")
ans =  178.62
datenum("26-jun-00 14:56:00",2000)
ans =  178.62
datenum("26-jun-00 14:56:00",000)
ans =  178.62
datenum("26-jun-2000 14:56:00")
ans =    7.3066e+05

That is, datenum does not correctly interpret datestrings with two digit
years.  Prior to updating, datenum may have worked properly as described in
the 'datenum' entry of Edition 3 of the GNU Octave reference manual.

Thank you,


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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