[Octave-bug-tracker] [bug #31079] DATESTR function buggy before year 1970

[J-D Bonjour]

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

                 Summary: DATESTR function buggy before year 1970
                 Project: GNU Octave
            Submitted by: jdb
            Submitted on: dim 19 sep 2010 22:27:29 GMT
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Incorrect Result
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 3.2.4
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

On Octave 3.2.4 Windows MinGW (from 3.2.0 ?), when the argument corresponds
to a date before 1st January 1970 at 1:00, result returned by DATESTR is
wrong. Example :

>> datestr(now)
ans = 17-Sep-2010 16:12:57
% it's OK

>> datestr(datenum(1970,1,1,1,0,01))
ans = 01-Jan-1970 01:00:01
% still OK

>> datestr(datenum(1970,1,1,0,59,30))
ans = 00-Jan-1900 00:00:00
% bad, shoud be 01-Jan-1970 00:59:30

>> datestr(1,'dd-mmm-yyyy HH:MM:SS')
ans = 00-Jan-1900 00:00:00
% bad, shoud be 01-Jan-0000 00:00:00

>> datestr(1.0001,'dd-mmm-yyyy HH:MM:SS')
ans = 01-Jan-1970 01:00:00
% bad, shoud be 01-Jan-0000 00:00:08
% and why suddenly back in year 1970 and not 1900 like previous command ???


On Linux Ubuntu 10.04, Octave 3.2.3 is buggy when the argument is earlier
than 13 December 1901 at 21:45:52, string allways returned is :  01-Jan-1970
00:59:59





    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message posté via/par Savannah
  http://savannah.gnu.org/