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

[John W. Eaton]

Update of bug #31079 (project octave):

                  Status:                    None => Ready For Test         

    _______________________________________________________

Follow-up Comment #2:

Here is what I see with the current development sources of Octave:

octave:1> datestr (datenum (1969, 1, 1), 0) 
ans = 01-Jan-1969 00:00:00
octave:2> datestr (datenum (1901, 1, 1), 0) 
ans = 01-Jan-1901 00:00:00
octave:3> datestr (datenum (1795, 1, 1), 0) 
ans = 01-Jan-1795 00:00:00

I also see the same results with Octave 3.2.4 installed from the Debian
package.

But my system has glibc.

Maybe using the mktime module from gnulib would solve the problem, as that is
based on code from glibc?  I checked in the following change:

  http://hg.savannah.gnu.org/hgweb/octave/rev/0de4eff677d6

This change includes tests based on the examples in this bug report.  If you
have additional tests that would help, please submit a changeset.

It would be helpful if someone could test my change on systems where the
failure was previously happening and report back.

    _______________________________________________________

Reply to this item at:

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

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